Malicious Code Detected in commitizen-tailwindcss-buffer-publish Package

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17416: Malicious code in commitizen-tailwindcss-buffer-publish (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 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

The commitizen-tailwindcss-buffer-publish package is a tool designed to facilitate the integration of Tailwind CSS into projects using Commitizen. It helps developers streamline their workflow by automating the publishing process of Tailwind CSS components. However, this package has been identified as containing malicious code, posing significant risks to users who rely on it for their development needs.

Vulnerability Detail

The vulnerability in the commitizen-tailwindcss-buffer-publish package stems from the inclusion of malicious code that can compromise the security of applications using this package. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious nature of the code was discovered by security researchers from Amazon Inspector, highlighting the importance of scrutinizing third-party packages for potential threats.

How To Fix

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

npm uninstall commitizen-tailwindcss-buffer-publish

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 measure, you can avoid using the commitizen-tailwindcss-buffer-publish package until a secure version is released. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The commitizen-tailwindcss-buffer-publish package has been identified as containing malicious code, posing significant risks to users. It is essential to remove the affected package and update to a secure version if available. Utilizing tools like Vulert can help monitor and alert for vulnerabilities in your software.

See every vulnerability recorded for commitizen-tailwindcss-buffer-publish →

Share this vulnerability

FAQ

It is a tool that helps integrate Tailwind CSS into projects using Commitizen, streamlining the publishing process.

The malicious code can potentially lead to unauthorized access and data breaches within applications that use the package.

You can use Vulert, which monitors open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

Remove the affected package and update to a patched version if available. Always keep your packages updated.

Yes, consider using other packages that provide similar functionality without the security risks associated with commitizen-tailwindcss-buffer-publish.

How To Fix

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

npm uninstall commitizen-tailwindcss-buffer-publish

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