Which versions of tailwind-minanimated are malicious?

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

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

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

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

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

Malicious package

tailwind-minanimatednpm

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

MAL-2026-15634

Immediate action

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

npm uninstall tailwind-minanimated

What this malware does

src/index.js appends a hidden payload after ~9KB of whitespace padding that decodes and runs via eval(atob(...)) whenever the package is required (the README instructs users to require('tailwind-minanimated') from tailwind.config.js). The payload queries the Ethereum Blockscout API (https://eth.blockscout.com/api) for the latest transaction from hardcoded sender address 0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a, decodes the destination address into two IPv4 addresses, fetches second-stage JavaScript from those hosts at paths /0x/cls and /0x/ls, XOR-decrypts the response with hardcoded keys, and executes the result via eval and a detached spawn('node', ['-e', code], {detached:true, stdio:'ignore'}).unref(). The blockchain-based C2 resolution allows the attacker to rotate infrastructure without republishing the package. The tailwind plugin functionality is a cover for the loader.

Malicious versions

1 flagged

2.3.7

Indicators of compromise (SHA-256)

78b5ade01536ccd988686907972ea2cc90b1c4abb91921604bea47ab7a53c7e2

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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