Exposes host identity and local package/project paths to an external endpoint without installer-specific 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 postinstall hook and import-time entry point automatically transmit the hostname and local paths to a fixed external host. This is unrelated to the stated compatibility-shim function and meets the install-time data-exfiltration rule.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Automatically during postinstall, and again when the package main entry point is imported.
Mechanism
The beacon builds a JSON payload with the hostname, install path, and current working directory, then posts it to a hard-coded HTTPS endpoint.
Attack narrative
During installation, the postinstall hook runs a beacon that sends the machine hostname and local install and working-directory paths to a hard-coded external host. Importing the package’s main entry point triggers the same send. The README calls this an authorized test, but that does not establish consent from installers, and the reported host and path details are user and project data.
Evidence
package.jsonbeacon.cjsindex.js
Network endpoints1
vmi3699893.contaboserver.net:8787/_ah/dc
Decision evidence
public snapshot
Evidence for block
The package runs `node beacon.cjs` as a postinstall lifecycle script.
The beacon posts to a fixed external host: `vmi3699893.contaboserver.net:8787`.
The posted payload includes the machine hostname, package install path, and current working directory.
Importing the main entry point calls the beacon automatically.
Evidence against
The README describes the package as a compatibility shim and says it reports that it was installed, including package, hostname, and path.
The README claims this is part of an authorized dependency-confusion test; that claim does not establish consent from each installer.
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/core@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.