Which versions of tailwind-anime are malicious?

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

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

tailwind-anime 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-anime — how do I know if it already compromised me?

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

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

Malicious package

tailwind-animenpm

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

Malicious code in tailwind-anime (npm)

MAL-2026-12027

Immediate action

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

npm uninstall tailwind-anime

What this malware does

[email protected] is a typosquat of tailwindcss-animate. Its index.js appends an eval(atob('...')) blob that runs whenever the plugin is required (e.g., when Tailwind loads the plugin during a build). The decoded payload queries multiple Ethereum RPC endpoints (eth.blockscout.com, 1rpc.io/eth, eth.drpc.org, ethereum-rpc.publicnode.com, eth-mainnet.public.blastapi.io) for transactions of address 0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a, reconstructs an IPv4 C2 address from bytes of a transaction's to field, fetches a follow-on payload over HTTP whose body is XOR-decoded from an x-payload-b64 response header, evals it, and then spawns a detached hidden node -e child process ({detached:true, stdio:'ignore', windowsHide:true}). All sensitive strings (require names 'http'/'https'/'child_process', the ETH address, RPC hosts, JSON-RPC method names 'eth_getBlockByNumber'/'eth_getTransactionCount', and C2 paths '/0x/cls' and '/0x/ls') are hidden as \uXXXX escapes inside the base64 blob. The declared purpose is CSS animation utilities; none of this behavior is consistent with that purpose. Installing this package and referencing it in a Tailwind config results in arbitrary remote code execution on the build machine, with the C2 endpoint rotatable by the attacker via new on-chain transactions.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.1.0

Indicators of compromise (SHA-256)

c97bd57720c55b87ce2ff3c9896199234f69ee874e972b7483ffd64a14691a48

fd7605f83f25074e67fa0c72679d47f50fe781dae40e4560ee0a216e91320014

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-anime (version 1.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwind-anime across your stack and pipelines.
If you installed it — respond
tailwind-anime 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-anime 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-anime 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-anime on npm has been identified as a malicious package (version 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-58f3-m5c8-hcrvIN-MAL-2026-013486

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tailwind-anime-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