The remote recipient learns the host identity and local package/project paths 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 path both reach code that sends host identity and local paths to a fixed external endpoint without user consent. This is concrete, reachable data exfiltration unrelated to the package's stated shim function.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Installation via postinstall, or import of the package entry point.
Mechanism
beacon.cjs sends a POST to a hard-coded VPS with hostname, install path, and working directory; TLS certificate verification is disabled.
Attack narrative
Installation or importing the package automatically triggers a beacon that sends the machine hostname and filesystem paths to a fixed external VPS. The package presents itself as a compatibility shim, and this collection is unrelated to that function.
Evidence
package.jsonindex.jsbeacon.cjs
Network endpoints1
vmi3699893.contaboserver.net:8787/_ah/dc
Decision evidence
public snapshot
Evidence for block
The package's postinstall script runs beacon.cjs.
Importing the main entry point calls beacon.cjs fire() automatically.
The beacon POSTs to a fixed external VPS and disables TLS certificate verification.
The payload includes the machine hostname, install path, and current working directory.
Evidence against
The README describes the package as an authorized dependency-confusion test and says it reports installation metadata.
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/bank@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.