Critical Malicious Code Vulnerability in error-fallback Package
Summary
MAL-2025-192985: Malicious code in error-fallback (npm). Affected versions are not published. 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 error-fallback package is an npm module designed to provide fallback mechanisms for error handling in JavaScript applications. It is commonly used in various projects to ensure that applications can gracefully handle errors without crashing. However, this package has been identified as containing malicious code that compromises the security of any system it is installed on.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within the error-fallback package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code is classified under CWE-506, indicating that it contains embedded malicious code. Users are advised to treat any system running this package as fully compromised, as removing the package may not eliminate all traces of the malicious software.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall error-fallbackIf 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 workaround, you should cease using the error-fallback package and replace it with a secure alternative for error handling in your application. Review your codebase to identify any dependencies on this package and refactor your error handling logic accordingly.
Conclusion
The error-fallback package has been identified as containing malicious code that poses a significant security risk. Users are strongly advised to remove the package, rotate any compromised secrets, and consider alternative solutions for error handling in their applications. Regular monitoring for vulnerabilities using tools like Vulert can help maintain the security of your software.
See every vulnerability recorded for error-fallback →
FAQ
Immediately remove the error-fallback package from your project and rotate any sensitive information that may have been compromised.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
While removing the package is crucial, there is no guarantee that all malicious software will be eliminated. It is advisable to conduct a thorough security audit of your system.
Failing to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and complete control of your system by malicious actors.
Yes, consider using other well-reviewed error handling libraries that do not have a history of security issues.
