🔍 Read the full analysis: Microsoft’s AI Agent Framework PyPI Hijack: Protecting Credentials Afterward 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
Malicious versions 1.26.1 and 1.26.2 of Microsoft’s Python Agent Framework package were available on PyPI on Nov. 17, 2026, and contained credential-stealing code, according to security advisories. PyPI quarantined both releases; anyone who installed either should treat accessible credentials as exposed, rebuild from a clean base, and rotate those credentials.
Two malicious releases of Microsoft’s agent-framework Python package briefly appeared on PyPI on Nov. 17, carrying code that sought cloud keys, CI tokens and other credentials, according to security advisories. PyPI quarantined both versions, but developers and organizations that installed 1.26.1 or 1.26.2 are advised to treat the affected environments as exposed, rebuild them and rotate credentials they could access.
The affected releases were 1.26.1 and 1.26.2. 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 records and researcher timelines place the first upload at 20:35 UTC and the second at 21:08 UTC on Nov. 17. StepSecurity says PyPI quarantined version 1.26.1 at 21:06 UTC and 1.26.2 at 21:16 UTC. The current PyPI version identified in the source material is 1.26.0, released Nov. 12.
The malicious code added a Python startup hook, meaning it could run when Python started in an affected environment even if a user did not import the framework, according to the advisory. Researchers say it searched for credentials in environment variables and developer-tool files, and sought tokens from cloud and pipeline identity services. Version 1.26.2 added GitHub Actions identity-token access, according to the advisory. The framework continued to work, which could make the compromise less obvious to users.
Security researchers at Socket, StepSecurity, Wiz, JFrog and Endor Labs analyzed the releases. The source material says Wiz reported its findings to Microsoft on Nov. 17. Microsoft told The Register: “We have made some repositories private while we investigate malicious content.” The source reports that no Microsoft security advisory had been found at the time of publication.
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
Credential Exposure in Build Systems
The incident matters because Python packages are often installed not only on individual laptops but also in CI pipelines, build servers and container images. Those systems can hold credentials that grant access to source repositories, cloud resources, package registries and AI services. If a malicious package can read or request such credentials, the risk extends beyond the machine where installation occurred.
Researchers’ descriptions indicate that the code could collect both stored secrets and tokens requested from identity services. The OpenSSF malware record and GitHub advisory provide technical details for defenders; the immediate response described in the source is to assume credentials reachable from an affected environment may have been exposed. This is guidance based on the package’s capabilities, not confirmation that every accessible credential was stolen or misused.
The short interval between the two uploads also illustrates a registry-response issue. StepSecurity and JFrog say quarantining the first release did not by itself revoke the publishing access used to upload the next one. That distinction matters during supply-chain incidents: removing a version can limit further installation, while the publisher account or credential may still need separate investigation and containment.
Products Worth Considering

DJI Mini 5 Pro Fly More Combo with DJI RC 2, 1-Inch CMOS

Jackery HomePower 3600 Plus Portable Power Station, 3584Wh, 3600W

DJI Mini 4K Drone Combo with 4K Camera, 3-Axis Gimbal, and Two Batteries
As an affiliate, we earn on qualifying purchases.
How the Two Releases Appeared
Microsoft’s Agent Framework is an open-source toolkit for building and coordinating AI agents in Python. The PyPI package agent-framework is an umbrella package that brings in framework components and integrations. The source material says Microsoft’s installation instructions point users to this official package, rather than to an unrelated lookalike.
The timeline began with clean release 1.26.0 on Nov. 12. Version 1.26.1 appeared on PyPI five days later as a wheel-only release, according to the GitHub advisory. PyPI quarantined it at 21:06 UTC, according to StepSecurity. A second release, 1.26.2, followed at 21:08 UTC; StepSecurity says it was quarantined eight minutes later. Both releases are now described as unavailable on PyPI.
The incident was recorded by the OpenSSF’s open-source malware database as MAL-2026-20101 and by the GitHub Advisory Database as GHSA-764m-3ppc-5m73. Wiz said it reported its findings to Microsoft on Nov. 17. The source material attributes the incident’s timelines and technical analysis to multiple security firms and advisories, rather than relying on a single researcher’s account.
““We have made some repositories private while we investigate malicious content.””
— Microsoft, in a statement to The Register
Victim Count and Token Use
The number of installations and affected organizations has not been established in the supplied reporting. Wiz says the package receives almost 200,000 downloads a month, but that figure is not a count of downloads during the incident window, nor does it show how many users installed either malicious version. The source material provides no confirmed number of compromised systems.
It is also unclear whether attackers used any collected credentials, whether particular credentials were successfully obtained, or whether any downstream accounts or services were accessed. The researchers’ analysis of what the code could do does not establish that every capability succeeded in each environment. Microsoft’s investigation and the extent of any action on its repositories remain unclear from the reported statement.
The source material says StepSecurity found no remote-code-loading second stage in the inspected code and reports that the malware was not persistent beyond the installed package. Those findings do not rule out exposure of credentials during the period the package was present, or later use of stolen credentials.
Rebuild and Rotate Exposed Secrets
Organizations should identify whether any laptop, CI worker, build server or container image installed 1.26.1 or 1.26.2. The advisory guidance summarized in the source is to treat an affected environment as exposed, rebuild it from a clean base using version 1.26.0, and rotate every credential the environment could reach, including CI and GitHub Actions secrets. Teams should also review their relevant security advisories and internal logs for signs of unauthorized use; the supplied reporting does not provide a universal detection result.
Microsoft’s investigation and any fuller company guidance are the next public developments to watch for, along with updates from PyPI, the GitHub Advisory Database and security researchers. Until the investigation clarifies the scope, the reported download figure should not be treated as a victim count, and organizations should not assume that quarantine alone addressed credentials already accessible to an affected installation.
Key Questions
Which Microsoft Agent Framework package versions were affected?
The reported malicious 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 cited in the advisory.
What should I do if I installed one of the affected versions?
Follow the advisory guidance: treat the environment as exposed, rebuild from a clean base on version 1.26.0, and rotate every credential it could access, including relevant CI and GitHub Actions secrets. Review security advisories for further instructions.
Does the incident confirm that my credentials were stolen?
No. The advisories describe code designed to seek and collect credentials, but the supplied reporting does not establish that every credential in every affected environment was obtained or misused. The number of confirmed victims is also unknown.
How long were the malicious releases available?
According to StepSecurity’s timeline, version 1.26.1 was quarantined about 31 minutes after its 20:35 UTC upload on Nov. 17, and version 1.26.2 was quarantined at 21:16 UTC, about eight minutes after its upload at 21:08 UTC. PyPI quarantines prevent installation of the affected releases.
Has Microsoft published a full incident explanation?
The supplied source reports a short statement to The Register that Microsoft had made some repositories private while investigating malicious content. It says no Microsoft security advisory had been found at publication time; further company findings were not included.
Source: ThorstenMeyerAI.com
