Malicious code in yakuza0 (npm)
The yakuza0 npm package versions 2.23.40 and 2.23.40-beta.3 contain malicious code that performs outbound network calls to a hardcoded, non-standard host. The code includes runtime fingerprinting of the host environment and uses shell command execution combined with HTTP requests to attacker-controlled endpoints. This behavior indicates potential exfiltration of data and remote command execution risks.
AI Analysis
Technical Summary
The yakuza0 npm package (versions =2.23.40 and =2.23.40-beta.3) includes malicious code embedded in cli/index.js and other files that bind outbound network calls to a hardcoded domain (https://registry-pxnpm.rdc.nfjbill.ren), which is not an official npm registry or publisher domain. The code performs runtime environment fingerprinting using process.versions, and executes shell commands via child_process combined with curl-based HTTP POST/GET requests to attacker-controlled endpoints. These actions occur in top-level module code paths, not user-invoked APIs, suggesting installer-targeted exfiltration and remote command execution capabilities.
Potential Impact
This malicious code can lead to unauthorized data exfiltration from the host environment and potentially allow remote command execution. Because the code runs automatically upon module load, it can compromise systems using these specific yakuza0 package versions without user interaction. The hardcoded attacker-controlled endpoint and shell execution increase the risk of persistent and stealthy compromise.
Mitigation Recommendations
No official patch or remediation information is provided in the source data. Patch status is not yet confirmed — check the vendor advisory or npm registry for current remediation guidance. Until a fix is available, avoid using the affected versions (=2.23.40 and =2.23.40-beta.3) of the yakuza0 package and consider removing or replacing them with trusted versions or alternatives.
Malicious code in yakuza0 (npm)
Description
The yakuza0 npm package versions 2.23.40 and 2.23.40-beta.3 contain malicious code that performs outbound network calls to a hardcoded, non-standard host. The code includes runtime fingerprinting of the host environment and uses shell command execution combined with HTTP requests to attacker-controlled endpoints. This behavior indicates potential exfiltration of data and remote command execution risks.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The yakuza0 npm package (versions =2.23.40 and =2.23.40-beta.3) includes malicious code embedded in cli/index.js and other files that bind outbound network calls to a hardcoded domain (https://registry-pxnpm.rdc.nfjbill.ren), which is not an official npm registry or publisher domain. The code performs runtime environment fingerprinting using process.versions, and executes shell commands via child_process combined with curl-based HTTP POST/GET requests to attacker-controlled endpoints. These actions occur in top-level module code paths, not user-invoked APIs, suggesting installer-targeted exfiltration and remote command execution capabilities.
Potential Impact
This malicious code can lead to unauthorized data exfiltration from the host environment and potentially allow remote command execution. Because the code runs automatically upon module load, it can compromise systems using these specific yakuza0 package versions without user interaction. The hardcoded attacker-controlled endpoint and shell execution increase the risk of persistent and stealthy compromise.
Mitigation Recommendations
No official patch or remediation information is provided in the source data. Patch status is not yet confirmed — check the vendor advisory or npm registry for current remediation guidance. Until a fix is available, avoid using the affected versions (=2.23.40 and =2.23.40-beta.3) of the yakuza0 package and consider removing or replacing them with trusted versions or alternatives.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-13605
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a75f709bf8831d53984ec6c
Added to database: 08/07/2026, 15:17:29 UTC
Last enriched: 08/07/2026, 15:20:47 UTC
Last updated: 08/07/2026, 15:21:26 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.