🔍 Read the full analysis: Microsoft’s AI Agent Framework PyPI Hijack: A Call For Credential Security on ThorstenMeyerAI.com
Get the little things that make your day 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 Python package agent-framework, 1.26.1 and 1.26.2, were published with credential-stealing code on November 17, according to security advisories and researchers. PyPI quarantined both releases, but users whose environments installed them should treat accessible credentials as exposed and rebuild from a clean version. The number of affected installations and any confirmed credential misuse have not been established in the supplied reporting.
Two releases of Microsoft’s Python package agent-framework carried credential-stealing code when they appeared on PyPI on November 17, according to the GitHub Advisory Database and security researchers. PyPI quarantined both versions, but any laptop, build server, container or CI environment that installed version 1.26.1 or 1.26.2 should be treated as exposed, the advisory says.
The affected releases were 1.26.1 and 1.26.2. The GitHub Advisory Database says they contained a credential stealer absent from the preceding clean version, 1.26.0, and rates the incident critical. The first release appeared at 20:35 UTC; PyPI quarantined it at 21:06 UTC, according to StepSecurity. Version 1.26.2 was uploaded at 21:08 UTC and quarantined at 21:16 UTC. The source article describes the first exposure window as about 31 minutes.
The malicious code was designed to run when Python started in an affected environment, without the user importing the framework, according to the advisory. The legitimate framework continued to work, meaning a successful install or normal-looking application behavior would not by itself show that an environment was clean. The package is the one referenced by Microsoft’s installation instructions, rather than an unrelated package using a similar name.
The advisory and researchers say the code sought credentials in environment variables and common developer-tool or container-registry files. It also requested tokens from cloud and pipeline identity services; version 1.26.2 added GitHub Actions identity tokens, according to the source report. PyPI’s current listed version is 1.26.0, released November 12. The source reports that the two malicious versions have been removed from the registry.
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 software build environments often hold powerful credentials. A developer laptop, CI runner or container may have access to cloud accounts, source-code repositories, package registries and AI services. If an attacker obtains those credentials, the potential consequences extend beyond the machine where the package was installed. That possibility is why the advisory calls for rotating credentials the affected environment could access, including CI and GitHub Actions secrets.
The code’s reported start-up behavior complicates detection: an environment could install and run the framework normally while the added code operated in the background on a later Python launch. StepSecurity said it found no remote-code-loading second stage in the code it inspected, and the source report, citing researchers, says the malware was not persistent beyond the installed package. Those observations do not establish whether any stolen credentials were used, or whether every affected system has been identified.
The publication sequence also highlights a separate supply-chain risk. StepSecurity said quarantining the first release did not immediately revoke the attacker’s publishing access; JFrog similarly warned that removing a release does not itself invalidate a compromised publishing credential. The second upload followed the first quarantine by just over two minutes, according to StepSecurity. Registry removal can stop further installs, but it does not clean systems that already received a release.
Products Worth Considering

BowFlex Results Series 552 SelectTech Adjustable Dumbbell

Withings Body Smart Wi-Fi and Bluetooth Body Composition Scale

Withings BPM Connect Wi-Fi and Bluetooth Blood Pressure Monitor
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 is an umbrella package that brings in framework components and integrations. The last clean release identified in the advisory was 1.26.0, published November 12.
On November 17, version 1.26.1 was uploaded as a wheel, a ready-to-install package file, according to the advisory. PyPI quarantined it at 21:06 UTC. Two minutes later, the attacker uploaded 1.26.2 with renamed files and additional capabilities, StepSecurity reported; PyPI quarantined that release at 21:16 UTC. The OpenSSF malware database listed the incident as MAL-2026-20101, and the GitHub Advisory Database published advisory GHSA-764m-3ppc-5m73, according to the source report.
Several security firms, including Socket, StepSecurity, Wiz, JFrog and Endor Labs, analyzed the releases. Wiz said it promptly reported its findings to Microsoft on November 17. Microsoft’s response reported to The Register was brief: it said some repositories had been made private while the company investigated malicious content. The source article said it had not found a Microsoft security advisory at the time it was published.
“The credential stealer is not present in the last clean release, 1.26.0.”
— GitHub Advisory Database
Victim Count and Credential Misuse
The supplied reporting does not give a confirmed number of affected installations or victims. Wiz said the package receives almost 200,000 downloads a month, but that figure is a download estimate, not a count of installations during the exposure windows or evidence that credentials were stolen from that many users.
It is also unclear whether the attacker successfully collected credentials from any environment, whether any collected credentials were used, or how many systems installed either release before PyPI quarantined it. The source material does not provide a final account of how publishing access was obtained or whether Microsoft has completed its investigation. Microsoft’s reported statement does not answer those questions.
Actions for Affected Environments
The GitHub Advisory Database advises treating any environment that installed 1.26.1 or 1.26.2 as exposed. Its recommended response is to rebuild the environment 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 apply that guidance to developer machines, CI pipelines, build servers and container images that may have received either release.
Security teams should follow the published advisory and researcher reports for technical indicators and response instructions; the source article deliberately does not reproduce indicators or attack details. Further clarity depends on updates from Microsoft, the package registry and researchers about the investigation, the publishing credential and the scope of any credential exposure. The available reporting does not give a date for a final investigation report.
Key Questions
Which package versions were affected?
The reported malicious versions were agent-framework 1.26.1 and 1.26.2. The advisory identifies 1.26.0, released November 12, as the last clean version.
Does installing the package mean credentials were stolen?
Not necessarily. The advisory says the code searched for credentials and requested certain tokens, but the supplied reporting does not confirm how many systems were affected or whether any credentials were successfully collected or misused. Affected environments should still be treated as exposed.
What should users do if they installed either release?
The advisory recommends rebuilding from a clean base on version 1.26.0 and rotating every credential the affected environment could access, including CI and GitHub Actions secrets.
How long were the releases available?
StepSecurity says PyPI quarantined version 1.26.1 about 31 minutes after its 20:35 UTC upload and quarantined version 1.26.2 eight minutes after its 21:08 UTC upload. Both events occurred on November 17, 2026.
Has Microsoft explained how the publishing access was compromised?
Not in the statement cited by the source material. Microsoft told The Register that it had made some repositories private while investigating malicious content. The cause of the publishing access and the investigation’s final findings remain unclear in the available reporting.
Source: ThorstenMeyerAI.com
