Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Malicious code in py-worm (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 py-worm

    Affected
    >= 0.1.0, <= 0.1.0>= 2.0.0, <= 2.0.0>= 2.0.1, <= 2.0.1
    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.

Importing py-worm's `agentaix` module downloads a mutable Python file from `https://raw.githubusercontent.com/anonrider404/pypl/refs/heads/main/readme.txt` to a temporary `.py` file and launches it without a visible console on Windows. Versions 0.1.0 and 2.0.0 do this directly during import; version 2.0.1 starts a daemon thread during import to perform the same action. The package's CLI and GUI entry points import this module. The remote file's Git history contains a Windows remote file management client that registers persistence through an HKCU Run entry, polls `https://googleforum.pythonanywhere.com` for commands, and supports file upload, download, deletion, and command execution. An earlier remote-file revision is byte-identical to the `readme.txt` payload reported in MAL-2026-17752 (`agentaix`); the 39,931-byte `agentaix/gui.py` is also byte-identical across that package and all py-worm releases. The remote file is mutable; its contents at the time of any particular victim…

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

    Published from osv record MAL-2026-17883

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

Advisory: Malicious code in py-worm (PyPI)
IDs: mal-2026-17883
Record: https://patchnext.com/advisories/mal-2026-17883 (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 py-worm: affected >= 0.1.0, <= 0.1.0; >= 2.0.0, <= 2.0.0; >= 2.0.1, <= 2.0.1

## Suggested inspection (read-only)
- `python -m pip show py-worm`: 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 py-worm.
- 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-17883 (OSV record MAL-2026-17883 lists affected ranges: PyPI py-worm >=0.1.0 =2.0.0 =2.0.1 <=2.0.1)

Commands are suggestions: review each one before running it.

Loading voting…