MAL-2026-13469 Malicious code in xxdxax (npm)
Malicious package
Published
MAL-2026-13469 is a malicious package: xxdxax (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-13469/ (Markdown: https://insights.sbomify.com/MAL-2026-13469/index.md)
- Package
- xxdxax
- Registry
- npm
What is MAL-2026-13469?
MAL-2026-13469 is a malicious package in xxdxax, published on 6 Aug 2026.
Official description
The package's main file (i.js) is an obfuscated browser-side script — its de-obfuscated form is shipped alongside as original.js — that gates execution on window.location.href containing 'noviembrenacional.com'. When loaded in a page on that host, it exfiltrates page HTML and authenticated session state (via fetch with credentials:'include') to a hardcoded https://canarytokens.com/articles/tags/images/j11lq4swuzvslc96qfi9pmsji/submit.aspx endpoint, then abuses the victim's WordPress session on /my-account/editar-cuenta/ to either delete other users' accounts or overwrite the target account's email to [email protected] and trigger a password reset, resulting in account takeover. Property names, selectors, URLs, WordPress form field names (e.g., wpnonce, account_first_name), the attacker email, and the target hostname are hidden via \uXXXX unicode escapes and reversed-string tricks ("ecnonpw".split('').reverse().join('')) to conceal the payload from casual review. The package is not a general-purpose library; it is a targeted CSRF / account-hijack exploit packaged as an npm module. Installing the package does not execute the payload against the Node installer directly (the code uses browser-only APIs and is gated to a specific site), but the package's shipped purpose is offensive action against third-party users of a specific WordPress site.
What should I do about MAL-2026-13469?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.