kmf-vendor-pack@100.100.101
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.
OpenSSF/OSV Malicious Advisory
imported 12d ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-17744 confirms this npm version as malicious.
Advisory
MAL-2026-17744
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in kmf-vendor-pack (npm)
Details
kmf-vendor-pack@100.100.100 is a dependency-confusion lure. package.json declares `postinstall: node postinstall.js`, which require()s a shipped prebuilt Linux x64 N-API addon at prebuilds/linux-x64/addon.node. The addon's napi_register_module_v1 Init routine calls fork(), opens a socket, connects to the hardcoded bare IP 64.181.165.115, and sends `POST /dc HTTP/1.0` with body `h=<HOSTNAME>&p=<npm_package_name>&u=<user>&r=<npm_config_registry>`, leaking the installing host's name, the resolved package name, and the configured npm registry URL to attacker infrastructure over plain TCP. The native binary ships with no accompanying C/C++ sources, no binding.gyp, and no legitimate functionality matching the stated `Frontend utilities` purpose; the JS entry point is an empty `module.exports = {}`. The version number 100.100.100 is implausibly high and consistent with resolution-winning against an internal package of the same name. Installing this package causes immediate outbound disclosure of install-environment and internal-registry metadata to the attacker.
## Source: ossf-package-analysis (90252f22765869df637f77df2754cd36724812550151c9c7c53926bc83daad2e) The OpenSSF Package Analysis project identified 'kmf-vendor-pack' @ 99.0.0 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to kmf-vendor-pack@100.100.101.
The same advisory and Firewall decision cover 3 recorded versions
100.100.100, 100.100.101, 100.100.106
See all versions of kmf-vendor-pack for other recorded verdicts.
- Avoid installing kmf-vendor-pack@100.100.101. 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: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.