gpsea has 1 version on PyPI flagged in 1 incident we track. Other versions of this package are not implicated - only the exact versions listed below were named by the source advisories.
Affected versions
Check what you actually have installed with pip show gpsea.
Between 2026-06-05 and 2026-06-08 the Shai-Hulud / Miasma operator hopped to PyPI as "Hades", trojanising ~33 packages across the nanguage bioinformatics cluster (StepSecurity: 19 quarantined projects), monarch-initiative phenotype tooling, and MCP/Flask typosquats. Each ships a *-setup.pth startup hook → Bun credential stealer with cross-platform memory scraping.
Versions named here: 0.9.14
What to do if you installed one of these
Treat the machine as compromised rather than simply upgrading. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.
1.Rotate every credential that machine or CI job could reach - registry tokens, cloud keys, SSH keys, CI secrets - from a different machine.
2.Pin to a version not listed above, then reinstall from a clean lockfile.
3.Clear caches and private mirrors. Artifactory, Nexus, Verdaccio, and devpi routinely keep serving a tarball after the public registry has pulled it.
4.Read the incident write-up above - recommended actions differ per incident, and some have specific indicators of compromise worth grepping your logs for.
Check your whole project
gpsea is one of many packages in these incidents, and it is usually pulled in as a transitive dependency rather than one you installed directly. Paste your requirements.txt to check every dependency at once - it runs in your browser and nothing is uploaded.
Version data comes from the public advisories cited on each incident page. We list only versions those advisories name - we don't infer additional ones. Think this is wrong or incomplete? Tell us.
