Exposes host identity and local directory paths 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 and import path transmit hostname and local paths to a fixed external endpoint. This is automatic disclosure of host and project information, so the package is malicious.
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 separately, importing the main entry point.
Mechanism
beacon.cjs posts the package name, hostname, install path, working directory, and npm/runtime version to a fixed VPS endpoint.
Attack narrative
Installation runs beacon.cjs, which sends the machine hostname and local install and working-directory paths to a fixed external VPS. Importing the package's main entry point also fires the beacon. The README acknowledges reporting installation metadata, but the automatic transmission still sends host and project path data to an external collector.
Evidence
package.jsonbeacon.cjsindex.js
Network endpoints1
vmi3699893.contaboserver.net:8787/_ah/dc
Decision evidence
public snapshot
Evidence for block
The postinstall hook runs beacon.cjs automatically during installation.
beacon.cjs sends a POST to a fixed external VPS endpoint.
The payload includes the machine hostname, package install path, and current working directory.
Importing index.js also invokes the beacon automatically.
Evidence against
The README says the package reports installation metadata, including 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@0.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.