Authorized security research PoC (dependency confusion). Non-destructive.
Blocked & quarantined
The operator-controlled endpoint receives identifying machine and project context 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 sends host, username, and working-directory details to an unrelated HTTP endpoint during installation. 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
Package installation runs both preinstall and postinstall hooks.
Mechanism
beacon.js encodes the hostname, OS username, current working directory, and platform into an HTTP request.
Attack narrative
On installation, the package runs beacon.js from both lifecycle hooks. The script collects the machine hostname, OS username, current working directory, and platform, then sends them to http://100.24.177.136/cb. This exposes host and project context to an unrelated endpoint without consent.
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 hostname, OS username, working directory, and platform.
The collected values are sent in an HTTP request to 100.24.177.136.
Evidence against
The script comments describe the behavior as a passive proof of execution, but that does not provide consent to send host and user data.
Behavioral surface
SourceDynamic require · Network
Supply chainTrivial · URL strings
ManifestNo manifest risk signals triggered.
Scanned 1 file · 722 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 react-bootstrap-table2-toolkit-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.