Critical Malicious Code Vulnerability in @voiceflow/test-common Package
Summary
MAL-2025-191378: Malicious code in @voiceflow/test-common (npm). Affects @voiceflow/test-common versions 2.1.1 – 2.1.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/test-common package is a utility library used within the Voiceflow ecosystem, primarily for testing purposes. It provides common functionalities that facilitate the development and testing of voice applications. However, this package has been compromised, exposing users to significant security risks.
Vulnerability Detail
The vulnerability originates from the Sha1-Hulud: The Second Coming NPM worm, which has infected the @voiceflow/test-common package. This malicious code is designed to steal 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 a GitHub action. The worm poses a severe risk as it may also delete the user's home directory, leading to data loss.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @voiceflow/test-commonIf 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 are advised to remove the @voiceflow/test-common package from their projects until a full resolution is implemented. You can uninstall the package using the following command: npm uninstall @voiceflow/test-common.
Conclusion
The @voiceflow/test-common package has been compromised by a malicious NPM worm, posing serious security risks to users. It is crucial to update the package to the latest version and monitor for any signs of compromise. Utilizing tools like Vulert can help in identifying vulnerabilities in your projects.
See every vulnerability recorded for @voiceflow/test-common →
FAQ
The malicious code is designed to steal sensitive information such as tokens and credentials, which can lead to unauthorized access to user accounts.
The worm can propagate itself to other NPM packages owned by the user and establish persistence through GitHub actions.
If you suspect that you have been affected, immediately remove the package and change any compromised credentials. Monitor your accounts for any unauthorized activity.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json file.
Absolutely! You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
