🔍 Read the full analysis: The Microsoft AI Agent Framework PyPI Hijack And Its Credential Risks on ThorstenMeyerAI.com
Get the latest gadgets delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
TL;DR
Two versions of Microsoft’s official Python package agent-framework, 1.26.1 and 1.26.2, contained credential-stealing code and were available on PyPI on November 17, 2026. The releases were quarantined, but anyone who installed either should treat the environment as exposed, rebuild it from a clean base, and rotate credentials it could access.
Two versions of Microsoft’s official Python package for its Agent Framework carried credential-stealing code after appearing on PyPI on November 17, according to public security advisories. PyPI quarantined both releases, but developers and organizations that installed either version should treat affected systems as exposed and replace reachable credentials.
The affected releases were agent-framework 1.26.1 and 1.26.2. The GitHub Advisory Database says both contained a credential stealer absent from the last clean version, 1.26.0, and rates the incident critical. The package is the one Microsoft’s installation instructions direct users to, rather than an unrelated package using a similar name. Security firm Wiz says the package receives almost 200,000 downloads a month; that figure is the firm’s reported monthly download estimate, not a count of affected installations.
According to the published timeline, version 1.26.1 appeared at 20:35 UTC on November 17. PyPI quarantined it at about 21:06 UTC. A second release, 1.26.2, was uploaded at 21:08 and quarantined at 21:16. StepSecurity says the first release was available for about 31 minutes and the second for eight minutes. PyPI now lists 1.26.0, released November 12, as the current version, according to the source material.
The advisory says a startup hook caused the malicious code to run when Python started in an affected environment, even if the user did not import the Agent Framework. It sought credentials and tokens from environment variables, developer-tool and container-registry files, and other processes where accessible. The advisory also describes requests for fresh tokens from Azure managed identity and Azure DevOps pipelines; version 1.26.2 added GitHub Actions identity tokens. The stolen material was sent to an attacker-controlled collection address, the advisory says.
agent-framework on PyPI · UTC
Two poisoned releases, one evening
The official package of Microsoft’s Agent Framework, step by step. Blue: what happened. Green: the clean version.
November 12 to 18, 2026
- Clean 1.26.0 publishedStill the current version on PyPI
- Malicious 1.26.1 appearsFramework works normally, a credential stealer runs whenever Python starts
- PyPI quarantines 1.26.1After about 31 minutes
- Attacker uploads 1.26.2Renamed files, also targets GitHub Actions tokens
- PyPI quarantines 1.26.2Eight minutes later
- Malware databases list itMAL-2026-20101 (OpenSSF), GHSA-764m-3ppc-5m73 (GitHub)
Sources: GitHub Advisory Database GHSA-764m-3ppc-5m73, Nov 18, 2026; OSV MAL-2026-20101, Nov 17, 2026; PyPI project data, checked Nov 19, 2026; StepSecurity analysis (quarantine times).
Graphic: Powered by Thorsten Meyer AI
Why Build Credentials Were at Risk
The incident matters because Python startup can follow installation in ordinary developer and automation workflows. A test, linter, or build command could start the interpreter and trigger the code without an explicit import of the framework. Since the framework itself continued to work, a successful installation or build would not necessarily alert users that anything was wrong.
Credentials available to a developer laptop or CI runner can grant access to cloud services, source repositories, package registries, and AI platforms. The advisory’s account of active token requests, alongside collection of existing credentials, means exposure may extend beyond static secrets. OpenSourceMalware, as quoted by The Register, said that short-lived tokens can still be useful to an attacker if they are taken promptly. The extent of any resulting access or misuse has not been publicly established in the supplied material.
For affected teams, removing the package alone is not enough: credentials it could reach may remain usable. The recommended response is to rebuild affected environments from a clean base and rotate the credentials accessible to them, including CI and GitHub Actions secrets, as specified in the GitHub advisory.
Products Worth Considering

LG 27GR83Q-B 27-inch Ultragear QHD IPS Gaming Monitor

Sony WH-1000XM6 Wireless Noise-Canceling Headphones, Black

Bose TV Speaker (2nd Gen) Compact Soundbar with Bluetooth and HDMI Connectivity
As an affiliate, we earn on qualifying purchases.
How the Two Releases Appeared
Microsoft’s Agent Framework is an open-source Python toolkit for building AI agents and coordinating them in workflows. The PyPI package agent-framework acts as an umbrella package, pulling in framework components and integrations. The latest clean version identified in the advisory was 1.26.0, published November 12.
The incident’s timeline highlights a weakness in responding to a compromised publisher account or credential. After PyPI quarantined 1.26.1, another version was uploaded two minutes later. StepSecurity says the quarantine did not immediately revoke the attacker’s publishing access; JFrog similarly noted that quarantining a version does not itself invalidate a compromised publishing credential. The sources identify several firms that analyzed the releases, including Socket, StepSecurity, Wiz, JFrog, and Endor Labs.
The OpenSSF’s open-source malware database listed the case as MAL-2026-20101 on November 17, and the GitHub Advisory Database published GHSA-764m-3ppc-5m73 on November 18, according to the supplied timeline. These records and researcher analyses provide the public account currently available here; the source material says no Microsoft security advisory had been found at publication.
“A credential stealer that is not present in the last clean release, 1.26.0.”
— GitHub Advisory Database
Victim Numbers and Investigation Status
No confirmed victim count is provided in the supplied material. Wiz’s estimate of almost 200,000 monthly downloads is not a count of installs during the exposure window, and it does not establish how many systems installed either affected release. Automatic updates may have brought the package into environments, but the number and identity of those environments are unknown here.
It is also unclear whether stolen credentials were used, which organizations or individuals were affected, or whether any data or systems were accessed with them. Researchers reported no remote-code-loading second stage in the code they inspected, and The Register reported that the malware was not persistent beyond the installed package; those observations do not establish that credentials already taken were harmless or unused. The supplied material includes no detailed Microsoft security advisory or final account of how the publishing access was compromised.
Rebuilds and Credential Rotation
Organizations should check package records, lockfiles, build logs, and deployment histories for installations of 1.26.1 or 1.26.2. If either version was installed, the advisory recommends treating the environment as exposed, rebuilding from a clean base using 1.26.0, and rotating every credential the environment could access. Teams should include cloud keys, repository and package tokens, and CI or GitHub Actions secrets where relevant.
Security teams should follow updates from Microsoft, PyPI, the GitHub Advisory Database, and the researchers who analyzed the packages. A fuller account may clarify the publishing-access compromise, the number of affected installations, and whether investigators have found evidence that stolen credentials were used. Until then, the response should be based on exposure to an affected release, not on whether the framework appeared to function normally.
Key Questions
Which package versions were affected?
The affected PyPI releases were agent-framework 1.26.1 and 1.26.2. The GitHub Advisory Database identifies 1.26.0 as the last clean release in this incident.
Did someone have to import the framework for the code to run?
No. The advisory says the added startup hook ran when Python started in an affected environment, without importing agent_framework.
What should teams do if they installed an affected version?
Treat the environment as exposed, rebuild it from a clean base using version 1.26.0, and rotate credentials it could access, including relevant cloud, CI, and GitHub Actions secrets.
How many users were affected?
The supplied reporting does not give a confirmed victim count. Wiz’s estimate of almost 200,000 downloads a month is a general monthly figure, not a count of affected installs during the brief exposure window.
Has Microsoft explained how the releases were published?
The source material cites a short Microsoft statement saying some repositories were made private while the company investigated malicious content. It does not provide a detailed account of the publishing compromise or the investigation’s results.
Source: ThorstenMeyerAI.com
