Critical Malicious Code Vulnerability in ts-big-number Package

ts-big-number Updated 02 Mar 2026

Summary

02/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1134: Malicious code in ts-big-number (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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The ts-big-number package is a JavaScript library used in Node.js applications for handling large numbers with precision. It is commonly utilized in financial applications, data analysis, and any scenario where numerical accuracy is paramount. However, this package has been compromised, introducing malicious code that can lead to severe security risks for any system using it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the ts-big-number 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 code can persist even after the package is removed, making it crucial for users to take immediate action to secure their systems.

How To Fix

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

npm uninstall ts-big-number

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

Currently, there are no workarounds to mitigate the risks associated with the malicious code in the ts-big-number package. The only effective measure is to uninstall the package and secure your system.

Conclusion

The ts-big-number package has been compromised with malicious code, posing significant risks to any system using it. Immediate action is required to uninstall the package and secure sensitive information. Users should also consider alternative libraries for handling large numbers and utilize tools like Vulert for ongoing vulnerability monitoring.

See every vulnerability recorded for ts-big-number →

Share this vulnerability

FAQ

Immediately uninstall the ts-big-number package and rotate any sensitive information stored on the affected system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.

No, there is currently no patched version available for the ts-big-number package. It is recommended to find an alternative library.

Failing to remove the package can lead to unauthorized access to sensitive data and full control of your system by malicious actors.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert and keep your packages updated to the latest secure versions.

How To Fix

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

npm uninstall ts-big-number

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