Critical Security Breach in @voiceflow/commitlint-config: Malicious Code Detected
Summary
MAL-2025-191339: Malicious code in @voiceflow/commitlint-config (npm). Affects @voiceflow/commitlint-config versions 2.6.1 – 2.6.2. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The @voiceflow/commitlint-config package is an npm package designed to enforce commit message conventions in projects using commitlint. It helps maintain a consistent commit history by validating commit messages against specified rules. However, this package has been compromised, making it vulnerable to severe security threats.
Vulnerability Detail
The vulnerability stems from a malicious code injection by the Sha1-Hulud: The Second Coming NPM worm. This worm is capable of stealing tokens and credentials from the user's environment and publishing them to GitHub. It can also propagate itself to other npm packages owned by the user and establish persistence through GitHub actions. Additionally, there is a risk of the worm destroying the user's home directory, leading to significant data loss.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @voiceflow/commitlint-configIf 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, consider removing the @voiceflow/commitlint-config package from your project until a secure version is confirmed. You can do this by executing the command: 'npm uninstall @voiceflow/commitlint-config'. Additionally, monitor your environment for any unauthorized access or changes.
Conclusion
The @voiceflow/commitlint-config package has been compromised by a malicious npm worm, posing serious security risks. It is essential to update the package to a secure version and monitor your environment for any signs of compromise. Utilizing tools like Vulert can help in identifying vulnerabilities in your software.
See every vulnerability recorded for @voiceflow/commitlint-config →
FAQ
The malicious code is part of an npm worm that steals sensitive information and can propagate to other packages.
You can use Vulert, which monitors open-source vulnerabilities in your software. Simply upload your package-lock.json file to the Vulert playground at Vulert Scanner to check for vulnerabilities.
If you suspect that your environment has been compromised, immediately change your tokens and credentials, and review your GitHub repositories for unauthorized changes.
Regularly update your dependencies, use tools like Vulert for real-time monitoring, and conduct security audits on your codebase.
Failing to address this vulnerability can lead to unauthorized access to your credentials, data loss, and potential damage to your project's integrity.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
