Malicious Code Detected in zipf Package on PyPI - MAL-2025-6624

zipf Updated 02 Oct 2025

Summary

31/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6624: Malicious code in zipf (PyPI). Affects zipf versions 0.0.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 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 zipf package is a Python library available on the Python Package Index (PyPI) that is designed for statistical analysis and modeling. It is commonly used in data science and machine learning applications due to its functionality in generating Zipf-distributed random variables. However, the package has been identified to contain malicious code, posing significant security risks to users who install it.

Vulnerability Detail

The vulnerability in the zipf package is classified as malicious code injection, which was discovered by ReversingLabs. This malicious code can potentially compromise the security of systems where the package is installed, allowing unauthorized access or data manipulation. The affected version is 0.0.1, and the malicious code was introduced in this specific release, making it critical for users to avoid this version.

How To Fix

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

pip uninstall zipf

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 specific workarounds available for this vulnerability. Users are advised to refrain from using the zipf package until a secure version is released.

Conclusion

The zipf package has been identified to contain malicious code, posing a significant risk to users. It is crucial to uninstall the affected version and monitor for any updates or patches. Users can utilize tools like Vulert to stay informed about vulnerabilities in their applications.

See every vulnerability recorded for zipf →

Share this vulnerability

FAQ

The zipf package is a Python library used for generating Zipf-distributed random variables, commonly utilized in statistical analysis and data science.

The vulnerability involves malicious code embedded in the zipf package, which can lead to unauthorized access and potential data breaches.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

As of now, there is no patched version of the zipf package available. Users should monitor the repository for updates.

If you have installed version 0.0.1 of the zipf package, you should uninstall it immediately using the command: pip uninstall zipf.

How To Fix

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

pip uninstall zipf

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