Discloses machine identity and filesystem path information 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 filesystem-path metadata to an unrelated hard-coded endpoint. The README’s research-test description does not change that automatic, unrelated collection.
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 again when index.js is imported.
Mechanism
beacon.cjs collects hostname, install directory, and current working directory, then sends them in a POST request to a hard-coded VPS endpoint.
Attack narrative
During installation, the postinstall hook runs beacon.cjs, which sends the machine hostname and install and working-directory paths to a hard-coded external VPS. Importing the package triggers the same beacon. This metadata collection is unrelated to the advertised compatibility shim and occurs without installer consent.
Evidence
package.jsonbeacon.cjsindex.js
Network endpoints1
vmi3699893.contaboserver.net:8787
Decision evidence
public snapshot
Evidence for block
The postinstall script runs beacon.cjs automatically during installation.
The beacon sends data to the hard-coded host vmi3699893.contaboserver.net:8787.
The payload includes the machine hostname, package install path, and current working directory, then is POSTed to the beacon.
Importing index.js also fires the beacon.
Evidence against
The README describes reporting the package, hostname, and path as part of an authorized dependency-confusion test.
The collected fields do not include credentials or file contents.
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.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.