🔍 Read the full analysis: What To Do About The PyPI Hijack Of Microsoft’s AI Agent Framework on ThorstenMeyerAI.com
Get hardware and tech essentials 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
PyPI versions 1.26.1 and 1.26.2 of Microsoft’s agent-framework package contained credential-stealing code and were quarantined on November 17, 2026. Security advisories say users should treat environments that installed either release as exposed, rebuild from a clean base using version 1.26.0, and rotate credentials the environment could access.
Two malicious versions of Microsoft’s official Python package for its Agent Framework were briefly available on PyPI on November 17, with code that security advisories say stole developer and cloud credentials. PyPI quarantined both releases, but anyone whose environment installed agent-framework 1.26.1 or 1.26.2 should treat it as exposed, rebuild from a clean base and rotate credentials it could reach.
The affected releases were 1.26.1 and 1.26.2 of the PyPI package agent-framework. The GitHub Advisory Database says both contained a credential stealer absent from the last clean release, 1.26.0, and rates the incident critical. PyPI’s current version is reported as 1.26.0, released November 12.
According to timelines from StepSecurity, version 1.26.1 appeared at 20:35 UTC on November 17 and was quarantined at 21:06. A second version, 1.26.2, was uploaded at 21:08 and quarantined at 21:16. The first release was therefore available for about 31 minutes; the second for about eight minutes. Both are no longer available from PyPI.
The advisory says the code ran when Python started in an affected environment, even if a user did not import agent-framework. It sought credentials and tokens associated with cloud services, developer tools and AI services. The recommended response is to rebuild affected environments from a clean base and rotate every credential they could access, including CI and GitHub Actions secrets. Several security firms, including Socket, StepSecurity, Wiz, JFrog and Endor Labs, reported examining the releases.
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 Brief Exposure Still Matters
The short availability window does not establish that only a small number of systems were affected. The package is the one Microsoft’s installation instructions direct Python users to, and Wiz says it receives almost 200,000 downloads a month. That figure describes monthly downloads; it does not reveal how many downloads occurred during the incident or how many installations were compromised.
The code reportedly left the framework functioning normally, making an affected installation less obvious to its user. Since Python could run the malicious hook on later interpreter starts, the exposure could extend beyond the moment of installation to subsequent work in the same environment. A laptop may contain personal or workplace credentials; a build server or CI pipeline may have access to deployment tokens and cloud identities.
Credential rotation matters even after removing the package because copied secrets can remain usable until revoked or replaced. Security researchers also highlighted that the code could request some short-lived identity tokens directly. OpenSourceMalware, as quoted by The Register, said that combining credential theft with active token requests made the incident especially dangerous in cloud build environments. That is an assessment of the risk, not a published count of successful thefts.
Products Worth Considering

LG 27G610A-B 27-inch UltraGear QHD (2560 x 1440) IPS Gaming Monitor, 200Hz, 1ms, AMD FreeSync Premium, VESA DisplayHDR 400, HDMI, DisplayPor

LG 27G810A-B 27-inch UltraGear 4K UHD IPS Gaming Monitor

Ledger Nano X – Classic Crypto Wallet with Bluetooth
As an affiliate, we earn on qualifying purchases.
How the Two Releases Appeared
Microsoft’s Agent Framework is an open-source toolkit for building AI agents in Python and coordinating them in workflows. The PyPI package agent-framework is an umbrella package that brings in framework code and integrations. The incident concerns the distribution package and its two releases, not a reported failure of the framework’s ordinary functions.
The last clean release identified in the advisory was 1.26.0, published November 12. Endor Labs said releases it examined from 1.21.0 through 1.26.0 had also included source code, while 1.26.1 was uploaded as a wheel only. StepSecurity’s account says PyPI quarantined 1.26.1, then the attacker uploaded 1.26.2 just over two minutes later with renamed files and additional capabilities.
That sequence matters because quarantine of one release did not, on its own, stop another upload. StepSecurity said quarantine did not immediately revoke the attacker’s publishing access; JFrog similarly noted that removing a version does not revoke a compromised publishing credential. The OpenSSF malware database listed the incident as MAL-2026-20101 on November 17, and the GitHub Advisory Database published GHSA-764m-3ppc-5m73 on November 18.
“The credential stealer is not present in the last clean release, 1.26.0.”
— GitHub Advisory Database
Victim Count and Credential Access
No victim count is provided in the supplied reporting, and it is not clear how many users or systems installed either malicious release before quarantine. The monthly download figure cited by Wiz is not a measure of incident-period downloads or confirmed infections.
Researchers describe the code’s credential-collection behavior, but the material does not establish which credentials were successfully taken, whether attackers used any stolen credentials, or whether particular organizations were affected. The source also reports no Microsoft security advisory at the time of publication. Microsoft’s investigation, including the reason repositories were made private, remains unclear from its brief statement.
StepSecurity reported no remote-code-loading second stage in the code it inspected, and The Register reported that researchers described the malware as not persistent beyond the installed package. Those findings do not rule out credentials being copied while it was present. The supplied material does not identify a confirmed publishing-account compromise or explain how the attacker obtained publishing access.
Rebuild, Rotate, and Monitor
Organizations should first check package records, lockfiles, build logs and container histories to determine whether 1.26.1 or 1.26.2 entered a laptop, CI runner, server or image. The GitHub Advisory Database and researchers’ advisories contain technical details for incident responders; this article does not reproduce indicators or attack instructions.
If either version was installed, treat the environment as exposed: rebuild it from a clean base using the reported clean version 1.26.0, then rotate credentials the environment could access. That includes cloud keys, source-control and CI secrets, package-registry credentials and AI-service keys where applicable. Teams should review relevant access and build logs for unexpected activity and follow their incident-response procedures.
Further information depends on updates from Microsoft, PyPI and the security researchers. Readers should check current advisories before acting because package status and investigation findings can change. The available reporting does not say when Microsoft will publish a fuller account or whether investigators will identify affected users.
Key Questions
Which PyPI versions were affected?
The GitHub Advisory Database identifies agent-framework 1.26.1 and 1.26.2 as containing the credential stealer. It identifies 1.26.0 as the last clean release.
What should a team do if it installed an affected version?
Treat the environment as exposed, rebuild it from a clean base using the reported clean version, and rotate every credential the environment could access, including relevant CI and GitHub Actions secrets. Review the advisories and follow your incident-response process.
Does the reporting say how many people were affected?
No. The source material provides no confirmed victim or installation count. Wiz’s figure of almost 200,000 downloads a month is a general monthly download estimate, not a count of downloads during the incident.
Was Microsoft’s framework itself nonfunctional?
The reported malicious code ran alongside the framework, which continued to work normally. The advisory says the code could run when Python started without the user importing agent-framework, so normal operation would not show that the environment was exposed.
Has Microsoft explained how the releases were published?
The source material reports a brief statement that Microsoft made some repositories private while investigating malicious content. It does not provide a fuller account of how the attacker gained publishing access or what Microsoft’s investigation has found.
Source: ThorstenMeyerAI.com
