Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Malicious code in wallet-tracking (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.

Add to your agent

Affected packages

  • PyPI wallet-tracking

    Affected
    >= 1.0.3
    Fixed in
    no fixed version recorded

Sources

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.

`wallet-tracking` is a PyPI cryptocurrency-wallet information stealer. Its `track_private_key_import()` function takes a private key supplied by the caller and POSTs it in a Discord embed to a hardcoded webhook, with no redaction unless the caller passes `include_private_key=False`. The package itself reads no files or environment variables, and its only network call is a POST to the publisher's Discord webhook, which rotates between releases. Only 1.0.3 through 1.0.6 contain the stealer; 1.0.0 and 1.0.1 ship no package module. --- _-= Per source details. Do not edit below this line.=-_

Source: kam193 (c8740417a04191ae16526d2407f2e97a145d9a34bac6d522317be2f49b328f8e) Package is prepared to send notifications with sensitive data. Update 2026-11-03: reclassified as malicious. The package is used as a dependency in a GitHub project to exfiltrate users' private keys…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record MAL-2026-18443

  2. Revision 1 · created ·

    Published from osv record MAL-2026-18443

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-18443

Advisory: Malicious code in wallet-tracking (PyPI)
IDs: mal-2026-18443
Record: https://patchnext.com/advisories/mal-2026-18443 (revision 2, source checked 4 Nov 2026, 06:20 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 wallet-tracking: affected >= 1.0.3

## Suggested inspection (read-only)
- `python -m pip show wallet-tracking`: 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 wallet-tracking.
- 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-18443 (OSV record MAL-2026-18443 lists affected ranges: PyPI wallet-tracking >=0)
- Verified: https://osv.dev/vulnerability/MAL-2026-18443 (OSV record MAL-2026-18443 lists affected ranges: PyPI wallet-tracking >=1.0.3)

Commands are suggestions: review each one before running it.

Loading voting…