Which versions of tailwind-animationgroup are malicious?

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

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

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

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

Yes — tailwind-animationgroup is associated with the IN-MAL-2026-014538 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-animationgroup 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-animationgroup (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-animationgroup across your stack and pipelines.

Malicious package

tailwind-animationgroupnpm

tailwind-animationgroup is a confirmed malicious npm package (MAL-2026-12219) 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-animationgroup (npm)

MAL-2026-12219

Immediate action

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

npm uninstall tailwind-animationgroup

What this malware does

src/index.js appends an eval(atob(...)) blob after the tailwind plugin export. On any require()/import of the package, the decoded loader queries Ethereum RPC and blockscout endpoints for the latest transaction from a hardcoded address (0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a), derives two IPv4 C2 endpoints from bytes of that transaction, and issues HTTP requests to http://<ip>:443/0x/cls and http://<ip>:443/0x/ls. The responses carry an XOR-encoded payload in an x-payload-b64 header; one payload is eval'd in-process and the other is executed via child_process.spawn('node', ['-e', <code>], {detached: true, stdio: 'ignore', windowsHide: true}).unref(). Strings such as 'child_process', 'http', 'https', 'GET', 'HEAD', 'spawn', and the endpoint paths are hidden with \uXXXX unicode escapes and layered base64 wrapping. The Tailwind animation plugin surface is a decoy; the C2 address rotates via on-chain lookups, so the delivered second-stage is arbitrary and mutable.

Malicious versions

1 flagged

2.3.7

Indicators of compromise (SHA-256)

aa7ac62a4a5dbe9acfdc813215213c698a79588f96614191505e41bf116c9c66

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-animationgroup (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-animationgroup across your stack and pipelines.
If you installed it — respond
tailwind-animationgroup 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-animationgroup 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-animationgroup 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-animationgroup 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-014538

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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