MAL-2026-17776 Malicious code in pay-methods-kmf (npm)
Malicious package
Published
MAL-2026-17776 is a malicious package: pay-methods-kmf (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-17776/ (Markdown: https://insights.sbomify.com/MAL-2026-17776/index.md)
- Package
- pay-methods-kmf
- Registry
- npm
What is MAL-2026-17776?
MAL-2026-17776 is a malicious package in pay-methods-kmf, published on 11 Oct 2026.
Official description
[email protected] is a trivial stub (empty index.js, manifest description 'Frontend utilities') that ships a prebuilt Linux x64 native addon at prebuilds/linux-x64/addon.node and loads it from postinstall.js via require('./prebuilds/linux-x64/addon.node'). On install the postinstall path performs two concurrent exfiltration channels: (1) a DNS beacon that resolves a subdomain of the form <hostname>.<packagename>.db4jlbku53082dmp0d7g3mffj7s7aordk.oast.me against an interactsh/OAST collector, encoding the installer hostname and package name into the DNS label; and (2) the native addon calls gethostname, getpwuid, and getenv and issues an HTTP POST to the hardcoded bare IPv4 endpoint http://64.181.165.115/dc with body shape 'h=<hostname>&u=<user>&p=<package>&r=<npm_config_registry>', leaking the installer's hostname, username, package name, and configured npm registry URL (which may reveal internal/private registry hosts). The package ships no source for the binary, the compiled addon's symbol set (socket/connect/send/fork) is unrelated to any frontend utility, and both the OAST subdomain and the bare-IP POST endpoint are attacker-controlled infrastructure. Dependency-confusion-style version (100.100.102) and the registry-URL field in the exfil payload are consistent with internal-registry reconnaissance.
What should I do about MAL-2026-17776?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.