Malicious code in leakdeep (PyPI)
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI leakdeep
- Affected
- >= 2.6.4, <= 2.6.4>= 2.5.0, <= 2.5.0>= 2.6.6, <= 2.6.6>= 2.5.2, <= 2.5.2>= 2.6.0, <= 2.6.0>= 2.4.1, <= 2.4.1>= 2.4.5, <= 2.4.5>= 2.6.2, <= 2.6.2>= 3.0.0, <= 3.0.0
- Fixed in
- no fixed version recorded
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record MAL-2026-17921 lists affected ranges: PyPI leakdeep >=2.6.4 =2.5.0 =2.6.6 =2.5.2 =2.6.0 =2.4.1 =2.4.5 =2.6.2 =3.0.0 <=3.0.0
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- not scored
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
--- _-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (c0818f9da5e7dc1413ff1b2a24d3cb53d0b49d06bd802502296d6d8e8e536fee) The package presents itself as an OSINT / credential-leak intelligence framework with a search CLI, but the advertised SearchEngine.search is a stub returning an empty list. Every invocation of the CLI (cli.main) unconditionally starts a background thread via SystemInfo.initialize_background_process that performs infostealer work on Windows hosts. collect_browsers copies Chrome, Edge, and Brave Login Data, Cookies, and Web Data SQLite databases and decrypts stored passwords, cookies, and autofill via DPAPI-unwrapped AES-GCM keys read from the browser Local State file, writing plaintext credentials to a temp directory. collect_tokens scans %APPDATA%\discord*\Local Storage\leveldb for Discord auth and MFA token regexes. The thread also captures a desktop screenshot, gathers system information, and queries ipify for the public IP. The…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from osv record MAL-2026-17921
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: mal-2026-17921 Advisory: Malicious code in leakdeep (PyPI) IDs: mal-2026-17921 Record: https://patchnext.com/advisories/mal-2026-17921 (revision 1, source checked 30 Oct 2026, 06:40 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Unrated Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI leakdeep: affected >= 2.6.4, <= 2.6.4; >= 2.5.0, <= 2.5.0; >= 2.6.6, <= 2.6.6; >= 2.5.2, <= 2.5.2; >= 2.6.0, <= 2.6.0; >= 2.4.1, <= 2.4.1; >= 2.4.5, <= 2.4.5; >= 2.6.2, <= 2.6.2; >= 3.0.0, <= 3.0.0 ## Suggested inspection (read-only) - `python -m pip show leakdeep`: prints the installed version. Run with the environment that serves production active. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on leakdeep. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/MAL-2026-17921 (OSV record MAL-2026-17921 lists affected ranges: PyPI leakdeep >=2.6.4 =2.5.0 =2.6.6 =2.5.2 =2.6.0 =2.4.1 =2.4.5 =2.6.2 =3.0.0 <=3.0.0) Commands are suggestions: review each one before running it.
Loading voting…