Critical Security Breach in @voiceflow/exception: Malicious Code Detected

@voiceflow/exception Updated 25 Nov 2025

Summary

25/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191347: Malicious code in @voiceflow/exception (npm). Affects @voiceflow/exception versions 1.10.1 – 1.10.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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The @voiceflow/exception package is a JavaScript library used in Node.js applications to handle exceptions and errors effectively. It provides developers with tools to manage error logging and reporting, enhancing application reliability. However, this package has been compromised, exposing users to severe security risks.

Vulnerability Detail

The vulnerability stems from a malicious code injection attributed to the Sha1-Hulud: The Second Coming NPM worm. This worm is designed to steal sensitive tokens and credentials from users, 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, potentially leading to unauthorized access to user accounts and destruction of the user's home directory.

How To Fix

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

npm uninstall @voiceflow/exception

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 should consider removing the affected package from their project until a secure version is confirmed. You can uninstall the package using the command: npm uninstall @voiceflow/exception.

Conclusion

The @voiceflow/exception package has been compromised by a malicious worm that poses serious security threats to users. It is crucial to update the package to the latest version and monitor your applications for any signs of compromise. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for @voiceflow/exception →

Share this vulnerability

FAQ

The malicious code is designed to steal sensitive information such as tokens and credentials, which can lead to unauthorized access to user accounts.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

If you suspect that you have been compromised, immediately change your credentials and tokens, and review your GitHub repositories for any unauthorized changes.

Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software using just your package-lock.json file.

Failing to address this vulnerability can lead to unauthorized access to sensitive data, potential data loss, and damage to your application's integrity.

How To Fix

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

npm uninstall @voiceflow/exception

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