Malicious Code Injection in tailwind-animate-kit: A Security Threat
Summary
MAL-2026-18078: Malicious code in tailwind-animate-kit (npm). Affects tailwind-animate-kit versions 2.0.6 – 2.0.8. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
tailwind-animate-kit is a Tailwind CSS plugin designed to facilitate animations within web applications. It allows developers to easily integrate animations into their projects using Tailwind's utility-first approach. However, recent findings have revealed that certain versions of this package (2.0.6, 2.0.7, 2.0.8) contain malicious code that can compromise the security of applications utilizing this plugin.
Vulnerability Detail
The vulnerability stems from the inclusion of a private scoped package, @jasperquinn/postcss-motion-helpers, which is not accessible on the public npm registry. This package is required in the src/motion.js file, and it executes code when the tailwind.config.js loads the plugin. The malicious code is hidden within this private dependency, which is only retrievable with a specific npm token committed in the lure repository's .npmrc file. This poses a significant risk as it allows for unauthorized code execution when the development server starts, potentially leading to data breaches or other security incidents.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tailwind-animate-kitIf it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As a temporary workaround, you can avoid using the affected versions of tailwind-animate-kit (2.0.6, 2.0.7, 2.0.8) and consider using alternative animation libraries or plugins that do not have known vulnerabilities. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which allows you to check your package-lock.json file for any security issues without requiring code access.
Conclusion
The discovery of malicious code in specific versions of tailwind-animate-kit highlights the importance of vigilance in managing open-source dependencies. By staying informed about vulnerabilities and utilizing tools like Vulert, developers can better protect their applications from potential threats.
See every vulnerability recorded for tailwind-animate-kit →
FAQ
Versions 2.0.6, 2.0.7, and 2.0.8 of tailwind-animate-kit are known to contain the malicious code.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
If you have installed the affected versions, it is recommended to uninstall them and update to a secure version of the package.
The risks include unauthorized code execution, potential data breaches, and compromise of application integrity.
Regularly monitor your dependencies for vulnerabilities using tools like Vulert, and ensure to review package updates and security advisories.
References
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
