The endpoint receives identifying host and project-location data without an explicit user action.
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 both trigger a beacon that sends hostname and filesystem-path details to a fixed external host. This data collection is not needed for the shim's stated compatibility function.
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 package import via index.js.
Mechanism
beacon.cjs posts package metadata, hostname, install path, working directory, and Node version to a fixed external endpoint.
Attack narrative
On installation or import, the package sends the machine hostname and install and working-directory paths to a fixed external host. This is an unrelated collector for a compatibility shim, so the behavior is malicious data exfiltration.
Evidence
package.jsonbeacon.cjsindex.js
Network endpoints1
vmi3699893.contaboserver.net:8787/_ah/dc
Decision evidence
public snapshot
Evidence for block
The package runs beacon.cjs automatically through its postinstall script.
The beacon sends data to vmi3699893.contaboserver.net:8787.
The payload includes the machine hostname, install path, working directory, and Node version.
Importing the package also calls the beacon automatically.
Evidence against
The README describes the package as a compatibility shim and says it reports installation details as part of an authorized dependency-confusion test.
Behavioral surface
SourceNetwork
Supply chainURL strings
ManifestNo manifest risk signals triggered.
Scanned 2 files · 2.41 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/commerce@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.