Exposes host identity and local installation and project 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 install hook sends hostname and local path data to a fixed external collector, and importing the package triggers the same send. The README’s authorized-test claim does not establish consent for 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 package installation via postinstall and again when the package is imported.
Mechanism
The beacon gathers hostname, installation path, and working directory, then posts the payload to a hard-coded external endpoint.
Attack narrative
The postinstall hook and package import send the machine hostname and local paths to a hard-coded external VPS, exposing host and project metadata without installer consent.
Evidence
package.jsonbeacon.cjsindex.js
Network endpoints1
vmi3699893.contaboserver.net:8787/_ah/dc
Decision evidence
public snapshot
Evidence for block
The postinstall script runs `beacon.cjs` automatically.
The beacon posts installation metadata to a fixed external VPS endpoint.
The payload includes the machine hostname, package installation path, and current working directory.
Importing the package also calls the beacon sender.
Evidence against
The README says the package reports its installation as part of an authorized dependency-confusion test; that claim 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/card@1.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.