Which versions of animatecss-tailwind-adapter are malicious?

The following npm versions of animatecss-tailwind-adapter are flagged malicious: 2.0.6. Treat any of these as compromised.

How do I remediate animatecss-tailwind-adapter if I installed it?

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

If animatecss-tailwind-adapter 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.

How do I find animatecss-tailwind-adapter across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for animatecss-tailwind-adapter (version 2.0.6).

Malicious package

animatecss-tailwind-adapternpm

Advisory published Oct 7, 2026Updated Oct 8, 2026

animatecss-tailwind-adapter is a confirmed malicious npm package (MAL-2026-17665) that steals credentials and exfiltrates sensitive data (malicious version 2.0.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in animatecss-tailwind-adapter (npm)

MAL-2026-17665

Immediate action

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

npm uninstall animatecss-tailwind-adapter

What this malware does

animatecss-tailwind-adapter 2.0.6 was published to npm on 2026-07-28 by the account grant587holloway. The package is part of a fake job interview campaign that targets developers, using the same method as the "Contagious Interview" campaign. A fake company sends a take-home coding assessment repository. The repository commits a web/.npmrc containing a plaintext npm auth token, and its tailwind.config.js loads this package as a Tailwind CSS plugin. The package presents itself as an Animate.css integration ("A configurable, namespaced Animate.css integration for Tailwind CSS", main plugin.js) but declares a runtime dependency on a private scoped npm package (@aaron205whitmore/postcss-animate-utils) that is not publicly readable, so npm audit and public scanners cannot see it; it only resolves with the token committed in the lure repository. The package has no install scripts, so --ignore-scripts does not help: the code runs when Tailwind loads the config, i.e. on npm run dev / next dev. Public analysis of the earlier package in this chain (animatecss-tailwind-adapter, by Yunus Aydın) reports that the private package contacts an operator-controlled server and runs the code it receives with full Node.js privileges. This is the earlier version of the chain, analysed by Yunus Aydın, whose analysis found the private dependency contacts an operator server and executes the code it returns. Its repository field uses the same GitHub account (sericpieap) as animatecss-tailwind-bridge; neither repository is publicly accessible. Related packages from the same template (same description, main file, dependency list and 2.0.x versioning, each published by a different single-use npm account): animatecss-tailwind-adapter 2.0.6 (2026-07-28, depends on private @aaron205whitmore/postcss-animate-utils), animatecss-tailwind-bridge 2.0.6 (2026-09-13, depends on private @jasperquinn/postcss-motion-helpers) and tailwind-animatecss-uniform 2.0.7 (2026-09-28, depends on private @jasperquinn/postcss-motion-helpers).

Malicious versions

1 flagged

2.0.6

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for animatecss-tailwind-adapter (version 2.0.6).
If you installed it — respond
animatecss-tailwind-adapter 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 animatecss-tailwind-adapter 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. animatecss-tailwind-adapter on npm has been identified as a malicious package (version 2.0.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

npmjs.com

Credits

juanda2222 · finder

Detect & block this

O3 blocks animatecss-tailwind-adapter-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