kmf-bootstrap@100.100.103
Frontend utilities
This package appears in our research on the dependency confusion probes at version 99 and above, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe automatic postinstall hook performs external DNS reporting and, on addon-load failure, posts identifying machine and npm environment data to a fixed IP. This is concrete install-time data exfiltration and supports blocking the package.
Decision evidence
public snapshot- package.json runs postinstall.js automatically during installation.
- postinstall.js encodes the machine hostname and package name into a DNS query to a fixed external domain.
- If the native addon load fails, postinstall.js collects the hostname, username, package name, and npm registry, then posts them to a fixed external IP.
- index.js exports an empty object; the observed collection and network behavior is in the install hook.
Source & flagged code
9 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgpackage.json runs postinstall.js automatically during installation.
package.jsonView on unpkg · L7Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to kmf-bootstrap@100.100.103.
See all versions of kmf-bootstrap for other recorded verdicts.
- Avoid installing kmf-bootstrap@100.100.103. 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.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.