Skip to content
AgentProv

2026-06-05 · 2026-Q2

Hades PyPI Worm Wave (Shai-Hulud / Miasma Lineage)

Where did this code come from?

The question layer 4 asks, and failed here.
Fixable
Architectural
Vendor response
Unknown
In the wild
Yes
Actor
Attacker

Target

19 PyPI packages across 37 malicious wheel artifacts, with a secondary cluster targeting computational-biology and MCP developers (IBM X-Force)

Impact

A `*-setup.pth` file runs the payload at Python interpreter startup with no import required; a Bun-based JavaScript stealer harvests credentials for GitHub, npm, PyPI, JFrog, CircleCI, Anthropic, AWS, GCP, Azure, and Kubernetes, plus SSH keys and Vault tokens. Notably, the malware embeds a plain-text prompt injection that tries to trick LLM-based package-analysis tools into rating it safe

Root cause

`.pth` startup-hook execution combined with the Shai-Hulud and Miasma worm lineage; GitHub repo descriptions carried the marker "Hades - The End for the Damned"

Sources

Catalog

Cite this: AgentProv incident record: Hades PyPI Worm Wave (Shai-Hulud / Miasma Lineage) (2026-06-05). https://agentprov.com/incidents/2026-06-05-hades-pypi-worm-wave-shai-hulud-miasma-lineage