Critical Malicious Code Vulnerability in tailwind-config-plugin (npm)

tailwind-config-plugin Updated 02 Oct 2025

Summary

15/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5960: Malicious code in tailwind-config-plugin (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 tailwind-config-plugin is an npm package designed to enhance the configuration of Tailwind CSS, a popular utility-first CSS framework. This plugin allows developers to customize their Tailwind setup easily, providing a streamlined way to manage styles in web applications. However, recent findings have revealed that this package contains embedded malicious code, posing significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the tailwind-config-plugin package. This code can compromise any computer that has the package installed or running, potentially allowing unauthorized access to sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as it may lead to full control of the affected system by an external entity, making it imperative for users to act swiftly to mitigate the risks.

How To Fix

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

npm uninstall tailwind-config-plugin

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

Currently, there are no known workarounds that can effectively mitigate the risks posed by the malicious code in the tailwind-config-plugin. The only recommended action is to remove the package entirely.

Conclusion

The tailwind-config-plugin package has been identified as containing malicious code that poses a significant security threat. Users are advised to remove the package immediately and monitor their systems for any signs of compromise. Utilizing tools like Vulert can help in identifying vulnerabilities in your software.

See every vulnerability recorded for tailwind-config-plugin →

Share this vulnerability

FAQ

You should remove the tailwind-config-plugin package immediately and rotate any secrets or keys stored on the affected computer.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring access to the code.

Currently, there are no effective workarounds. The only solution is to remove the package.

Failure to address this vulnerability could lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

You can find detailed information about this vulnerability on the GitHub repository and the Open Source Vulnerability database.

How To Fix

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

npm uninstall tailwind-config-plugin

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