PYSEC-2026-610
Vulnerability from pysec - Published: 2026-07-01 22:08 - Updated: 2026-07-01 22:08
VLAI?
Details
Part of the "Hades" wave of the Shai-Hulud supply-chain campaign. On 2026-06-08, malicious phantom releases of ufish were published to PyPI using stolen credentials. The package executes a bundled JavaScript payload (via the Bun runtime) on import that harvests and exfiltrates credentials and attempts self-propagation. This entry is a summary; behavior may not be fully characterized here. See the linked references for detailed analysis and indicators of compromise.
Impacted products
| Name | purl | ufish | pkg:pypi/ufish |
|---|
Aliases
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "ufish",
"purl": "pkg:pypi/ufish"
},
"versions": [
"0.1.2",
"0.1.3"
]
}
],
"aliases": [
"MAL-2026-5285"
],
"details": "Part of the \"Hades\" wave of the Shai-Hulud supply-chain campaign. On 2026-06-08,\nmalicious phantom releases of ufish were published to PyPI using stolen\ncredentials. The package executes a bundled JavaScript payload (via the Bun\nruntime) on import that harvests and exfiltrates credentials and attempts\nself-propagation. This entry is a summary; behavior may not be fully\ncharacterized here. See the linked references for detailed analysis and\nindicators of compromise.\n",
"id": "PYSEC-2026-610",
"modified": "2026-07-01T22:08:28Z",
"published": "2026-07-01T22:08:28Z",
"references": [
{
"type": "EVIDENCE",
"url": "https://inspector.pypi.io/project/ufish/0.1.3/packages/c9/3d/62d93be789de98b0c3c23c5b3dfcf3f569d21984fed2613057d6dbae0daa/ufish-0.1.3-py3-none-any.whl//ufish-setup.pth"
},
{
"type": "ARTICLE",
"url": "https://www.endorlabs.com/learn/shai-hulud-hades-wave-hits-six-pypi-bioinformatics-packages"
},
{
"type": "ARTICLE",
"url": "https://www.stepsecurity.io/blog/the-hades-campaign-pypi-packages"
}
],
"summary": "Malicious code in ufish (PyPI)"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…