Malicious code in yakuza0 (npm)
The npm package yakuza0 contained malicious code that exfiltrates system information and executes remote commands via hardcoded attacker-controlled endpoints. The package performed unauthorized outbound network calls to a non-standard registry host, combined with process fingerprinting and shell command execution.
- Disclosed
- Last updated
- Blast radius
- All npm users who installed yakuza0
- Ecosystems
- Attack vectors
- Affected entities
- yakuza0npm package containing malicious code
The npm package yakuza0 was found to contain malicious code designed to exfiltrate data and enable remote command execution. The package shipped code in cli/index.js that binds outbound network calls to a hardcoded non-standard host at https://registry-pxnpm.rdc.nfjbill.ren, with fetch calls at lines 513, 554, and 623 alongside references to process.versions for host fingerprinting.\n\nAdditional malicious functionality was embedded in server/proxy/tire.js and server/proxy/csrf.js, which combine child_process usage with curl-based POST/GET operations. These files mix shell command execution with outbound HTTP requests to non-registry endpoints, creating a mechanism for both data exfiltration and remote command execution.\n\nThe destination host mimics the format of a private npm registry but is not the official npm registry or any documented publisher domain. The malicious code is invoked from top-level module code paths rather than through user-invoked APIs, meaning it executes automatically upon package installation or import.\n\nThe incident was identified by Amazon Inspector and credited to the OpenSSF malicious-packages project.
Indicators of compromise
- Packages
- yakuza0
- Domains
- registry-pxnpm.rdc.nfjbill.ren
Remediation
- Immediately uninstall yakuza0 from all systems
- Audit npm package.json files and lock files for yakuza0 dependencies
- Review system logs and network traffic for connections to https://registry-pxnpm.rdc.nfjbill.ren or related attacker infrastructure
- Regenerate any credentials or secrets that may have been exposed on affected systems
- Scan affected systems for signs of unauthorized command execution or data exfiltration
- Update to a clean version of any legitimate package yakuza0 was intended to replace, if applicable
Sources
- GitHub Advisory GHSA-j3c6-qq5r-wp79 · GitHub Advisory Database
Cite this entry
"Malicious code in yakuza0 (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 7, 2026; last updated August 7, 2026. https://supplychainattack.org/incident/malicious-code-in-yakuza0-npm-0gv9dt
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malware in alphazone
The npm package alphazone contained malware that provided full system compromise to attackers. Any computer with the package installed or running should be considered fully compromised.
npmCompromised package - activecritical
Malware in celonix-otp-react
Malware discovered in the npm package celonix-otp-react. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - resolvedcritical
Malicious code in bcc-design (npm)
bcc-design@9999.0.0 on npm is a dependency-confusion beacon package with no legitimate functionality. Its postinstall script exfiltrates the installer's hostname and system metadata to an attacker-controlled IP endpoint.
npmDependency confusionCompromised package - containedcritical
Malware in blastradar
Malware was discovered in the npm package blastradar, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.
npmCompromised package