Skip to content
OpenAdvisories
Malicious MAL-2026-12027 GHSA-58f3-m5c8-hcrv

tailwind-anime

npm package · versions 1.1.0, 1.1.1, 1.0.0, 0.0.1

Reported Aug 4, 2026 · Updated Aug 5, 2026

If this package is installed

Remove it, treat the machine (or CI runner) as compromised, and rotate every secret, token and key it could access — from a different, clean machine.

Details

Source: amazon-inspector (fd7605f83f25074e67fa0c72679d47f50fe781dae40e4560ee0a216e91320014)
tailwind-anime@1.1.0 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.

Source: ghsa-malware (c97bd57720c55b87ce2ff3c9896199234f69ee874e972b7483ffd64a14691a48)
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.