MAL-2026-14058 Malicious code in adxaa (npm)
Malicious package
Published
MAL-2026-14058 is a malicious package: adxaa (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-14058/ (Markdown: https://insights.sbomify.com/MAL-2026-14058/index.md)
- Package
- adxaa
- Registry
- npm
What is MAL-2026-14058?
MAL-2026-14058 is a malicious package in adxaa, published on 15 Aug 2026.
Official description
The tarball stages an obfuscated JavaScript payload (i.js, with an un-obfuscated copy in original.js) that gates on window.location.href containing 'noviembrenacional.com' and then, using the victim's authenticated session (fetch with credentials:'include'), exfiltrates the current page HTML and username to a canarytokens.com submit endpoint, POSTs to /members/<user>/settings/delete-account/, and for a specific target user overwrites the account email to a hardcoded attacker ProtonMail address ([email protected]) via /my-account/editar-cuenta/ before triggering /wp-login.php?action=lostpassword to seize the account through password reset. The package's declared main (a.js) is absent from the tarball and no lifecycle scripts are declared, so this code does not auto-execute on npm install or require against an arbitrary installer; the payload is staged on the registry for delivery to browsers on the targeted WordPress site.
What should I do about MAL-2026-14058?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.