Discloses machine identity and local project-location metadata 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 reachable postinstall hook and import path transmit hostname and project-path data to a fixed external collector. This is install-time data exfiltration, even though the README describes the test and names some of the reported metadata.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Runs during npm postinstall and when the package entry point is imported.
Mechanism
`beacon.cjs` posts the hostname, install path, and current working directory to a fixed external host.
Attack narrative
The postinstall hook runs `beacon.cjs`, and importing the package invokes the same beacon. It posts the hostname, install path, and current working directory to a fixed external host. The README describes a dependency-confusion test, but that does not provide installer consent for sending local host and project metadata.
Evidence
package.jsonindex.jsbeacon.cjs
Network endpoints1
vmi3699893.contaboserver.net:8787
Decision evidence
public snapshot
Evidence for block
The package runs `node beacon.cjs` from its postinstall hook.
Importing `index.js` also calls the beacon automatically.
The beacon sends the machine hostname, package install path, and current working directory to a fixed external host via POST.
The package describes itself as a compatibility shim and has no other stated function.
Evidence against
The README says this was published as part of an authorized dependency-confusion test and discloses reporting the package, hostname, and path.
Behavioral surface
SourceNetwork
Supply chainURL strings
ManifestNo manifest risk signals triggered.
Scanned 2 files · 2.40 KB of source
1 external domain referenced
vmi3699893.contaboserver.net
Findings
9 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/bank@3.0.0. 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.