Critical Malicious Code Vulnerability in @voiceflow/base-types Package
Summary
MAL-2025-191335: Malicious code in @voiceflow/base-types (npm). Affects @voiceflow/base-types versions 2.136.2 – 2.136.3. 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/base-types package is a library used in Node.js applications, primarily for managing and defining data types in voice applications. It provides essential functionalities for developers working with voice interfaces. However, this package has been compromised, making it susceptible to severe security threats that can affect user data and application integrity.
Vulnerability Detail
The vulnerability originates from the Sha1-Hulud: The Second Coming NPM worm, which has infected the @voiceflow/base-types package. This malicious code is designed to steal tokens and credentials from users, subsequently publishing this sensitive information to GitHub. The worm can propagate itself to other NPM packages owned by the user and establish persistence through GitHub actions. Additionally, it poses a risk of destroying 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/base-typesIf 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 an immediate workaround, users are advised to temporarily remove the @voiceflow/base-types package from their project until a secure version is confirmed. This can be done using the command: npm uninstall @voiceflow/base-types.
Conclusion
The @voiceflow/base-types package has been compromised by a malicious worm that poses significant security risks. It is crucial for developers using this package to take immediate action by updating to the latest version or removing the package until a fix is confirmed. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for @voiceflow/base-types →
FAQ
The vulnerability involves malicious code that steals 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 real-time. Visit Vulert Scanner to check your application without needing to sign up.
If an immediate update is not possible, consider removing the package from your project as a temporary measure to mitigate risks.
Yes, the consequences include unauthorized access to sensitive information, potential data loss, and propagation of the malicious code to other packages.
Regularly monitor your dependencies for vulnerabilities using tools like Vulert, and keep your packages updated to the latest secure versions.
