Malicious versions of Microsoft’s agent-framework package were published to the Python Package Index on 17 November 2026 and later removed, according to Wiz Research and a GitHub security advisory. Anyone who installed 1.26.1 or 1.26.2 should treat the environment as exposed. The most recent safe version, both sources say, is 1.26.0. No Microsoft statement was found, and the root cause has not been confirmed.
In a blog post published on 17 November, Wiz said: “At 20:35 UTC on November 17, 2026, a malicious version (1.26.1) of the agent-framework package (Microsoft Agent Framework) was uploaded to PyPI. A second version, 1.26.2, followed at 21:08 UTC. As of 21:30 UTC, both versions were no longer available on PyPI.” Those times are 20:35 GMT, 21:08 GMT and 21:30 GMT. A GitHub advisory, GHSA-764m-3ppc-5m73, published at 00:31 GMT on 18 November, rates the issue as critical and of type malware. It says versions 1.26.1 and 1.26.2 “add a credential stealer that is not present in the last clean release, 1.26.0,” that 1.26.1 was published “at 20:35 UTC as a wheel only,” and that both releases “have since been removed from PyPI.”
The dangerous part is how little a user has to do to run the extra code. Wiz and the advisory both say each malicious wheel drops a .pth file into the site-packages root, and that Python runs .pth files on every interpreter start, “so the credential stealer runs whenever Python starts in that environment, even if agent-framework is never imported.” The file names changed between the two releases. In 1.26.1 they are agent_framework_meta.pth and agent_framework_meta/_telemetry.py. In 1.26.2 they were renamed to af_runtime_diag.pth and af_runtime_diag.py, and searching only for the first pair will miss the second.
Wiz says the stealer “is focused on Azure and Azure DevOps.” It describes collection of secret-looking environment variables, credential files, Azure DevOps OIDC tokens and Azure managed-identity tokens. Version 1.26.2, uploaded 33 minutes after 1.26.1, adds theft of GitHub Actions OIDC tokens in workflows that have id-token: write. Stolen managed-identity and OIDC-exchanged tokens, Wiz says, “are valid for up to 24 hours.” The data was sent to a webhook.site address on that service’s free tier. Wiz says it confirmed the attackers’ token was on the free tier, “and a maximum of 50 requests were captured. However, those requests can contain working cloud, CI and registry credentials.” That 50 is Wiz’s reading of what the inbox captured, not a count of compromised companies. The webhook address itself is not published here.
The package “gets about 41,000 downloads a week,” Wiz says, and in a summary line “almost 200k downloads a month.” Those are Wiz’s download figures for the legitimate package, not a count of hosts that installed the malicious versions. The company also sets out why it thinks 1.26.1 may have been built outside the project’s normal release process: there is “no python-1.26.1 tag or release in microsoft/agent-framework,” the main branch does not contain the malicious code, and unlike legitimate releases, 1.26.1 was “a wheel only” that still depends on agent-framework-core[all]==1.26.0. “The root cause hasn’t been confirmed.” Wiz notes that another Microsoft Python package, durabletask, was compromised earlier this year after a PyPI token was stolen, and adds: “We have not linked the two incidents.” No statement from Microsoft about this week’s packages was found for this article.
Anyone who may have installed the malicious versions should, according to Wiz and the advisory, search lockfiles, CI logs, virtual environments and container images for agent-framework 1.26.1 or 1.26.2, and pin 1.26.0. They should look in site-packages for both filename sets: agent_framework_meta.pth and agent_framework_meta/_telemetry.py for 1.26.1, or af_runtime_diag.pth and af_runtime_diag.py for 1.26.2. If those files are present, any Python process started in that environment ran the payload. Credentials reachable from affected hosts and runners should be rotated, including secrets in the environment, Azure CLI sessions, Azure DevOps tokens and service connections, and package-registry or git credentials. Teams should also audit sign-in and activity logs for Azure managed identities and federated credentials that were reachable from those machines or pipelines, and, for 1.26.2, treat GitHub OIDC tokens from workflows that installed the package with id-token: write as exposed.
This is the latest in a line of software-supply-chain incidents TSN has covered in which a trusted package channel was used to steal credentials, including a malicious LiteLLM release on PyPI, secret-stealing code in WPPConnect’s WhatsApp libraries on npm, the Gheist campaign that Wiz said used stolen GitHub tokens to take CI secrets, and an npm worm campaign that JFrog said armed 42 GitHub repositories. The overlap is the pattern, not a finding that the same operators were involved.
A short window, an unconfirmed root cause, and two sets of file names
The publication window described by Wiz is short: 1.26.1 at 20:35 GMT, 1.26.2 at 21:08 GMT, and both gone from PyPI by 21:30 GMT. That does not make the packages harmless. A .pth hook means the stealer ran on interpreter start, not on the first import, so a brief install in CI can still have been enough. The “maximum of 50 requests” Wiz reports from the free-tier inbox is a cap on what that inbox logged, not a statement that only 50 machines were affected, and the 41,000 weekly downloads figure is not a count of malicious installs. Until someone publishes a verified infection total, those numbers should be left as Wiz stated them.
The other open fact is how the packages got onto the index. Wiz’s observations about a missing git tag, a wheel-only upload and an unchanged agent-framework-core dependency are clues, not a confirmed account of stolen credentials or a broken release pipeline. “The root cause hasn’t been confirmed,” and no Microsoft statement was found to add one. For anyone who installed 1.26.1 or 1.26.2, the immediate work is therefore the same either way: look for both filename sets, pin 1.26.0, rotate every secret that was reachable from that environment, and review Azure identities and GitHub OIDC trust for the 24-hour window in which stolen tokens could still have been used.
Sources
- Wiz Research, “Microsoft agent-framework Compromised: Credential Stealer Targets Azure and CI Pipelines,” 17 November 2026.
- GitHub Advisory Database, GHSA-764m-3ppc-5m73, “Malicious code in agent-framework (PyPI),” published 18 November 2026, 00:31 GMT.
Get TSN’s biggest tech stories, explained.
News and insights across AI, tech, crypto and cybersecurity. Every source linked. Unsubscribe anytime.
Get the newsletterRelated stories
WPPConnect WhatsApp Libraries Shipped Secret-Stealing Code is the closest recent TSN account of a trusted software package shipping secret-stealing code, and is the next read.
- Wiz Says Gheist Campaign Uses Stolen GitHub Tokens to Steal CI Secrets
- Malicious LiteLLM Release on PyPI Stole Credentials, Researchers Say
- JFrog Says npm Worm Campaign Armed 42 GitHub Repos From 11 Owners
Follow @tsnmediahub on X for breaking AI news as it happens.
Follow on X


