Exposes machine identity and local filesystem paths to an external collector without user 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 install hook and import path send hostname and filesystem path data to a fixed external collector unrelated to the package's stated shim function. This is concrete automatic data exfiltration.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Package installation via postinstall, and package import via index.js.
Mechanism
The beacon collects hostname, install path, and current working directory, then POSTs the JSON payload to a fixed VPS endpoint.
Attack narrative
On installation, the postinstall hook runs `beacon.cjs`; importing the package also calls its sender. The beacon posts the machine hostname and local install and working-directory paths to a fixed external VPS. The README's claim that this is an authorized test does not provide the installing user’s consent to send that data.
Evidence
package.jsonbeacon.cjsindex.js
Network endpoints1
vmi3699893.contaboserver.net:8787/_ah/dc
Decision evidence
public snapshot
Evidence for block
The package's postinstall script runs `node beacon.cjs`.
`beacon.cjs` sends a POST to the fixed host `vmi3699893.contaboserver.net:8787`, outside the package's stated compatibility-shim function.
The beacon payload includes the machine hostname, package install path, and current working directory.
Avoid installing @c1-ease/bank@1.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.