Critical Malicious Code Vulnerability in error-ex Package

error-ex Updated 02 Oct 2025

Summary

08/09/2025
CRITICAL
No i
Critical
Not published

MAL-2025-46975: Malicious code in error-ex (npm). Affects error-ex versions 1.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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The error-ex package is a utility for error handling in Node.js applications, providing a simple way to create and manage error objects. It is widely used in the npm ecosystem for its ease of use and functionality. However, a recent compromise has introduced malicious code into version 1.3.3, posing significant security risks to applications that rely on this package.

Vulnerability Detail

The vulnerability stems from the compromise of the error-ex package, where malicious code was intentionally embedded. This malicious code can lead to full control of the affected system, allowing attackers to access sensitive information such as secrets and keys stored on the machine. The origin of this issue is linked to the package being tampered with, and it is classified under CWE-506, indicating the presence of embedded malicious code. Users are advised to consider any system with this package installed as fully compromised.

How To Fix

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

npm uninstall error-ex

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 avoid using the error-ex package altogether until a secure version is confirmed. If your application depends on it, consider refactoring your code to eliminate this dependency.

Conclusion

The error-ex package has been compromised, leading to the introduction of malicious code that poses serious security risks. Users are strongly advised to remove the affected version and update to a secure version immediately. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities in your software effectively.

See every vulnerability recorded for error-ex →

Share this vulnerability

FAQ

You should immediately remove the error-ex package and update to a safe version to mitigate any security risks.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. You can check your application using the Vulert playground without any signup.

Leaving the compromised package installed can lead to unauthorized access to sensitive information and complete control of your system by malicious actors.

Yes, updating to the latest version of the error-ex package will ensure that you are using a version without the malicious code.

Regularly monitor your dependencies using tools like Vulert to identify and address any vulnerabilities in your software.

Related vulnerabilities

Recent vulnerabilities recorded for error-ex.

How To Fix

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

npm uninstall error-ex

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