MAL-2026-15906 Malicious code in tailwindcss-animate-styles (npm)
Malicious package
Published
MAL-2026-15906 is a malicious package: tailwindcss-animate-styles (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-15906/ (Markdown: https://insights.sbomify.com/MAL-2026-15906/index.md)
- Package
- tailwindcss-animate-styles
- Registry
- npm
What is MAL-2026-15906?
MAL-2026-15906 is a malicious package in tailwindcss-animate-styles, published on 4 Sep 2026.
Official description
On require() of tailwindcss-animate-styles, index.js runs eval(atob(…)) on a payload appended to the Tailwind plugin. The decoded loader queries public Ethereum RPC endpoints (eth.blockscout.com, 1rpc.io, drpc.org, publicnode, blastapi.io) for transactions from hardcoded wallet 0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a, decodes the destination-address bytes of those transactions into two IPv4 C2 hosts, then fetches XOR-encoded stage-2 code from http://<c2>:443/0x/cls and http://<c2>:443/0x/ls and executes it via eval() and a detached spawn('node', ['-e',…]) with stdio ignored and windowsHide set. Before executing the fetched code the loader pins global.r=require and global.m=module and passes the XOR keys and C2 URLs in, granting the remotely-served stage-2 full Node capabilities (fs, net, child_process, env) on the installer's host. After the eval, the module reads its own source, locates the 'eval(atob("Z2x' region, and rewrites index.js with that region spliced out, erasing the loader from disk after first import.
What should I do about MAL-2026-15906?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.