PYSEC-2026-4388 json
agent-framework 1.26.1 and 1.26.2 contain credential-stealing code
published yesterday modified 13h ago
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
`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.
Is PYSEC-2026-4388 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | agent-framework | 2 listed versions |
no fix listed |
References
-
inspector.pypi.io
/project/agent-framework/1.26.1/packages/6a/ce/71a695e356e692b2b74de921418b41c1aee5d2cd2501fe8e01469083339b/ag
evidence
-
inspector.pypi.io
/project/agent-framework/1.26.1/packages/6a/ce/71a695e356e692b2b74de921418b41c1aee5d2cd2501fe8e01469083339b/ag
evidence
-
inspector.pypi.io
/project/agent-framework/1.26.1/packages/6a/ce/71a695e356e692b2b74de921418b41c1aee5d2cd2501fe8e01469083339b/ag
evidence
-
inspector.pypi.io
/project/agent-framework/1.26.2/packages/a9/31/b8edc034d5b544831b70c3353ae8c1ec2dd7d7389d15da6ec5402e6ec509/ag
evidence
-
inspector.pypi.io
/project/agent-framework/1.26.2/packages/a9/31/b8edc034d5b544831b70c3353ae8c1ec2dd7d7389d15da6ec5402e6ec509/ag
evidence
-
inspector.pypi.io
/project/agent-framework/1.26.2/packages/a9/31/b8edc034d5b544831b70c3353ae8c1ec2dd7d7389d15da6ec5402e6ec509/ag
evidence
-
wiz.io
/blog/malicious-version-of-microsofts-agent-framework-published-to-pypi
article
-
pypi.org
/project/agent-framework/
package
Sources
- OSV PYSEC-2026-4388
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.