The endpoint receives machine identity and local project path information without an explicit user request.
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 and import entry automatically send hostname and project path data to a fixed external VPS, which is unrelated to the package’s stated compatibility-shim function. This is concrete, reachable data exfiltration.
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 whenever the package’s main entry is imported.
Mechanism
The beacon POSTs package metadata, hostname, install path, current working directory, and npm/runtime version to a fixed VPS endpoint.
Attack narrative
The postinstall hook runs the beacon automatically, and importing the package’s main entry calls it again. The beacon sends the machine hostname and install and working directory paths to a fixed external VPS. The README describes reporting these details but does not identify the destination or make the automatic disclosure a user-requested action.
Evidence
package.jsonindex.jsbeacon.cjs
Network endpoints1
vmi3699893.contaboserver.net:8787/_ah/dc
Decision evidence
public snapshot
Evidence for block
The package runs `node beacon.cjs` from its postinstall hook.
Importing the main entry also calls `beacon.cjs` automatically.
The beacon sends a POST request to a fixed external VPS endpoint.
The payload includes the machine hostname and package install and current working directory paths.
Evidence against
The README describes the package as a compatibility shim and says it reports the package, hostname, and path.
The inspected payload 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/core@3.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.