MalwarePublished 6 Jun 2026Updated 8 Jul 2026

gpsea (PyPI) · Malicious Code

Affects gpseaSource GCVE Database

Malicious package : remove gpsea and rotate any secrets on hosts that installed it.

Data as of 9 Jul 2026, 10:03 UTC

Classification

Malicious package

Published to PyPI · OSV MAL-2026-5316

What to do

Remove gpsea from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Upgrade gpsea to 0.9.15.

Affected software

Product	Affected	Fixed in
PyPIgpsea	Affected >=0.9.14 <0.9.15 =0.9.14	Fixed in 0.9.15

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The PyPI package 'gpsea' version 0.9.14 contains a malicious .pth file that executes a Bun-based credential stealer on every Python startup. This stealer downloads the Bun runtime and runs obfuscated JavaScript code to exfiltrate environment variables, .env files, SSH keys, cloud credentials, and other sensitive data to an attacker-controlled GitHub repository. The campaign is linked to the TeamPCP threat actor and known as Hades/Miasma or Shai-Hulud. The malicious code also attempts persistence and spreading by publishing infected packages using stolen credentials and may perform destructive actions if invalid GitHub tokens are detected. The package includes evasion techniques such as sandbox detection and uses obfuscation to hinder analysis.

Impact

This malicious package compromises the confidentiality of sensitive data by stealing environment variables, credentials (including cloud and SSH keys), .env files, and cryptocurrency assets. It also threatens data integrity and availability by potentially wiping user data if invalid GitHub tokens are detected. The attacker gains persistence and propagation capabilities by publishing infected packages using stolen credentials, increasing the risk of supply chain compromise. The use of obfuscation and sandbox detection complicates detection and mitigation efforts.

Defensive guidance

Users should immediately uninstall version 0.9.14 of the 'gpsea' package and avoid using it. Review and revoke any credentials or tokens that may have been exposed. Conduct a thorough security audit of affected systems, especially focusing on environment variables, SSH keys, cloud credentials, and any other secrets. Exercise caution during cleanup due to the potential destructive payload. Monitor for any unauthorized package publishing activity using compromised credentials. Stay updated with vendor or repository advisories for any official remediation or further guidance.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Jul 2026, 10:03 UTC

Technical details

References

Community reviews