kmf-i18n@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 automatic install hook performs covert DNS disclosure of machine and package identifiers to an unrelated domain, which is concrete data exfiltration. The bundled native addon is opaque, but is not needed to support the malicious verdict.
Decision evidence
public snapshot- The manifest runs postinstall.js automatically during installation.
- The install hook constructs a DNS name from the machine hostname and npm package name under an unrelated oast.me domain, then issues DNS lookups.
- The same install hook attempts to load an opaque native addon whose behavior could not be inspected.
- index.js only exports an empty object; it does not add a runtime behavior that explains the install-time DNS lookups.
Source & flagged code
6 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgThe manifest 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-i18n@100.100.102.
See all versions of kmf-i18n for other recorded verdicts.
- Avoid installing kmf-i18n@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.