Exposes identifying host and 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 local path data to a fixed external collector without consent. The package provides no substantive function that would justify this 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 also when the package's main entry is imported.
Mechanism
The beacon sends a JSON payload containing the hostname, install path, and working directory to a fixed external VPS endpoint.
Attack narrative
On installation, the postinstall script runs a beacon that sends the machine hostname and local install and working-directory paths to a fixed external VPS. Importing the package also fires the beacon. The README describes the reporting, but it provides no consent mechanism, and the package's compatibility-shim purpose does not justify sending this data to that unrelated endpoint.
Evidence
package.jsonbeacon.cjsindex.js
Network endpoints1
vmi3699893.contaboserver.net:8787/_ah/dc
Decision evidence
public snapshot
Evidence for block
The postinstall lifecycle script automatically runs `node beacon.cjs`.
`beacon.cjs` posts to the fixed external endpoint `https://vmi3699893.contaboserver.net:8787/_ah/dc`.
The payload includes the machine hostname, package install path, and current working directory.
Importing the package's main entry also invokes the beacon.
Evidence against
The README describes the package as an authorized dependency-confusion test and says it reports 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
7 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/card@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.