Critical Malicious Code Vulnerability in transform-jsbi-to-bigint Package
Summary
MAL-2026-1504: Malicious code in transform-jsbi-to-bigint (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 transform-jsbi-to-bigint package is an npm library designed to facilitate the conversion of JSBI objects to BigInt types. It is commonly used in JavaScript applications that require precise numerical operations. However, this package has been compromised, leading to severe security risks for any system utilizing it.
Vulnerability Detail
The vulnerability stems from the presence of embedded malicious code within the transform-jsbi-to-bigint 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 this code is classified under CWE-506, indicating that it contains code that appears to be malicious in nature. Users are advised to treat any system with this package as fully compromised.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall transform-jsbi-to-bigintIf 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, it is recommended to uninstall the transform-jsbi-to-bigint package using the command: npm uninstall transform-jsbi-to-bigint. However, be aware that simply removing the package may not eliminate all malicious software that may have been installed as a result.
Conclusion
The transform-jsbi-to-bigint package has been compromised with malicious code, posing significant risks to any system that utilizes it. Immediate action is required to remove the package and secure any sensitive information. Regular monitoring for vulnerabilities is essential to maintain application security.
See every vulnerability recorded for transform-jsbi-to-bigint →
FAQ
Immediately uninstall the package and rotate any sensitive information stored on the affected system.
You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.
Currently, there is no patched version available. The best course of action is to remove the package entirely.
Failure to address this vulnerability can lead to unauthorized access to sensitive data and complete system compromise.
While most npm packages are safe, it is crucial to monitor for vulnerabilities and use tools like Vulert to stay informed about potential risks.
