Microsoft agent-framework 1.26.1 and 1.26.2 on PyPI were malicious: a .pth startup hook stole Azure, GitHub Actions and CI credentials
On 17 November 2026 two releases of the official agent-framework meta-package for Microsoft Agent Framework, 1.26.1 (20:35 UTC) and 1.26.2 (21:08 UTC), were uploaded to PyPI with a credential stealer. Each wheel drops a .pth file into site-packages, so the stealer runs on every Python start in that environment, even if agent_framework is never imported. It harvests secrets from environment variables, credential files and other processes, requests fresh GitHub Actions, Azure DevOps and Azure managed-identity tokens, and posts everything to a webhook.site URL. Both versions were quarantined; 1.26.0 is the last clean release.
What it is
1.26.1 ships agent_framework_meta.pth and agent_framework_meta/_telemetry.py; 1.26.2 moves the payload to a new top-level af_runtime_diag.pth and af_runtime_diag.py and restores agent_framework_meta/__init__.py to the clean 1.26.0 file, so a diff of the package module alone misses it.
Collected: hostname, user, cwd and arguments; environment variables whose names contain TOKEN, SECRET, PASSWORD, KEY, AZURE, AWS, GITHUB, HF_, OPENAI, NPM, PIP and similar; secret-looking entries from up to 300 /proc/*/environ files; credential files such as ~/.azure, .npmrc, pip.conf, .netrc, .git-credentials, .docker/config.json, Hugging Face tokens, Azure Pipelines agent .credentials and .env files.
It also mints new tokens: Azure DevOps OIDC (SYSTEM_ACCESSTOKEN + SYSTEM_OIDCREQUESTURI), Azure managed-identity tokens from IDENTITY_ENDPOINT/MSI_ENDPOINT or 169.254.169.254 for management, Key Vault, Graph, storage, Cognitive Services and more, and in 1.26.2 GitHub Actions OIDC tokens (ACTIONS_ID_TOKEN_REQUEST_URL) for api://AzureADTokenExchange and management.azure.com.
Data is zlib-compressed, base64-encoded and POSTed to https://webhook.site/d381fd80-ec62-42ad-8f5c-d1b15103c9bb (stored base64-encoded in the code) with User-Agent af-runtime-diagnostics/1 (1.26.1) or runtime-diagnostics/1 (1.26.2). No second-stage payload was found.
Both malicious versions were wheel-only and still pin agent-framework-core[all]==1.26.0, so the framework keeps working. Wiz found no matching tag in microsoft/agent-framework; Endor Labs saw no new releases of agent-framework-core or the other agent-framework-* packages it checked. StepSecurity reports 1.26.1 was quarantined at 21:06 UTC and 1.26.2 was uploaded about two minutes later, then quarantined at 21:16 UTC. The root cause (likely publisher access compromise) has not been confirmed.
How to check
- Search lockfiles, CI logs, virtualenvs and container images for agent-framework==1.26.1 or 1.26.2 (an unpinned install on 17 November could have resolved to either).
- In every site-packages directory, look for agent_framework_meta.pth, agent_framework_meta/_telemetry.py, af_runtime_diag.pth or af_runtime_diag.py.
- Search proxy and DNS logs for webhook.site/d381fd80-ec62-42ad-8f5c-d1b15103c9bb.
How to fix
- Pin agent-framework==1.26.0 (or a later release confirmed clean by Microsoft) and rebuild affected environments and images from scratch.
- Treat any host or runner that installed 1.26.1/1.26.2 as compromised: rotate cloud, Azure DevOps, GitHub, package-registry, Docker, Hugging Face and AI provider secrets that were in its environment or files, including secrets of other processes on shared runners.
- Review Azure activity logs for use of the workload's managed identities and federated (OIDC) credentials around 17 November 2026, and revoke sessions where possible.
pip show agent-framework 2>/dev/null | grep -i '^version'
python - <<'PY'
import site, glob, os
for d in site.getsitepackages() + [site.getusersitepackages()]:
for n in ('agent_framework_meta.pth', 'af_runtime_diag.pth', 'af_runtime_diag.py', 'agent_framework_meta/_telemetry.py'):
if os.path.exists(os.path.join(d, n)): print('FOUND', os.path.join(d, n))
PY
grep -rE 'agent-framework==1\.26\.(1|2)' requirements*.txt poetry.lock uv.lock Pipfile.lock 2>/dev/null