Authorized security research PoC (dependency confusion). Non-destructive.
Blocked & quarantined
The operator receives identifying host and project-path information without installer 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 runs a beacon during both installation hooks and sends host and working-directory data to an unrelated external endpoint. This is 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
The package's preinstall or postinstall lifecycle script runs.
Mechanism
Each script runs beacon.js, which collects hostname, username, current working directory, and platform, then sends them in an HTTP request.
Attack narrative
During installation, both lifecycle hooks execute beacon.js. It collects the machine hostname, OS username, working directory, and platform, then sends those values to the unrelated operator-controlled endpoint at 100.24.177.136.
Evidence
package.jsonbeacon.js
Network endpoints1
100.24.177.136/cb
Decision evidence
public snapshot
Evidence for block
Both preinstall and postinstall run beacon.js automatically.
beacon.js collects the machine hostname, OS username, current working directory, and platform.
The collected values are sent by HTTP to 100.24.177.136/cb.
Evidence against
Behavioral surface
SourceDynamic require · Network
Supply chainTrivial · URL strings
ManifestNo manifest risk signals triggered.
Scanned 1 file · 702 B of source
1 external domain referenced
100.24.177.136
Findings
5 high · 2 medium · 2 low
Where they are, most severe file first. Code opens a file's flagged lines, with their evidence, below.
Avoid installing file-saver-bg@9.9.9. 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.