Exposes machine identity and local package/project paths to an unrelated collector without installer consent.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
AI security review
scanned · by lpm-firewall-ai
The automatic postinstall and import paths send identifying host and local path data to a hard-coded endpoint outside the package’s stated function. This is install-time data exfiltration, even though the README describes the reported fields.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
npm postinstall; also importing index.js.
Mechanism
beacon.cjs posts a payload containing the hostname, install directory, and current working directory to a hard-coded server.
Attack narrative
The postinstall hook runs beacon.cjs, which sends the machine hostname and local install and working-directory paths to a hard-coded external server. Importing the package triggers the same send. The package is presented as a compatibility shim, so this collection is unrelated to its function.
Evidence
package.jsonbeacon.cjsindex.js
Network endpoints1
vmi3699893.contaboserver.net:8787/_ah/dc
Decision evidence
public snapshot
Evidence for block
The postinstall script runs beacon.cjs automatically.
beacon.cjs sends a POST to a hard-coded server unrelated to the compatibility-shim purpose.
The payload includes the machine hostname, package install path, and current working directory.
Importing index.js also calls the beacon.
Evidence against
The README describes the package as a compatibility shim and says it reports package, hostname, and path.
Behavioral surface
SourceNetwork
Supply chainURL strings
ManifestNo manifest risk signals triggered.
Scanned 2 files · 2.41 KB of source
1 external domain referenced
vmi3699893.contaboserver.net
Findings
8 high · 1 medium · 2 low
Where they are, most severe file first. Code opens a file's flagged lines, with their evidence, below.
Avoid installing @c1-ease/autoloan@2.0.1. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.