# MAL-2026-17744: Malicious code in kmf-vendor-pack (npm)


- **Type:** Malicious package
- **Package:** `kmf-vendor-pack` (npm)
- **Published:** 9 Oct 2026

## What is MAL-2026-17744?

MAL-2026-17744 is a malicious package in kmf-vendor-pack, published on 9 Oct 2026. 

### Official description

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.

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.

## What should I do about MAL-2026-17744?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-17744 is a malicious package: kmf-vendor-pack (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-17744/ (Markdown: https://insights.sbomify.com/MAL-2026-17744/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-17744

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-17744/
Summaries are generated and may contain mistakes; the official description above is the record.