Malicious code in xxdxax (npm)
The npm package xxdxax contains obfuscated malicious code designed to target users of a specific WordPress site. When loaded in a browser on noviembrenacional.com, it exfiltrates session data and performs account takeover attacks via CSRF.
- Disclosed
- Last updated
- Blast radius
- Targeted attack against users of a specific WordPress site (noviembrenacional.com); blast radius limited to installations that load the package in a browser context on that domain.
- Ecosystems
- Attack vectors
- Affected entities
- xxdxaxnpm package containing obfuscated malicious browser-side code
The npm package xxdxax was published with intentional malicious code. The package's main file (i.js) is an obfuscated browser-side script that includes a de-obfuscated version (original.js) for reference.\n\nThe payload is gated to execute only when window.location.href contains 'noviembrenacional.com'. When triggered, it exfiltrates page HTML and authenticated session state via fetch with credentials to a hardcoded endpoint at https://canarytokens.com/articles/tags/images/j11lq4swuzvslc96qfi9pmsji/submit.aspx.\n\nThe malicious code then abuses the victim's WordPress session to either delete other user accounts or overwrite the target account's email to nyxalor_25@proton.me and trigger a password reset, resulting in account takeover. Property names, selectors, URLs, and WordPress form field names are obfuscated using unicode escapes and reversed-string techniques to evade casual code review.\n\nThe package is not a general-purpose library but a targeted CSRF/account-hijack exploit. While installation does not execute the payload in Node.js directly (due to browser-only API dependencies and domain gating), the package's sole purpose is offensive action against third-party users of the specific WordPress site.
Indicators of compromise
- Packages
- xxdxax
- Domains
- noviembrenacional.com
- canarytokens.com
Remediation
- Remove the xxdxax package from all npm projects immediately
- Audit npm dependencies for any installations of xxdxax and verify no malicious code was executed
- If the package was loaded in a browser on noviembrenacional.com, reset WordPress account credentials and review account activity for unauthorized changes
- Monitor for account takeover attempts on affected WordPress installations
- Review npm package.json and lock files to ensure xxdxax is not present in any project dependencies
Sources
- GitHub Advisory GHSA-vmq9-f9v2-mpqm · GitHub Advisory Database
Cite this entry
"Malicious code in xxdxax (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 7, 2026; last updated August 7, 2026. https://supplychainattack.org/incident/malicious-code-in-xxdxax-npm-1e9wz4
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in chlklib
Malware was discovered in the npm package chlklib, resulting in full system compromise of any computer with the package installed or running. All affected systems should be considered fully compromised and all secrets and keys rotated immediately from a different computer.
npmCompromised package - 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 - containedcritical
Malware in chai-as-deployer
Malware was discovered in the npm package chai-as-deployer, 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 - containedcritical
Malware in checkout-common-tokens
Malware was discovered in the npm package checkout-common-tokens. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package