Critical Security Breach in @voiceflow/eslint-config: Malicious Code Detected
Summary
MAL-2025-191345: Malicious code in @voiceflow/eslint-config (npm). Affects @voiceflow/eslint-config versions 7.16.4 – 7.16.5. 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
Background
The @voiceflow/eslint-config package is a configuration tool for ESLint, a popular JavaScript linter that helps developers identify and fix problems in their JavaScript code. This package is widely used in projects to maintain code quality and consistency. However, it has recently been compromised, exposing users to significant security risks.
Vulnerability Detail
The vulnerability stems from a malicious code injection by the Sha1-Hulud: The Second Coming NPM worm. This worm is designed to steal tokens and credentials from users and publish them to GitHub. It can propagate itself to other NPM packages owned by the user and establish persistence through a GitHub action. Additionally, the worm has the potential to destroy the user's home directory, making it a severe threat to both personal and organizational data.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @voiceflow/eslint-config
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, users can remove the @voiceflow/eslint-config package from their project until a secure version is confirmed. This can be done by executing: npm uninstall @voiceflow/eslint-config.
Conclusion
The @voiceflow/eslint-config package has been compromised by a malicious worm that poses serious security threats to users. It is essential to take immediate action by updating to the latest version or removing the package entirely. Utilizing tools like Vulert can help in monitoring and preventing future vulnerabilities.
See every vulnerability recorded for @voiceflow/eslint-config →
FAQ
The malicious code is designed to steal sensitive tokens and credentials, potentially leading to unauthorized access to user accounts.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application against this vulnerability using the Vulert playground at Vulert Scanner.
If you have installed the affected version, it is crucial to uninstall it immediately and update to the latest patched version.
Yes, the worm has the potential to destroy the user's home directory, which can lead to significant data loss.
Regularly monitor your dependencies for vulnerabilities using tools like Vulert and keep your packages updated to their latest secure versions.