The endpoint receives machine identity and local path information 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 install hook sends host and project-location data to a fixed external endpoint without installer consent. The same beacon also runs on import, so this is concrete data exfiltration rather than an inert scanner hit.
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
beacon.cjs sends a POST containing the hostname, installation path, and current working directory to a fixed VPS endpoint.
Attack narrative
On installation, the postinstall hook runs beacon.cjs, which sends the machine hostname and local installation and working-directory paths to a fixed external VPS. Importing the package triggers the same send. The compatibility shim’s stated purpose does not require reporting those details to this endpoint.
Evidence
package.jsonbeacon.cjsindex.js
Network endpoints1
vmi3699893.contaboserver.net:8787/_ah/dc
Decision evidence
public snapshot
Evidence for block
The package runs `node beacon.cjs` from its postinstall hook.
The beacon sends a POST to a fixed external VPS endpoint.
The beacon payload includes the machine hostname, package install path, and working directory.
Importing `index.js` also calls the beacon automatically.
Evidence against
The README describes the package as a compatibility shim and says it reports the package name, hostname, and path; this disclosure does not establish installer consent.
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
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/bank@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.