MAL-2026-13605 Malicious code in yakuza0 (npm)
Malicious package
Published
MAL-2026-13605 is a malicious package: yakuza0 (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-13605/ (Markdown: https://insights.sbomify.com/MAL-2026-13605/index.md)
- Package
- yakuza0
- Registry
- npm
What is MAL-2026-13605?
MAL-2026-13605 is a malicious package in yakuza0, published on 7 Aug 2026.
Official description
The package ships code that binds outbound network calls to a hardcoded non-standard host, https://registry-pxnpm.rdc.nfjbill.ren, from cli/index.js (fetch calls at lines 513, 554, 623 alongside a reference to process.versions for host fingerprinting). Additional files server/proxy/tire.js and server/proxy/csrf.js combine child_process usage with curl-based POST/GET operations, mixing shell command execution with outbound HTTP to non-registry endpoints. The destination host is not the npm registry or a documented publisher domain; its name mimics the format of a private npm registry, and it is invoked from top-level module code paths rather than a user-invoked API. The composition — hardcoded attacker-shaped endpoint, runtime process/version fingerprinting, curl-driven POSTs, and child_process shell execution wired to the same network paths — matches the shape of installer-targeted exfiltration and remote command execution.
What should I do about MAL-2026-13605?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.