Critical Malicious Code Vulnerability in @voiceflow/verror Package
Summary
MAL-2025-191382: Malicious code in @voiceflow/verror (npm). Affects @voiceflow/verror versions 1.1.4 – 1.1.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/verror package is a utility for handling and formatting error messages in Node.js applications. It is widely used in various projects for its simplicity and effectiveness in error management. However, it has recently been compromised, making it susceptible to severe security threats that can affect developers and their applications.
Vulnerability Detail
The vulnerability originates from a malicious NPM worm known as Sha1-Hulud: The Second Coming, which has infected the @voiceflow/verror package. This worm is designed to steal sensitive tokens and credentials from users and publish them to GitHub. Additionally, it can propagate itself to other NPM packages owned by the user and establish persistence through GitHub actions. The worm poses a significant risk as it may also delete the user's home directory, leading to potential data loss.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @voiceflow/verrorIf 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, you can remove the @voiceflow/verror package from your project until a secure version is available. Use the following command: npm uninstall @voiceflow/verror. Additionally, ensure that your environment variables and sensitive information are not exposed in your codebase.
Conclusion
The @voiceflow/verror package has been compromised by a malicious NPM worm, posing significant risks to developers and their applications. It is essential to take immediate action by updating or removing the package to mitigate these risks. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in the future.
See every vulnerability recorded for @voiceflow/verror →
FAQ
The vulnerability involves malicious code that steals tokens and credentials, potentially leading to unauthorized access to user accounts and data.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check your application without needing to sign up.
If you cannot update the package, consider removing it from your project and looking for alternative packages that provide similar functionality.
The malicious code can propagate to other NPM packages owned by the user and establish persistence through GitHub actions, making it a persistent threat.
The consequences include unauthorized access to sensitive information, potential data loss, and the risk of further spreading the malicious code to other projects.
