Critical Malicious Code Vulnerability in @voiceflow/backend-utils Package

@voiceflow/backend-utils Updated 25 Nov 2025

Summary

25/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191334: Malicious code in @voiceflow/backend-utils (npm). Affects @voiceflow/backend-utils versions 5.0.1 – 5.0.2. 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/backend-utils package is a utility library designed for backend development within the Voiceflow ecosystem. It provides essential functions and tools that facilitate the creation of voice applications. However, recent findings have revealed that this package has been compromised, making it susceptible to severe security threats.

Vulnerability Detail

The vulnerability stems from a malicious code injection by the Sha1-Hulud: The Second Coming NPM worm. This worm is capable of stealing sensitive tokens and credentials from users and subsequently publishing them to GitHub. Additionally, it can propagate itself to other NPM packages owned by the user and establish persistence through GitHub actions. The malicious payload poses a significant risk as it may also lead to the destruction of the user's home directory, resulting in potential data loss.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @voiceflow/backend-utils

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 confirmed. Use the following command to uninstall the package: npm uninstall @voiceflow/backend-utils. Additionally, consider using Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The @voiceflow/backend-utils package has been compromised by a malicious worm that poses significant security risks. It is essential for users to update to a secure version of the package and consider using tools like Vulert for ongoing vulnerability monitoring. Taking these steps will help protect sensitive information and maintain the integrity of your applications.

See every vulnerability recorded for @voiceflow/backend-utils →

Share this vulnerability

FAQ

The vulnerability involves malicious code that can steal credentials and tokens, potentially leading to unauthorized access to user accounts.

You can use Vulert to monitor your project for vulnerabilities. The Vulert playground allows you to check for affected packages without requiring any signup.

As a workaround, consider uninstalling the affected package until a secure version is available.

Failing to address this vulnerability could lead to unauthorized access to sensitive information and potential data loss.

Yes, using tools like Vulert can help automate the monitoring of your project for open-source vulnerabilities in real-time.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @voiceflow/backend-utils

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