Critical Malicious Code Vulnerability in @voiceflow/storybook-config Package
Summary
MAL-2025-191376: Malicious code in @voiceflow/storybook-config (npm). Affects @voiceflow/storybook-config versions 1.2.2 – 1.2.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/storybook-config package is a tool used in the development of user interfaces, particularly for managing Storybook configurations. It is designed to streamline the process of building and testing UI components. However, this package has been compromised, making it susceptible to severe security risks that can affect developers and their projects.
Vulnerability Detail
The vulnerability stems from a malicious code injection by the Sha1-Hulud: The Second Coming NPM worm. This worm is designed to steal tokens and credentials from users, publishing them to GitHub. It can propagate itself to other NPM packages owned by the user and establish persistence through a GitHub action. Additionally, there is a risk that the worm may destroy the user's home directory, leading to significant data loss and operational disruption.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @voiceflow/storybook-configIf 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, avoid using the affected versions (1.2.2 and 1.2.3) of the @voiceflow/storybook-config package until a secure version is available. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The @voiceflow/storybook-config package has been compromised by a malicious NPM worm, posing significant risks to developers and their projects. It is essential to update to a secure version of the package and implement monitoring tools like Vulert to safeguard against future vulnerabilities.
See every vulnerability recorded for @voiceflow/storybook-config →
FAQ
The affected versions are 1.2.2 and 1.2.3.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit the Vulert playground at Vulert Scanner to check your application without any signup.
If you suspect that your tokens or credentials have been compromised, immediately revoke them and generate new ones. Review your codebase for any unauthorized changes.
Regularly update your dependencies, use tools like Vulert to monitor for vulnerabilities, and conduct security audits on your codebase.
The consequences include unauthorized access to sensitive information, potential data loss, and the propagation of malicious code to other projects.
