Which versions of tailwindcss-animate-styles are malicious?

The following npm versions of tailwindcss-animate-styles are flagged malicious: 1.0.9. Treat any of these as compromised.

How do I remediate tailwindcss-animate-styles if I installed it?

tailwindcss-animate-styles is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed tailwindcss-animate-styles — how do I know if it already compromised me?

If tailwindcss-animate-styles was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is tailwindcss-animate-styles part of a known attack campaign?

Yes — tailwindcss-animate-styles is associated with the IN-MAL-2026-019451 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find tailwindcss-animate-styles across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tailwindcss-animate-styles (version 1.0.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwindcss-animate-styles across your stack and pipelines.

Malicious package

tailwindcss-animate-stylesnpm

tailwindcss-animate-styles is a confirmed malicious npm package (MAL-2026-15906) that steals credentials and exfiltrates sensitive data (malicious version 1.0.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tailwindcss-animate-styles (npm)

MAL-2026-15906

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall tailwindcss-animate-styles

What this malware does

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.

Malicious versions

1 flagged

1.0.9

Indicators of compromise (SHA-256)

c51002139fd978b564f7449840b2aafe85ba738c2e392f497f44951070f3643c

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tailwindcss-animate-styles (version 1.0.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwindcss-animate-styles across your stack and pipelines.
If you installed it — respond
tailwindcss-animate-styles is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If tailwindcss-animate-styles was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks tailwindcss-animate-styles before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. tailwindcss-animate-styles on npm has been identified as a malicious package (version 1.0.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019451

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tailwindcss-animate-styles-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database