Critical Malicious Code Vulnerability in bign.ts Package
Summary
MAL-2026-1357: Malicious code in bign.ts (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 bign.ts package is a JavaScript library designed for arbitrary-precision arithmetic in Node.js and browsers. It allows developers to perform calculations with large numbers that exceed the limits of standard JavaScript number types. However, this package has been compromised, leading to significant security risks for any application that utilizes it.
Vulnerability Detail
The vulnerability stems from the presence of malicious code embedded within the bign.ts package. This code can fully compromise any computer where the package is installed, allowing unauthorized access to sensitive information, including secrets and keys. The origin of this issue is linked to a malicious actor who has inserted harmful code into the package, making it a severe threat to users and their systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall bign.tsIf 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 bign.ts package altogether and look for alternative libraries that provide similar functionality without the associated risks.
Conclusion
The bign.ts package has been identified as containing malicious code, posing a significant risk to users. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help monitor for vulnerabilities in your software.
See every vulnerability recorded for bign.ts →
FAQ
You should remove the bign.ts package from your project and rotate any sensitive information stored on the affected system.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.
Currently, there is no safe version of bign.ts available. It is recommended to remove the package entirely.
Failing to address this vulnerability could lead to unauthorized access to sensitive data, potential data breaches, and complete system compromise.
Yes, consider using alternative libraries that provide similar functionality without the security risks associated with bign.ts.
