Critical Malicious Code Vulnerability in bignumber-tool.js Package

bignumber-tool.js Updated 16 Mar 2026

Summary

16/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1442: Malicious code in bignumber-tool.js (npm). Affected versions are not published. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

bignumber-tool.js is an npm package designed for arbitrary-precision arithmetic in JavaScript. It allows developers to handle large numbers accurately, which is essential for applications requiring high precision calculations. 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 malicious code embedded within the bignumber-tool.js package. This code can fully compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The origin of this issue is linked to a malicious actor who has injected harmful code into the package, making it a significant 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 bignumber-tool.js

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

There are no effective workarounds to mitigate the risks posed by this vulnerability other than removing the package entirely. It is advisable to avoid using bignumber-tool.js until a secure version is released.

Conclusion

The bignumber-tool.js package has been compromised with malicious code, posing a significant security risk to any system using it. Immediate action is required to remove the package and secure sensitive information. Users are advised to monitor their projects for vulnerabilities using tools like Vulert.

See every vulnerability recorded for bignumber-tool.js →

Share this vulnerability

FAQ

bignumber-tool.js is an npm package used for performing arbitrary-precision arithmetic in JavaScript applications.

If bignumber-tool.js is installed, your system may be fully compromised, allowing attackers to access sensitive information.

You should immediately uninstall the package and rotate any sensitive information stored on the affected system.

Currently, there is no patched version available for bignumber-tool.js. It is recommended to avoid using this package until further notice.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground without any signup.

How To Fix

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

npm uninstall bignumber-tool.js

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