Critical Malicious Code Vulnerability in big-numben Package
Summary
MAL-2026-1441: Malicious code in big-numben (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 big-numben package is an npm library designed for handling large numbers in JavaScript applications. It provides various functionalities for mathematical operations involving big integers and floating-point numbers. However, this package has been identified as containing malicious code that compromises the security of any system where it is installed.
Vulnerability Detail
The vulnerability stems from the presence of embedded malicious code within the big-numben 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 origin of this vulnerability is linked to the package being flagged by the GitHub Security Advisory (GHSA-3q53-ww3h-grwr) as malware. Users are advised to treat any system with this package as compromised, as removing the package may not eliminate all malicious software introduced by its installation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall big-numbenIf 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
Currently, there are no effective workarounds to mitigate the risks posed by the big-numben package. The only recommended action is to remove the package entirely from your project and system.
Conclusion
The big-numben package poses a significant security risk due to the embedded malicious code. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help in monitoring and preventing future vulnerabilities.
See every vulnerability recorded for big-numben →
FAQ
You should immediately remove the big-numben package from your project and consider the system 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.
Keeping the big-numben package can lead to unauthorized access to sensitive information and potential control over your system by malicious actors.
As of now, there is no patched version available. The best course of action is to remove the package.
Regularly monitor your dependencies using tools like Vulert, and ensure to keep your packages updated to their latest versions.
