Which versions of tailwind-animationpack are malicious?

The following npm versions of tailwind-animationpack are flagged malicious: 2.3.7. Treat any of these as compromised.

How do I remediate tailwind-animationpack if I installed it?

tailwind-animationpack establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed tailwind-animationpack — how do I know if it already compromised me?

If tailwind-animationpack 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 tailwind-animationpack part of a known attack campaign?

Yes — tailwind-animationpack is associated with the IN-MAL-2026-014539 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 tailwind-animationpack 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 tailwind-animationpack (version 2.3.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwind-animationpack across your stack and pipelines.

Malicious package

tailwind-animationpacknpm

tailwind-animationpack is a confirmed malicious npm package (MAL-2026-12220) that opens a backdoor for remote access (malicious version 2.3.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tailwind-animationpack (npm)

MAL-2026-12220

Immediate action

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

npm uninstall tailwind-animationpack

What this malware does

src/index.js appends an obfuscated eval(atob(...)) block after a legitimate-looking Tailwind plugin export. The decoded loader hides module names and constants behind \uXXXX escapes, queries Ethereum JSON-RPC endpoints (eth.blockscout.com/api, 1rpc.io/eth, eth.drpc.org, ethereum-rpc.publicnode.com, eth-mainnet.public.blastapi.io) for the latest transaction from hardcoded address 0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a, decodes the transaction's to field into two IPv4 addresses, fetches an XOR-encoded second-stage payload from those hosts, then runs it via eval() and a detached spawn('node', ['-e', payload], {detached:true, stdio:'ignore', windowsHide:true}).unref(). The loader executes whenever a consumer require()s the package, giving the operator of the referenced Ethereum address arbitrary code execution on the installer's machine with a detached child process that survives the parent.

Malicious versions

1 flagged

2.3.7

Indicators of compromise (SHA-256)

63abd5591507bb96b45cdf17209563ccfe52015a0bb8c5258bf3ea8cdc034fb3

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tailwind-animationpack (version 2.3.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwind-animationpack across your stack and pipelines.
If you installed it — respond
tailwind-animationpack establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If tailwind-animationpack 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 tailwind-animationpack 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. tailwind-animationpack on npm has been identified as a malicious package (version 2.3.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014539

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tailwind-animationpack-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database