Critical Malicious Code Vulnerability in @voiceflow/logger Package
Summary
MAL-2025-191354: Malicious code in @voiceflow/logger (npm). Affects @voiceflow/logger versions 2.4.2 – 2.4.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/logger package is a logging utility designed for applications built with Voiceflow, providing developers with tools to log and manage application events effectively. However, this package has been compromised, making it susceptible to malicious attacks that can severely impact users' systems.
Vulnerability Detail
The vulnerability originates from a compromise by the Sha1-Hulud: The Second Coming NPM worm, which has infected versions 2.4.2 and 2.4.3 of the @voiceflow/logger package. This malicious payload is capable of stealing sensitive tokens and credentials, publishing them to GitHub, and propagating itself to other NPM packages owned by the user. Additionally, it poses a risk of destroying the user's home directory, leading to potential 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/loggerIf 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/logger package from your project until a secure version is confirmed. Use the following command to uninstall the package: npm uninstall @voiceflow/logger.
Conclusion
The @voiceflow/logger package has been compromised by a malicious worm, posing significant risks to users. It is crucial to update to a secure version and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for @voiceflow/logger →
FAQ
The vulnerability involves malicious code that can steal sensitive information and propagate itself to other packages.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
If you suspect that you have been compromised, immediately remove the affected package and change any credentials that may have been exposed.
Versions 2.4.2 and 2.4.3 are known to be compromised. Always check for the latest version and security advisories.
Yes, Vulert can monitor your open-source dependencies in real-time for vulnerabilities using just your package-lock.json file.
