Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious packageDiscovered by O3 Security

gpseaPyPI

Malicious code in gpsea (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-5316
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall gpsea

What this malware does

The package gpsea version 0.9.14 contains a malicious .pth file (gpsea-setup.pth) that executes a Bun-based credential stealer on every Python startup via CPython's site.py exec() mechanism. The payload downloads the Bun runtime from the official GitHub release page, then runs an obfuscated JavaScript stealer that exfiltrates environment variables, .env files, SSH keys, and cloud credentials to an attacker-controlled GitHub repository. This is part of the Hades/Miasma campaign (also called Shai-Hulud), attributed to the TeamPCP threat actor.

Novel finding: gpsea/_index.js (same campaign) embeds CBRN-level dangerous-content text to trigger AI safety refusals in LLM-based security scanners, causing them to skip the file entirely.

C2 IP: 20.207.73.82 Sentinel file: /tmp/.bun_ran MITRE ATT&CK: T1546.018

Versions 0.9.14 were compromised.

Compromised packages start an obfuscated infostealer. The infostealer is a heavily obfuscated JavaScript code executed using Bun runtime on Python startup. It collectes all kinds of sensitive data, including API keys, credentials to package repositories, cryptocurrency assets, password manager data. Infostealer actively queries online services to collect additional secrets as well as attempts to gain persistence and spread further by publishing infected packages using collected credentials. Data are exfiltrated likely using Github. The code seems to threaten to wipe the user's data if it detects invalid GitHub tokens. Cleanup should be done with caution.

It seems to be related to the recent Mini Shai Hulud campaign.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-06-compr-woodpecker

Reasons (based on the campaign):

  • compromised-package

  • exfiltration-env-variables

  • exfiltration-cloud-tokens

  • exfiltration-credentials

  • abuses-pth

  • obfuscation

  • infostealer

  • The package contains code to detect if it is running in a sandbox environment.

  • exfiltration-crypto

  • files-exfiltration

  • destructive-actions

Malicious versions

1 flagged
0.9.14

Indicators of compromise (SHA-256)

8f0d8d3e53a1baf4fa106b737ed698dc8b36e30f7d4b4f545be0437c9826d2b2
a954646bbe93fae5fe6204189c824b3e77e1adfa97252528e5df0fad24533dc9
7346cb23311841f58ac624f92cd4023842006e177048c586d1549bb5cb8e7d6a

Frequently asked questions

No. gpsea on PyPI has been identified as a malicious package (version 0.9.14 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-06-compr-woodpecker

References

Credits

  • Kamil Mańkowski (kam193) · analyst
  • O3 Security · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection
gpsea (PyPI) malicious package — MAL-2026-5316 | O3 Security