Which versions of tailwind-animationbased are malicious?

Every published version of tailwind-animationbased on npm is considered malicious. Remove the package entirely.

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

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

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

Yes — tailwind-animationbased is associated with the GHSA-wp25-rrp2-mfgj 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-animationbased 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-animationbased (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwind-animationbased across your stack and pipelines.

Malicious package

tailwind-animationbasednpm

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

MAL-2025-192640

Immediate action

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

npm uninstall tailwind-animationbased

What this malware does

The package tailwind-animationbased was found to contain 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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

8f363e7f1df253579ca3343007b5af1dd7e80516e2ccf58d13fd3fff5ab3aa47

ac7eef2c8a93c095a7c203eb12ac4dab149ff712b00eef96d4a8febb468710f0

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tailwind-animationbased (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwind-animationbased across your stack and pipelines.
If you installed it — respond
Remove tailwind-animationbased 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-animationbased 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-animationbased 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-animationbased on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-wp25-rrp2-mfgj

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

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