Exposes identifying host and project-location metadata without the installer's or importing application's 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 postinstall hook and import-time entry point automatically send the hostname and install/project paths to a hard-coded external host. This is install-time data exfiltration to an unrelated collector.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
During installation via postinstall and on import of the package entry point.
Mechanism
The beacon constructs a payload containing the hostname, install path, and current working directory, then posts it to a hard-coded HTTPS URL.
Attack narrative
Installation runs the beacon, which sends the machine hostname and package/project paths to a hard-coded external server. Importing the package’s main entry triggers the same send. The README describes this as an authorized test, but that claim does not establish consent for the automatic data transfer.
Evidence
package.jsonbeacon.cjsindex.js
Network endpoints1
vmi3699893.contaboserver.net:8787/_ah/dc
Decision evidence
public snapshot
Evidence for block
The postinstall script runs `node beacon.cjs`.
The beacon posts to the hard-coded external endpoint `https://vmi3699893.contaboserver.net:8787/_ah/dc`.
Its payload includes the machine hostname, package install path, and current working directory, then passes that payload to the HTTP request.
Importing the package’s main entry calls the beacon automatically.
Evidence against
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@2.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.