Which versions of tailwind-animate-v4 are malicious?

The following npm versions of tailwind-animate-v4 are flagged malicious: 1.1.0, 2.1.0, 2.1.1, 2.1.2. Treat any of these as compromised.

How do I remediate tailwind-animate-v4 if I installed it?

tailwind-animate-v4 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed tailwind-animate-v4 — how do I know if it already compromised me?

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

Yes — tailwind-animate-v4 is associated with the IN-MAL-2026-009102, IN-MAL-2026-009347, IN-MAL-2026-009349, IN-MAL-2026-009590 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-animate-v4 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-animate-v4 (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwind-animate-v4 across your stack and pipelines.

Malicious package

tailwind-animate-v4npm

Malicious code in tailwind-animate-v4 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10073

Immediate action

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

npm uninstall tailwind-animate-v4

What this malware does

The package presents itself as a Tailwind CSS animation plugin and reproduces the legitimate tailwindcss-animate source (including its original author metadata) verbatim in index.js. A long whitespace run at the end of the file visually hides an appended obfuscated loader. On require(), the loader permutation-decodes a string to recover the identifiers 'require', 'module', '__dirname', '__filename', and 'undefined', re-installs them on the global object, then resolves the Function constructor indirectly via a String prototype method whose name is produced by string permutation ('constructor'). It then uses Function() to compile and immediately invoke a large opaque decoded payload (uwg(4261)). This is dynamic execution of an obfuscated blob at library-load time, delivered under a name that mimics the widely used tailwindcss-animate package. Any project that adds this dependency and requires it will execute the hidden payload in the developer/build process, with full access to environment variables, filesystem, and network.

Malicious versions

4 flagged

1.1.02.1.02.1.12.1.2

Indicators of compromise (SHA-256)

90507eebce1061b352492fe3e6bb9673a9b4072c5b35381df73d86b52a342889

e0607a23b0fe8f0cfcaff40e021d2b66893dc14b9389c4fa498bd9f21c2987ab

f84f64cb815db4292d41676cee2df5e9e5ca2953ed29f3bd2288e83d7c3779dc

fd43366b04ea80c2244079c09602623af157ce00cba9ae1837005b97ffe44bdb

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tailwind-animate-v4 (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwind-animate-v4 across your stack and pipelines.
If you installed it — respond
tailwind-animate-v4 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If tailwind-animate-v4 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-animate-v4 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-animate-v4 on npm has been identified as a malicious package (versions 1.1.0, 2.1.0, 2.1.1, 2.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009102IN-MAL-2026-009347IN-MAL-2026-009349IN-MAL-2026-009590

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tailwind-animate-v4-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring