Critical Malicious Code Vulnerability in @voiceflow/eslint-plugin Package
Summary
MAL-2025-191346: Malicious code in @voiceflow/eslint-plugin (npm). Affects @voiceflow/eslint-plugin versions 1.6.1 – 1.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
Background
The @voiceflow/eslint-plugin is an npm package designed to provide linting capabilities for Voiceflow projects, ensuring code quality and adherence to best practices. However, it has recently been compromised, exposing users to significant security risks due to malicious code embedded within the package.
Vulnerability Detail
The vulnerability originates from the Sha1-Hulud: The Second Coming NPM worm, which has infected versions 1.6.1 and 1.6.2 of the @voiceflow/eslint-plugin package. This malicious payload is capable of stealing tokens and credentials, publishing them to GitHub, and propagating itself to other npm packages owned by the user. Additionally, it can establish persistence through a GitHub action and may even destroy the user's home directory, leading to severe data loss and security breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @voiceflow/eslint-pluginIf 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, users should avoid using the affected versions of the @voiceflow/eslint-plugin package (1.6.1 and 1.6.2) until a secure version is confirmed. Additionally, consider using alternative linting tools or packages that do not have known vulnerabilities.
Conclusion
The @voiceflow/eslint-plugin package has been compromised by a malicious worm, posing serious security risks to users. Immediate action is required to update the package to a secure version and mitigate potential threats. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.
See every vulnerability recorded for @voiceflow/eslint-plugin →
FAQ
Versions 1.6.1 and 1.6.2 of the @voiceflow/eslint-plugin package are affected by this vulnerability.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
If you have installed the affected package, you should immediately update it to the latest version using the command: npm install @voiceflow/eslint-plugin@latest.
Failing to address this vulnerability could result in unauthorized access to your tokens and credentials, potential data loss, and propagation of the malicious code to other packages.
Yes, Vulert provides a service that monitors and alerts you in real-time for open-source vulnerabilities in your software using just the package-lock.json file.
