kmf-bootstrap@100.100.102
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 install-time hook deliberately transmits machine and package identifiers through DNS to a fixed external domain. This is concrete covert data disclosure behavior and supports blocking publication.
Decision evidence
public snapshot- package.json runs postinstall.js automatically during installation.
- postinstall.js encodes the machine hostname and npm package name into a DNS query to a fixed oast.me subdomain.
- postinstall.js issues DNS lookups for that constructed hostname, creating an install-time outbound disclosure channel.
- index.js only exports an empty object; the observed network behavior is in the postinstall hook.
Source & flagged code
7 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.102.
See all versions of kmf-bootstrap for other recorded verdicts.
- Avoid installing kmf-bootstrap@100.100.102. 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.