PYSEC-2026-4388

Vulnerability from pysec - Published: 2026-11-17 23:18 - Updated: 2026-11-17 23:18
VLAI
Details

agent-framework versions 1.26.1 and 1.26.2 were uploaded to PyPI on 2026-11-17 without authorization, as wheel-only releases repackaged from the legitimate 1.26.0 wheel. Both added a .pth file, which runs the payload on every Python interpreter start in the environment where the package is installed, without needing an import. The payload forks a background process that collects: - environment variables matching TOKEN, SECRET, KEY, AZURE, AWS, GITHUB, OPENAI and CI names - credential files such as ~/.azure, pip.conf, .npmrc, .netrc, .git-credentials, Docker config, the Hugging Face token, Azure DevOps agent .credentials and .env files under /app and /workspace - secrets from other processes' /proc/*/environ - Azure DevOps OIDC tokens (via SYSTEM_OIDCREQUESTURI and SYSTEM_ACCESSTOKEN) - Azure managed identity tokens for ARM, Graph, Key Vault, Storage, ACR, Azure DevOps and AzureADTokenExchange, plus IMDS instance metadata Version 1.26.2 also requests GitHub Actions OIDC tokens and collects runner temp files. Collected data is compressed and POSTed to a webhook.site URL.

Indicators of compromise: - 1.26.1: agent_framework_meta.pth and agent_framework_meta/_telemetry.py; wheel sha256 d27fa34414e6201d5e03e559ef634f020057554d7b3f4898dd5d7cd3e989e110 - 1.26.2: af_runtime_diag.pth and af_runtime_diag.py; wheel sha256 3d20a8bc91351a9a16b6db243b848ceca0206b7a8623b02d2af553a9c9f7e0a9 - Exfiltration: hxxps://webhook[.]site/d381fd80-ec62-42ad-8f5c-d1b15103c9bb?t=telemetry - User-Agent: af-runtime-diagnostics/1 (1.26.1), runtime-diagnostics/1 (1.26.2) - Environment variable _AF_TEL set in child processes

Any system or CI job that installed either version should be treated as compromised. Rotate every credential reachable from it, including cloud identities, CI tokens and package registry tokens, and review cloud and CI audit logs for their use.

PyPI Security worked with Microsoft to review the project's accounts and complete remediation steps. Both versions have been removed from PyPI. Version 1.26.0 is not affected.

Impacted products
Name purl
agent-framework pkg:pypi/agent-framework

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "agent-framework",
        "purl": "pkg:pypi/agent-framework"
      },
      "versions": [
        "1.26.1",
        "1.26.2"
      ]
    }
  ],
  "credits": [
    {
      "contact": [
        "https://www.wiz.io/"
      ],
      "name": "Wiz",
      "type": "REPORTER"
    },
    {
      "name": "Mike Fiedler",
      "type": "COORDINATOR"
    },
    {
      "name": "Microsoft",
      "type": "REMEDIATION_DEVELOPER"
    }
  ],
  "details": "`agent-framework` versions 1.26.1 and 1.26.2 were uploaded to PyPI on 2026-11-17\nwithout authorization, as wheel-only releases repackaged from the legitimate 1.26.0 wheel.\nBoth added a `.pth` file, which runs the payload on every Python interpreter start\nin the environment where the package is installed, without needing an import.\nThe payload forks a background process that collects:\n- environment variables matching TOKEN, SECRET, KEY, AZURE, AWS, GITHUB, OPENAI and CI names\n- credential files such as `~/.azure`, `pip.conf`, `.npmrc`, `.netrc`,\n  `.git-credentials`, Docker config, the Hugging Face token, Azure DevOps agent\n  `.credentials` and `.env` files under `/app` and `/workspace`\n- secrets from other processes\u0027 `/proc/*/environ`\n- Azure DevOps OIDC tokens (via `SYSTEM_OIDCREQUESTURI` and `SYSTEM_ACCESSTOKEN`)\n- Azure managed identity tokens for ARM, Graph, Key Vault, Storage, ACR,\n  Azure DevOps and AzureADTokenExchange, plus IMDS instance metadata\nVersion 1.26.2 also requests GitHub Actions OIDC tokens and collects runner temp files.\nCollected data is compressed and POSTed to a webhook.site URL.\n\nIndicators of compromise:\n- 1.26.1: `agent_framework_meta.pth` and `agent_framework_meta/_telemetry.py`;\n  wheel sha256 d27fa34414e6201d5e03e559ef634f020057554d7b3f4898dd5d7cd3e989e110\n- 1.26.2: `af_runtime_diag.pth` and `af_runtime_diag.py`;\n  wheel sha256 3d20a8bc91351a9a16b6db243b848ceca0206b7a8623b02d2af553a9c9f7e0a9\n- Exfiltration: hxxps://webhook[.]site/d381fd80-ec62-42ad-8f5c-d1b15103c9bb?t=telemetry\n- User-Agent: `af-runtime-diagnostics/1` (1.26.1), `runtime-diagnostics/1` (1.26.2)\n- Environment variable `_AF_TEL` set in child processes\n\nAny system or CI job that installed either version should be treated as compromised.\nRotate every credential reachable from it, including cloud identities, CI tokens and\npackage registry tokens, and review cloud and CI audit logs for their use.\n\nPyPI Security worked with Microsoft to review the project\u0027s accounts and complete\nremediation steps. Both versions have been removed from PyPI. Version 1.26.0 is not affected.\n",
  "id": "PYSEC-2026-4388",
  "modified": "2026-11-17T23:18:29Z",
  "published": "2026-11-17T23:18:29Z",
  "references": [
    {
      "type": "EVIDENCE",
      "url": "https://inspector.pypi.io/project/agent-framework/1.26.1/packages/6a/ce/71a695e356e692b2b74de921418b41c1aee5d2cd2501fe8e01469083339b/agent_framework-1.26.1-py3-none-any.whl/agent_framework_meta.pth"
    },
    {
      "type": "EVIDENCE",
      "url": "https://inspector.pypi.io/project/agent-framework/1.26.1/packages/6a/ce/71a695e356e692b2b74de921418b41c1aee5d2cd2501fe8e01469083339b/agent_framework-1.26.1-py3-none-any.whl/agent_framework_meta/__init__.py#line.34"
    },
    {
      "type": "EVIDENCE",
      "url": "https://inspector.pypi.io/project/agent-framework/1.26.1/packages/6a/ce/71a695e356e692b2b74de921418b41c1aee5d2cd2501fe8e01469083339b/agent_framework-1.26.1-py3-none-any.whl/agent_framework_meta/_telemetry.py"
    },
    {
      "type": "EVIDENCE",
      "url": "https://inspector.pypi.io/project/agent-framework/1.26.2/packages/a9/31/b8edc034d5b544831b70c3353ae8c1ec2dd7d7389d15da6ec5402e6ec509/agent_framework-1.26.2-py3-none-any.whl/af_runtime_diag.pth"
    },
    {
      "type": "EVIDENCE",
      "url": "https://inspector.pypi.io/project/agent-framework/1.26.2/packages/a9/31/b8edc034d5b544831b70c3353ae8c1ec2dd7d7389d15da6ec5402e6ec509/agent_framework-1.26.2-py3-none-any.whl/af_runtime_diag.py#line.9"
    },
    {
      "type": "EVIDENCE",
      "url": "https://inspector.pypi.io/project/agent-framework/1.26.2/packages/a9/31/b8edc034d5b544831b70c3353ae8c1ec2dd7d7389d15da6ec5402e6ec509/agent_framework-1.26.2-py3-none-any.whl/af_runtime_diag.py#line.147"
    },
    {
      "type": "ARTICLE",
      "url": "https://www.wiz.io/blog/malicious-version-of-microsofts-agent-framework-published-to-pypi"
    },
    {
      "type": "PACKAGE",
      "url": "https://pypi.org/project/agent-framework/"
    }
  ],
  "summary": "agent-framework 1.26.1 and 1.26.2 contain credential-stealing code"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.