Critical Malicious Code Vulnerability in @voiceflow/semantic-release-config Package
Summary
MAL-2025-191372: Malicious code in @voiceflow/semantic-release-config (npm). Affects @voiceflow/semantic-release-config versions 1.4.1 – 1.4.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/semantic-release-config package is a tool designed to facilitate the automation of versioning and package publishing in JavaScript projects. It integrates with semantic versioning principles to streamline the release process. However, it has recently been compromised, exposing users to severe security risks.
Vulnerability Detail
The vulnerability stems from a malicious payload introduced by the Sha1-Hulud: The Second Coming NPM worm. This worm is capable of stealing tokens and credentials from users and publishing 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 threat as it may also destroy 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/semantic-release-config
If 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 affected package from their project until a secure version is released. This can be done using the command: npm uninstall @voiceflow/semantic-release-config.
Conclusion
The @voiceflow/semantic-release-config package has been compromised by a malicious worm that poses serious security risks. Users must take immediate action to update or remove the package to protect their projects from potential threats. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.
See every vulnerability recorded for @voiceflow/semantic-release-config →
FAQ
The malicious code is designed to steal sensitive tokens and credentials and can also destroy the user's home directory.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities. Check your application using the Vulert playground at Vulert Scanner.
You should uninstall the affected package immediately and check for any signs of compromise in your project.
Users are encouraged to update to the latest version of the package, which may contain security patches. Always refer to the official repository for updates.
Failure to address this vulnerability can lead to unauthorized access to sensitive information, potential data loss, and further propagation of the malicious code.