What is GHSA-93QJ-5Q5V-3C2H?

GHSA-93QJ-5Q5V-3C2H is a critical-severity security vulnerability in pantheon-agents (pip), affecting versions >= 0.6.1, <= 0.6.2. It is fixed in 0.6.4.

Which versions of pantheon-agents are affected by GHSA-93QJ-5Q5V-3C2H?

pantheon-agents (pip) versions >= 0.6.1, <= 0.6.2 is affected.

Is there a fix for GHSA-93QJ-5Q5V-3C2H?

Yes. GHSA-93QJ-5Q5V-3C2H is fixed in 0.6.4. Upgrade to this version or later.

Is GHSA-93QJ-5Q5V-3C2H exploitable, and should I be worried?

Whether GHSA-93QJ-5Q5V-3C2H is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-93QJ-5Q5V-3C2H is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix GHSA-93QJ-5Q5V-3C2H?

Upgrade pantheon-agents to 0.6.4 or later.

GHSA-93QJ-5Q5V-3C2H in pantheon-agents

Q: Which versions of pantheon-agents are affected by GHSA-93QJ-5Q5V-3C2H?

pantheon-agents (pip) versions >= 0.6.1, <= 0.6.2 is affected.

Q: Is there a fix for GHSA-93QJ-5Q5V-3C2H?

Yes. GHSA-93QJ-5Q5V-3C2H is fixed in 0.6.4. Upgrade to this version or later.

Q: Is GHSA-93QJ-5Q5V-3C2H exploitable, and should I be worried?

Whether GHSA-93QJ-5Q5V-3C2H is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-93QJ-5Q5V-3C2H is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-93QJ-5Q5V-3C2H?

Upgrade pantheon-agents to 0.6.4 or later.

Summary

Trojanized pantheon-agents 0.6.1 and 0.6.2 on PyPI ship a credential stealer (supply-chain account compromise)

The PyPI account that publishes pantheon-agents was compromised in the June 2026 "Hades" PyPI supply-chain attack (Mini Shai-Hulud / Miasma lineage). The attacker used a stolen, long-lived PyPI API token to upload trojanized releases pantheon-agents 0.6.1 and 0.6.2 directly to PyPI.

Only the PyPI artifacts are affected. The GitHub source repository, its git tags, and all other distribution channels are clean, no malicious code was committed to the repository.

Affected

pantheon-agents 0.6.1 and 0.6.2 on PyPI.

Not affected: installs from the GitHub source, version 0.6.0 and earlier, and the Desktop / Online apps.

Indicators of compromise

The malicious wheels ship a *-setup.pth file that executes on Python startup. It downloads the Bun JavaScript runtime and runs an obfuscated credential stealer (_index.js) that harvests and exfiltrates credentials reachable from the host, environment variables, ~/.pypirc, ~/.npmrc, cloud credentials (~/.aws, etc.), SSH keys, and API tokens.

Check your environment's site-packages for an unexpected *-setup.pth, and your home directory for _index.js or a Bun runtime (~/.bun).

Status

The PyPI account is suspended and the malicious token has been disabled. PyPI distribution will resume after account recovery and migration to PyPI Trusted Publishing (OIDC). Sibling projects by the same maintainer (e.g. executor-engine, funcdesc, cmd2func, pantheon-toolsets, coolbox, ufish, magique, executor-http) were hit by the same campaign and are being remediated separately.

Impact

Anyone who pip installed pantheon-agents 0.6.1 or 0.6.2 should assume every credential present on that machine has been exfiltrated.

Affected versions

pantheon-agents (>= 0.6.1, <= 0.6.2)

Security releases

pantheon-agents → 0.6.4 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Do not install pantheon-agents from PyPI until distribution resumes.
If you installed 0.6.1 or 0.6.2:
- Run pip uninstall pantheon-agents immediately and check for the IoCs above.
- Rotate every credential that was present on that machine (API keys, tokens, SSH keys, cloud credentials).

Install only from the clean GitHub source:

pip install "git+https://github.com/aristoteleo/PantheonOS.git"

Frequently Asked Questions

What is GHSA-93QJ-5Q5V-3C2H? GHSA-93QJ-5Q5V-3C2H is a critical-severity security vulnerability in pantheon-agents (pip), affecting versions >= 0.6.1, <= 0.6.2. It is fixed in 0.6.4.
Which versions of pantheon-agents are affected by GHSA-93QJ-5Q5V-3C2H? pantheon-agents (pip) versions >= 0.6.1, <= 0.6.2 is affected.
Is there a fix for GHSA-93QJ-5Q5V-3C2H? Yes. GHSA-93QJ-5Q5V-3C2H is fixed in 0.6.4. Upgrade to this version or later.
Is GHSA-93QJ-5Q5V-3C2H exploitable, and should I be worried? Whether GHSA-93QJ-5Q5V-3C2H is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-93QJ-5Q5V-3C2H is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-93QJ-5Q5V-3C2H? Upgrade pantheon-agents to 0.6.4 or later.