Malicious Code Injection in tailwind-kinetic: A Critical Vulnerability

tailwind-kinetic Updated 20 Oct 2026

Summary

19/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-18084: Malicious code in tailwind-kinetic (npm). Affects tailwind-kinetic versions 2.0.6 – 2.0.8. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

tailwind-kinetic is a Tailwind CSS plugin designed to enhance animations within web applications. It allows developers to easily integrate animations into their projects using Tailwind's utility-first approach. However, this package has been compromised, leading to serious security concerns due to the inclusion of malicious code that can execute when the plugin is loaded.

Vulnerability Detail

The vulnerability stems from the tailwind-kinetic package versions 2.0.6 and 2.0.8, which were published by a malicious actor as part of a fake job interview campaign. The package requires a private scoped dependency, @aaron205whitmore/postcss-animate-utils, which is not accessible on the public npm registry. This dependency contains malicious code that executes when the tailwind.config.js file loads the plugin, potentially compromising the developer's environment and application. The malicious code is hidden within a private dependency that is only retrievable using a specific npm token, making it difficult to detect.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall tailwind-kinetic

If 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, avoid using the tailwind-kinetic package until a fix is provided. If you need similar functionality, consider using alternative animation libraries that are known to be secure.

Conclusion

The tailwind-kinetic package has been identified as having a critical vulnerability due to the inclusion of malicious code in its dependencies. Developers using this package should take immediate action to update or remove it to protect their applications. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for tailwind-kinetic →

Share this vulnerability

FAQ

tailwind-kinetic is a plugin for Tailwind CSS that allows developers to easily add animations to their web applications.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

If you have installed tailwind-kinetic versions 2.0.6 or 2.0.8, you should update to a patched version or remove the package until a secure version is released.

Using the compromised package can lead to unauthorized code execution in your development environment, potentially exposing sensitive data or compromising your application.

Regularly monitor your dependencies using tools like Vulert, and keep your packages updated to the latest secure versions to minimize the risk of vulnerabilities.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall tailwind-kinetic

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback