Critical Malicious Code Vulnerability in @voiceflow/chat-types Package
Summary
MAL-2025-191337: Malicious code in @voiceflow/chat-types (npm). Affects @voiceflow/chat-types versions 2.14.58 – 2.14.59. 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/chat-types package is a library used in Node.js applications for building chat interfaces. It provides developers with tools and types to facilitate the integration of chat functionalities. However, this package has been compromised, making it susceptible to a serious security threat that can affect user credentials and system integrity.
Vulnerability Detail
The vulnerability originates from a malicious NPM worm known as Sha1-Hulud: The Second Coming. This worm injects malicious code into the @voiceflow/chat-types package, which can steal tokens and credentials from users. It also has the capability to publish these stolen credentials to GitHub, propagate itself to other NPM packages owned by the user, and establish persistence through GitHub actions. Furthermore, there is a risk that the worm could destroy the user's home directory, leading to significant data loss.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @voiceflow/chat-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 a temporary workaround, users can remove the @voiceflow/chat-types package from their project until a secure version is confirmed. This can be done by executing the following command: npm uninstall @voiceflow/chat-types.
Conclusion
The @voiceflow/chat-types package has been compromised by a malicious NPM worm, posing significant risks to user credentials and system integrity. It is essential for developers to update to the latest secure version of the package or remove it temporarily to mitigate these risks. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for @voiceflow/chat-types →
FAQ
The vulnerability involves malicious code that can steal user tokens and credentials, potentially leading to unauthorized access to user accounts.
You can check if your application is affected by using Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to analyze your package-lock.json file.
If immediate updates are not possible, consider removing the package from your project as a temporary measure to prevent exploitation.
Yes, the impacts include the theft of sensitive credentials, potential data loss, and unauthorized access to other NPM packages owned by the user.
Yes, using Vulert, you can monitor your application for vulnerabilities without needing to access the code or installation. It uses the package-lock.json file for real-time alerts.
