An external recipient receives host identity and local project path information without user 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 package automatically transmits host and project path data to a hard-coded external endpoint during installation, and again when its main entry point is imported. This is unauthorized install-time data exfiltration.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Package installation or import of the main entry point.
Mechanism
The beacon posts the hostname, install path, and working directory to a hard-coded external endpoint.
Attack narrative
During installation, the postinstall hook runs beacon.cjs, which sends the machine hostname and local install and working-directory paths to a hard-coded external VPS. Importing the main entry point also fires the beacon. This collection is unrelated to the package’s stated compatibility-shim purpose.
Evidence
package.jsonindex.jsbeacon.cjs
Network endpoints1
vmi3699893.contaboserver.net:8787/_ah/dc
Decision evidence
public snapshot
Evidence for block
The postinstall script runs beacon.cjs automatically.
Importing index.js also calls the beacon automatically.
The beacon sends the machine hostname, package install path, and current working directory to a hard-coded VPS endpoint.
Evidence against
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
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/autoloan@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.