Critical Malicious Code Vulnerability in node-tailwind Package

node-tailwind Updated 05 Dec 2025

Summary

05/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192310: Malicious code in node-tailwind (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The node-tailwind package is a tool designed for integrating Tailwind CSS into Node.js applications, providing developers with a streamlined way to utilize Tailwind's utility-first CSS framework. However, this package has been compromised, embedding malicious code that poses significant security risks to any system where it is installed.

Vulnerability Detail

The vulnerability originates from the presence of malicious code within the node-tailwind package. This code can fully compromise any computer that has the package installed or running, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code is classified under CWE-506, indicating that it contains embedded malicious code. Users are advised to treat any system with this package as compromised and take immediate action to secure their data.

How To Fix

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

npm uninstall node-tailwind

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 workaround, if you need to continue using Tailwind CSS, consider using an alternative package or directly integrating Tailwind CSS into your project without the compromised node-tailwind package. You can manually include Tailwind CSS by following the official documentation available at https://tailwindcss.com/docs/installation.

Conclusion

The node-tailwind package has been found to contain malicious code that compromises the security of any system where it is installed. Users must take immediate action to remove the package and secure their sensitive information. Monitoring tools like Vulert can help keep your projects safe from future vulnerabilities.

See every vulnerability recorded for node-tailwind →

Share this vulnerability

FAQ

node-tailwind is a package that helps developers integrate Tailwind CSS into their Node.js applications.

The malicious code can compromise your system, allowing unauthorized access to sensitive information and potentially leading to data breaches.

Immediately uninstall the node-tailwind package and rotate any sensitive information stored on the affected system.

No, there is currently no patched version available. The only solution is to remove the package entirely.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall node-tailwind

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