Critical Malicious Code Vulnerability in leakdeep Package

leakdeep Updated 18 Oct 2026

Summary

18/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17921: Malicious code in leakdeep (PyPI). Affects leakdeep versions 2.5.0 – 2.6.6. 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 leakdeep package is marketed as an OSINT and credential-leak intelligence framework, designed to assist users in searching for leaked credentials. It features a command-line interface (CLI) for executing searches. However, the package has been found to contain malicious code that compromises user data and system integrity.

Vulnerability Detail

The vulnerability originates from the leakdeep package, which deceptively presents itself as a legitimate tool while embedding malicious functionalities. The CLI invokes a background thread that performs unauthorized actions on Windows systems, including collecting sensitive browser data, capturing screenshots, and exfiltrating this information to a hardcoded Discord webhook. The malicious code circumvents user consent and operates under the guise of a non-functional search feature, posing significant risks to user privacy and data security.

How To Fix

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

pip uninstall leakdeep

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 for this vulnerability. The best course of action is to uninstall the leakdeep package entirely and refrain from using any unverified packages that may pose similar risks.

Conclusion

The leakdeep package contains critical malicious code that poses significant risks to user data and system integrity. Users are strongly advised to uninstall the package and consider secure alternatives for their OSINT needs. Continuous monitoring for vulnerabilities is essential to maintain software security.

See every vulnerability recorded for leakdeep →

Share this vulnerability

FAQ

The leakdeep package is a tool intended for OSINT and credential-leak intelligence, providing a CLI for searching leaked credentials.

The vulnerability allows the package to collect sensitive information from your browsers and system without your consent, potentially leading to data breaches.

You should uninstall the leakdeep package immediately using the command pip uninstall leakdeep.

Yes, consider using reputable OSINT tools that are well-reviewed and have a strong security track record.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just the Pipfile.lock. You can 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.

pip uninstall leakdeep

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