Critical Malicious Code Vulnerability in tailwindcss-effects-kit Package

tailwindcss-effects-kit Updated 08 Oct 2026

Summary

08/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17686: Malicious code in tailwindcss-effects-kit (npm). Affected versions are not published. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The tailwindcss-effects-kit is an npm package designed to enhance Tailwind CSS with additional effects and utilities. It is widely used in web development to streamline the design process. However, this package has been compromised, leading to significant security concerns for users who have it installed.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the tailwindcss-effects-kit package. This code can fully compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information, including secrets and keys. The origin of this issue is linked to malicious actors who have manipulated the package, making it a serious threat to users and their systems.

How To Fix

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

npm uninstall tailwindcss-effects-kit

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

There are no effective workarounds for this vulnerability. The best course of action is to uninstall the package and secure your system.

Conclusion

The tailwindcss-effects-kit package has been compromised with malicious code, posing a significant risk to users. Immediate action is required to uninstall the package and secure sensitive information. Regular monitoring of your npm packages is essential to prevent such vulnerabilities in the future.

See every vulnerability recorded for tailwindcss-effects-kit →

Share this vulnerability

FAQ

You should immediately uninstall the package and rotate any sensitive information stored on your computer.

You can uninstall the package by running the command: npm uninstall tailwindcss-effects-kit in your terminal.

No, there is currently no patched version available for this package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can also check your application for vulnerabilities using the Vulert playground without any signup.

Failing to remove the package may leave your system vulnerable to unauthorized access and data breaches, as the malicious code can compromise your entire computer.

How To Fix

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

npm uninstall tailwindcss-effects-kit

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