GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

GHSA-93QJ-5Q5V-3C2H

Vulnerability from github – Published: 2026-08-26 14:36 – Updated: 2026-08-26 14:36
VLAI
Summary
Trojanized pantheon-agents 0.6.1 and 0.6.2 on PyPI ship a credential stealer (supply-chain account compromise)
Details

Summary

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).

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.

Remediation

  1. Do not install pantheon-agents from PyPI until distribution resumes.
  2. If you installed 0.6.1 or 0.6.2:
  3. Run pip uninstall pantheon-agents immediately and check for the IoCs above.
  4. Rotate every credential that was present on that machine (API keys, tokens, SSH keys, cloud credentials).
  5. Install only from the clean GitHub source: pip install "git+https://github.com/aristoteleo/PantheonOS.git"

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.

Show details on source website

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 0.6.2"
      },
      "package": {
        "ecosystem": "PyPI",
        "name": "pantheon-agents"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.6.1"
            },
            {
              "fixed": "0.6.4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [],
  "database_specific": {
    "cwe_ids": [
      "CWE-506",
      "CWE-522"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-08-26T14:36:45Z",
    "nvd_published_at": null,
    "severity": "CRITICAL"
  },
  "details": "## Summary\nThe 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**.\n\n**Only the PyPI artifacts are affected.** The GitHub source repository, its git tags, and all other distribution channels are clean \u2014 no malicious code was committed to the repository.\n\n## Affected\n- `pantheon-agents` **0.6.1** and **0.6.2** on PyPI.\n\nNot affected: installs from the GitHub source, version 0.6.0 and earlier, and the Desktop / Online apps.\n\n## Indicators of compromise\nThe 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 \u2014 environment variables, `~/.pypirc`, `~/.npmrc`, cloud credentials (`~/.aws`, etc.), SSH keys, and API tokens.\n\nCheck your environment\u0027s `site-packages` for an unexpected `*-setup.pth`, and your home directory for `_index.js` or a Bun runtime (`~/.bun`).\n\n## Impact\nAnyone who `pip install`ed `pantheon-agents` 0.6.1 or 0.6.2 should assume **every credential present on that machine has been exfiltrated.**\n\n## Remediation\n1. **Do not install `pantheon-agents` from PyPI** until distribution resumes.\n2. If you installed 0.6.1 or 0.6.2:\n   - Run `pip uninstall pantheon-agents` immediately and check for the IoCs above.\n   - **Rotate every credential** that was present on that machine (API keys, tokens, SSH keys, cloud credentials).\n3. Install only from the clean GitHub source:\n   ```\n   pip install \"git+https://github.com/aristoteleo/PantheonOS.git\"\n   ```\n\n## Status\nThe 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.",
  "id": "GHSA-93qj-5q5v-3c2h",
  "modified": "2026-08-26T14:36:45Z",
  "published": "2026-08-26T14:36:45Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/aristoteleo/PantheonOS/security/advisories/GHSA-93qj-5q5v-3c2h"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/aristoteleo/PantheonOS"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [],
  "summary": "Trojanized pantheon-agents 0.6.1 and 0.6.2 on PyPI ship a credential stealer (supply-chain account compromise)"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

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…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Loading…