Which versions of tailwind-animates are malicious?

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

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

Remove tailwind-animates from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

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

Yes — tailwind-animates is associated with the GHSA-3cr6-gpr8-pjfm, IN-MAL-2026-008625 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-animates across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for tailwind-animates (version 1.0.1).

Malicious package

tailwind-animatesnpm

Advisory published Jul 2, 2026Updated Jul 8, 2026

tailwind-animates is a confirmed malicious npm package (MAL-2026-6727) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tailwind-animates (npm)

MAL-2026-6727

Immediate action

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

npm uninstall tailwind-animates

What this malware does

The package was found to contain malicious code or consuming dependency that contains malicious code

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

1 flagged

1.0.1

Indicators of compromise (SHA-256)

976a38db77a7958d63f884cc2b09a6a7bf725deb719d632d7442e39503b43fb0

4da1c506d3ce6cb8bac934a9b51e967b8c2965de414adb1193ba38a64934a78c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for tailwind-animates (version 1.0.1).
If you installed it — respond
Remove tailwind-animates from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If tailwind-animates 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. tailwind-animates on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-3cr6-gpr8-pjfmIN-MAL-2026-008625

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tailwind-animates-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database