Which versions of tailwindcss-3d-animate are malicious?

The following npm versions of tailwindcss-3d-animate are flagged malicious: 0.0.1-security, 1.1.0, 1.2.0, 1.2.1, 1.2.2. Treat any of these as compromised.

How do I remediate tailwindcss-3d-animate if I installed it?

tailwindcss-3d-animate 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 tailwindcss-3d-animate — how do I know if it already compromised me?

If tailwindcss-3d-animate was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is tailwindcss-3d-animate part of a known attack campaign?

Yes — tailwindcss-3d-animate is associated with the GHSA-683p-54mf-9297, IN-MAL-2026-018815, IN-MAL-2026-018812, IN-MAL-2026-019213, IN-MAL-2026-019214 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-3d-animate across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for tailwindcss-3d-animate (5 malicious versions).

Malicious package

tailwindcss-3d-animatenpm

Advisory published Aug 27, 2026Updated Sep 3, 2026

tailwindcss-3d-animate is a confirmed malicious npm package (MAL-2026-14567) that opens a backdoor for remote access (malicious versions 0.0.1-security, 1.1.0, 1.2.0…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tailwindcss-3d-animate (npm)

MAL-2026-14567

Immediate action

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

npm uninstall tailwindcss-3d-animate

What this malware does

index.js re-exports the legitimate tailwindcss-3d plugin and then appends eval(atob("...")) at module top level, so the payload runs on any require('tailwindcss-3d-animate'). The decoded blob is an obfuscator.io string-array/control-flow-flattened bundle (_0x240a rotation, global['r']=require, global['m']=module) that pulls in http/https/zlib/child_process and executes network-fetched code. Decoded strings reveal an Ethereum-address-as-dead-drop staging channel: Etherscan-style ?module=account&action=txlist&address=0xa322E5f3...D311D3080e...9aDC2490Ef queries against public RPC/explorer hosts (drpc.org, eth-mainnet.publicnode, *.blockscout.com) are used to read attacker-controlled on-chain data as the next-stage URL, which is then zlib-inflated and executed via Function/eval and child_process spawn. The package name typosquats the legitimate tailwindcss-3d (same sambauers/tailwindcss-3d repo URL) and reproduces its source verbatim as cover.

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

5 flagged

0.0.1-security1.1.01.2.01.2.11.2.2

Indicators of compromise (SHA-256)

3d1defedbeea471958124829553069330323040f99fc537a12c91f6949a752a9

9d074da2d67a0c2843f1700a1185bd735f842431ce38e0fa6949261aeb24e90d

bc554005eb9004f33d22597b929261d865d4bfe991d0b99d148dc25fffb7e97c

29f2e74c6abebb25eac7ce7c26a2fadd5aa02de37e2dd97df4da2f856b4a5161

6cd755818f8cddee8338a6c19dfb134474fe802f7789e317cb586f02c77f9284

4326aebdde324960b73bef281b5e01cda01eaaa7e7449d97aad124973e93d108

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for tailwindcss-3d-animate (5 malicious versions).
If you installed it — respond
tailwindcss-3d-animate 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 tailwindcss-3d-animate was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. tailwindcss-3d-animate on npm has been identified as a malicious package (versions 0.0.1-security, 1.1.0, 1.2.0, 1.2.1, 1.2.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-683p-54mf-9297IN-MAL-2026-018815IN-MAL-2026-018812IN-MAL-2026-019213IN-MAL-2026-019214

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tailwindcss-3d-animate-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