kmf-vendor-packnpm
Advisory published Updated
kmf-vendor-pack is a confirmed malicious npm package (MAL-2026-17744) that executes malicious code on install (malicious versions 99.0.0, 100.100.100, 100.100.101…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in kmf-vendor-pack (npm)
What this malware does
[email protected] 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.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for kmf-vendor-pack (4 malicious versions).
If you installed it — respond
Remove kmf-vendor-pack from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If kmf-vendor-pack was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- InvisiRisk, Inc. · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks kmf-vendor-pack-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.