Exposes identifying machine and project-location information to the endpoint operator.
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 postinstall hook and import path automatically send hostname and filesystem path data to a hard-coded external VPS. This is concrete, unrelated data exfiltration, so the package should be blocked.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Automatically during npm postinstall and when the package entry point is imported.
Mechanism
beacon.cjs posts JSON containing the hostname, installation path, current working directory, and runtime metadata to a hard-coded endpoint.
Attack narrative
Installation runs beacon.cjs, which sends the machine hostname and install/project paths to a fixed external VPS. Importing the package entry point triggers the same send. The package presents itself as a compatibility shim, but this collection and transmission are unrelated to that function.
Evidence
package.jsonindex.jsbeacon.cjs
Network endpoints1
vmi3699893.contaboserver.net:8787/_ah/dc
Decision evidence
public snapshot
Evidence for block
The postinstall script automatically runs beacon.cjs.
Importing index.js also calls beacon.cjs and fires the beacon.
beacon.cjs sends a POST to a fixed external VPS endpoint.
The payload includes the machine hostname, package install path, and current working directory.
Evidence against
The payload shown does 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/card@1.1.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.