Malicious Code Injection in bignum Package - PyPI Vulnerability

bignum Updated 09 Dec 2025

Summary

09/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192391: Malicious code in bignum (PyPI). Affects bignum versions 0.1.0 – 0.1.1. 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

The bignum package, available on PyPI, is designed for handling large numerical computations in Python. It is often used in mathematical applications and data processing tasks. However, this package has been compromised, leading to a significant security vulnerability that allows for the execution of remote malicious code, posing a threat to users and their systems.

Vulnerability Detail

The vulnerability originates from a malicious version of the bignum package, specifically versions 0.1.0 and 0.1.1, which were altered to execute remote scripts without user consent. This malicious behavior includes obfuscation techniques to hide its true intent, making it difficult for users to detect. The implications of this vulnerability are severe, as it can lead to unauthorized access to sensitive data, system compromise, and further exploitation of the affected systems.

How To Fix

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

pip uninstall bignum

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

As a temporary workaround, users can avoid using the bignum package until a patched version is confirmed. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The bignum package has been compromised, leading to a serious vulnerability that allows for the execution of malicious code. Users are urged to update their installations immediately and consider alternative packages to mitigate risks. Utilizing tools like Vulert can help in monitoring and managing such vulnerabilities effectively.

See every vulnerability recorded for bignum →

Share this vulnerability

FAQ

The bignum package is a Python library used for performing calculations with large numbers, commonly utilized in mathematical and data processing applications.

If you have installed versions 0.1.0 or 0.1.1 of the bignum package, your installation is affected. You can check your installed version using 'pip show bignum'.

You should immediately update the bignum package to a safe version using 'pip install --upgrade bignum' and monitor your system for any unusual activity.

Yes, consider using other libraries such as 'decimal' or 'numpy' for handling large numerical computations without the associated risks of the bignum package.

Vulert provides real-time monitoring and alerts for open-source vulnerabilities in your software using the Pipfile.lock. You can check if your application is affected by this vulnerability through the Vulert playground without any signup.

Related vulnerabilities

Recent vulnerabilities recorded for bignum.

How To Fix

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

pip uninstall bignum

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