Critical Malicious Code Vulnerability in @voiceflow/encryption Package

@voiceflow/encryption Updated 25 Nov 2025

Summary

25/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191344: Malicious code in @voiceflow/encryption (npm). Affects @voiceflow/encryption versions 0.3.2 – 0.3.3. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The @voiceflow/encryption package is a Node.js library designed to provide encryption functionalities for applications. It is widely used in projects that require secure data handling. However, this package has been compromised, making it susceptible to severe security threats that can affect users' credentials and data integrity.

Vulnerability Detail

The vulnerability stems from a compromise by the Sha1-Hulud: The Second Coming NPM worm, which has infected versions 0.3.2 and 0.3.3 of the @voiceflow/encryption package. This malicious code is designed to steal tokens and credentials, publishing them to GitHub. Additionally, the worm can propagate itself to other NPM packages owned by the user and may establish persistence through a GitHub action. There is also a risk that it 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/encryption

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 measure, you can remove the affected package from your project until a secure version is released. Use the following command to uninstall the package: npm uninstall @voiceflow/encryption. Additionally, consider using alternative encryption libraries that are not affected by this vulnerability.

Conclusion

The @voiceflow/encryption package has been compromised by a malicious worm, posing significant risks to users' credentials and data. It is essential to take immediate action by updating or removing the affected package and monitoring your applications for vulnerabilities using tools like Vulert.

See every vulnerability recorded for @voiceflow/encryption →

Share this vulnerability

FAQ

The malicious code can steal sensitive tokens and credentials, potentially leading to unauthorized access to user accounts and data breaches.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check if your application is affected without any signup.

If you have installed versions 0.3.2 or 0.3.3 of the package, it is recommended to uninstall them immediately and update to the latest secure version.

Yes, the worm can propagate itself to other NPM packages owned by the user, increasing the risk of widespread compromise.

Yes, the malicious code 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/encryption

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback