Which versions of tailwind-animation-founder are malicious?

The following npm versions of tailwind-animation-founder are flagged malicious: 2.5.7. Treat any of these as compromised.

How do I remediate tailwind-animation-founder if I installed it?

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

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

Yes — tailwind-animation-founder is associated with the IN-MAL-2026-014547 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-animation-founder 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-animation-founder (version 2.5.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwind-animation-founder across your stack and pipelines.

Malicious package

tailwind-animation-foundernpm

tailwind-animation-founder is a confirmed malicious npm package (MAL-2026-12218) that steals credentials and exfiltrates sensitive data (malicious version 2.5.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tailwind-animation-founder (npm)

MAL-2026-12218

Immediate action

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

npm uninstall tailwind-animation-founder

What this malware does

The package publishes as 'tailwind-animation-founder' while its README, homepage, and npm badges point to a differently-named upstream ('tailwindcss-animationfound'), indicating a typosquat identity. src/index.js appends an obfuscated IIFE after a legitimate-looking Tailwind plugin export. The trailing block pulls http, https, and child_process.spawn into globals, uses a length-based string-shuffle routine to reconstruct the identifier 'constructor', instantiates a Function from a shuffle-decoded source blob, and immediately invokes it. The executable payload is only readable after runtime decoding, so the plugin performs opaque code execution the moment a build tool runs require('tailwind-animation-founder'). The combination of obfuscation, networking primitives (http/https), process-spawn capability, and Function-constructor evaluation on the main entry is the shape of a dropper/stealer, not a Tailwind utility plugin.

Malicious versions

1 flagged

2.5.7

Indicators of compromise (SHA-256)

212392bc085368a2f4227f1cba627c6dd4629855bb5f3aa3529931d35f13ed21

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-animation-founder (version 2.5.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwind-animation-founder across your stack and pipelines.
If you installed it — respond
tailwind-animation-founder 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-animation-founder 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-animation-founder 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-animation-founder on npm has been identified as a malicious package (version 2.5.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014547

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tailwind-animation-founder-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

Explore

All malware advisories How O3 detects malware Vulnerability database