Microsoft's agent-framework 1.26.1 and 1.26.2 on PyPI stole CI credentials, and ONNX Runtime's GitHub repos are gone
Two releases of agent-framework, the PyPI meta-package for Microsoft Agent Framework, were credential stealers. Version 1.26.1 appeared on PyPI at 20:35 UTC on November 17 and 1.26.2 at 21:08 UTC, both uploaded to the project's own listing, not to a lookalike name. PyPI now marks both as "Release quarantined"; 1.26.0, released on November 12, is the last clean version. A few hours later microsoft/agent-framework, microsoft/onnxruntime and several other ONNX repositories started returning 404 on GitHub. As of 05:00 UTC on November 18, Microsoft has not explained either event.
What the two wheels did
The malware analyses from Endor Labs, OpenSourceMalware and the OSV entry MAL-2026-20101 agree on the mechanism. Each wheel adds a .pth file to site-packages. Python reads .pth files at every interpreter start and executes lines that begin with import, so the stealer runs whenever any Python process starts in that environment, pip included. Nobody has to import agent_framework. In 1.26.2 the hook is one line, import af_runtime_diag.
The collector forks into the background and reads environment variables with names like TOKEN, SECRET, KEY, AZURE, GITHUB or OPENAI, the environments of other processes through /proc/*/environ, and files such as ~/.azure, .npmrc, .git-credentials, Docker config, Hugging Face tokens and Azure DevOps agent credentials. It also asks for new tokens: Azure managed-identity tokens from the instance metadata service for a list of Azure services (Endor Labs counts 12), an Azure DevOps OIDC token, and in 1.26.2 GitHub Actions OIDC tokens. Everything goes, zlib-compressed and Base64-encoded, to a fixed webhook.site URL.
The application itself keeps working. Both malicious versions depend on agent-framework-core[all]==1.26.0, so an agent built on the framework installs and runs as before. Endor Labs also points out that in 1.26.2 the package's own agent_framework_meta/__init__.py is byte-identical to 1.26.0 and the payload sits in a new top-level module, so a check that only compares the package's own code against the previous release finds nothing.
What could have flagged them
Both uploads were wheel-only. The PyPI index still lists a wheel and an sdist for each clean release we looked at, from 1.24.0 to 1.26.0, and Endor Labs reports the same back to 1.21.0. The project page lists two maintainers, microsoft and vibiret. StepSecurity's finding, as summarized by InfraStack, is that vibiret was created and added to the project on the day of the attack.
Provenance attestations did not help, because the clean releases never had them either. PyPI's integrity endpoint returns 404 for the 1.26.0 wheel and sdist, which means no attestation was published, while a project that publishes them, such as sigstore 4.5.1, returns its provenance. The same is true of onnxruntime 1.32.0. A malicious upload without an attestation looked like every other release of the package.
Anyone who installed agent-framework between 20:35 and roughly 21:30 UTC on November 17 without pinning a version may have received one of the two. A host where it ran should be treated as exposed: look for agent_framework_meta.pth (1.26.1) or af_runtime_diag.pth (1.26.2) in site-packages, rebuild the environment and rotate the credentials it could reach, including CI and cloud identities. Endor Labs checked 22 sibling agent-framework-* packages and found no new releases since November 12; agent-framework-core still shows 1.26.0 as latest. OpenSourceMalware says the attacker was still believed to have publishing access, since 1.26.2 went up after 1.26.1 was quarantined.
The repositories that are gone
The first public complaints about microsoft/onnxruntime we found on X came at 22:53 UTC on November 17. When we checked at 05:01 UTC on November 18, these repositories returned 404:
microsoft/onnxruntimemicrosoft/onnxruntime-genaimicrosoft/onnxruntime-extensionsmicrosoft/onnxruntime-swift-package-managermicrosoft/onnxscriptmicrosoft/onnxconverter-commonmicrosoft/agent-framework
Other Microsoft AI repositories, including microsoft/Olive, microsoft/semantic-kernel and microsoft/autogen, were still up, as was onnx/onnx, the format specification.
The packages are still there. PyPI serves onnxruntime 1.32.0 (November 13) and onnxruntime-genai 0.20.0 (November 14), NuGet has Microsoft.ML.OnnxRuntime 1.32.0, and npm has onnxruntime-web 1.31.1. We read the install script of onnxruntime-node 1.31.1: it fetches its CUDA binaries from NuGet, not from GitHub, so that path should still work, though we did not run it.
What breaks is everything that goes to GitHub itself. Release assets are gone too; releases/download/v1.32.0/onnxruntime-linux-x64-1.32.0.tgz returns 404. Source builds, CMake or Git submodule setups that clone the repository, and tools that download the prebuilt C/C++ archives fail. One developer reported on X that fresh Windows builds of flutter_onnxruntime fail while fetching ONNX Runtime. Forks survive, such as intel/onnxruntime, which carries OpenVINO changes. People on Hacker News are also passing around mirrors and archives of unknown origin; the only independent reference for the official history we found is a Wayback Machine snapshot of the repository from November 13.
We found no unauthorized ONNX Runtime package releases, and no statement linking the two events. The removal of microsoft/agent-framework the same night makes a connection plausible, but Microsoft has not said whether the repositories were deleted, made private for an investigation, or removed for an unrelated reason. Still open: how the attacker got upload rights on PyPI, whether that access has been revoked, and when ONNX Runtime's source and release downloads will be back.
- MAL-2026-20101: Malicious code in agent-framework (PyPI)
- agent-framework compromised: Python startup hooks steal Azure and CI credentials (Endor Labs)
- Official Microsoft agent-framework PyPI package compromised (OpenSourceMalware)
- agent-framework on PyPI
- Malicious packages this week (InfraStack)
- microsoft/onnxruntime (404 as of 2026-11-18 05:01 UTC)
- Wayback Machine snapshot of microsoft/onnxruntime, 2026-11-13
- Report of flutter_onnxruntime Windows builds failing
- Microsoft's ONNX Runtime has disappeared from GitHub (Hacker News)
Comments
No comments yet. Be the first.