tailwindcss-animotionnpm
Advisory published Updated
tailwindcss-animotion is a confirmed malicious npm package (MAL-2026-5637) 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 tailwindcss-animotion (npm)
What this malware does
The package's main entry (dist/index.cjs, with the same code in src/utils/helper.min.js) aliases require to global.r and module to global.m, then deobfuscates two large opaque strings via a custom character-shuffle routine and passes the result to a dynamically-resolved Function constructor (AQq = YWG[OSN] where OSN resolves to 'constructor'). The constructed function is invoked immediately at module load (XZs(7942)). Any consumer that references this package from tailwind.config.js or otherwise require()s it will execute the runtime-decoded code with full Node privileges and a pre-aliased require. A Tailwind CSS plugin (a declarative class generator) has no legitimate need for runtime code generation, global require injection, or multi-layer string obfuscation. The combination of import-time Function() execution, global.r=require aliasing, and custom-shuffle obfuscation of the executed bytes is the canonical shape of a dropper designed to evade static review.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for tailwindcss-animotion (version 1.0.1).
If you installed it — respond
Remove tailwindcss-animotion 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 tailwindcss-animotion 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks tailwindcss-animotion-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.