Compromised releases of the agent-framework package, versions 1.26.1 and 1.26.2, added a credential stealer after they were published on November 17, 2026, according to GitHub advisory GHSA-764m-3ppc-5m73. The advisory, published November 18, 2026, says anyone who installed those versions should treat the environment as exposed and rotate the credentials reachable from it, including CI and GitHub Actions secrets. Version 1.26.0 and earlier are not affected. As of November 19, 2026, both compromised releases have been removed from PyPI.

#What changed?

Two compromised releases of the agent-framework package, 1.26.1 and 1.26.2, were published to the Python Package Index (PyPI) on November 17, 2026, and later removed, according to the GitHub advisory. The advisory’s own description is: “Malicious releases of the legitimate ‘agent-framework’ package (Microsoft Agent Framework).” 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.” It also says: “Both releases were published on 2026-11-17 (1.26.1 at 20:35 UTC as a wheel only, 1.26.2 at 21:08 UTC) and have since been removed from PyPI.” Those publication times are 02:05 IST and 02:38 IST on November 18, 2026.

SecurityWeek reported that the two versions “were released roughly 33 minutes apart.” BleepingComputer reported that the stealer “executed automatically during normal Python startup in affected environments, even when the Agent Framework package was not imported.”

An Amazon Inspector entry on the same GitHub advisory says: “Package metadata impersonates Microsoft and mimics the real microsoft/agent-framework README as cover.” It also says: “The name resembles the legitimate Microsoft package.” BleepingComputer described the incident as a compromise of “Microsoft’s official Agent Framework Python package on PyPI.”

SecurityWeek reported that “Unlike legitimate releases, which included both built and source distributions, the malicious versions contained only built packages.” SecurityWeek, citing Wiz, also reported: “Wiz also found no corresponding releases or malicious code in Microsoft’s main source repository, suggesting the packages may have been uploaded outside the normal release process.”

BleepingComputer said both versions “retained their dependency on the legitimate agent-framework-core 1.26.0 package, allowing the framework to function normally while the malware ran in the background.” SecurityWeek wrote: “This allowed applications to continue functioning normally despite the compromise.”

As of November 19, 2026, the agent-framework project page on PyPI lists 1.26.0 as the latest release, dated November 12, 2026.

#Who is affected and when?

Anyone who installed agent-framework 1.26.1 or 1.26.2 is in the advisory’s scope, including installs on laptops, in CI/CD pipelines and in container images. Version 1.26.0 and earlier are not affected, the advisory says.

Download figures published with the story are for the whole package, not for the compromised versions. BleepingComputer put the package at roughly 200,000 monthly downloads. SecurityWeek put it at approximately 190,000 downloads per month.

The GitHub advisory says: “We have not attributed this to a known campaign.”

BleepingComputer reported that “PyPI quarantined the first malicious release, but the attacker published a second version roughly 2.5 minutes later, which was also quarantined about eight minutes afterward.” It added: “The second release indicates that the attacker still had publishing access after the initial quarantine.”

Microsoft has acknowledged the incident, SecurityWeek reported, citing an Agent Framework maintainer who confirmed in a GitHub discussion that the compromised releases were removed from PyPI and that an investigation was underway. BleepingComputer said it had contacted Microsoft and had not received a response when it published its report on November 18, 2026.

BleepingComputer and SecurityWeek report that the method used to publish the malicious releases is unknown.

#What should you do?

If 1.26.1 or 1.26.2 was installed, treat that environment as exposed, rebuild it from 1.26.0, and rotate cloud, CI and GitHub Actions secrets reachable from it.

The GitHub advisory says: “Anyone who installed 1.26.1 or 1.26.2 should treat the environment as exposed and rotate the credentials reachable from it, including CI and GitHub Actions secrets.” It also says: “1.26.0 and earlier are not affected.”

BleepingComputer says: “Developers who installed either malicious version should isolate affected environments, avoid running Python or pip until they are secured, and rebuild from a known-clean environment using the safe 1.26.0 release.” It adds: “Any potentially exposed credentials that were within the reach of the compromised environment should be rotated immediately.”

SecurityWeek says: “Organizations are advised to check developer environments, CI/CD pipelines, and container images for the compromised versions, and replace affected installations with verified packages.” It also says they “should also rotate potentially exposed credentials, investigate suspicious cloud activity, and rebuild affected environments.”

#What did the stealer target?

The credential stealer collected secrets from the local environment and tried to obtain cloud and CI tokens, according to SecurityWeek and BleepingComputer, and it ran when the Python interpreter started even if the package was not imported.

SecurityWeek reported: “The malware runs whenever the Python interpreter starts, even if the application doesn’t explicitly import the compromised package.” It said the targets “include secrets stored in environment variables and configuration files, as well as credentials belonging to other running processes.” It also “attempts to obtain Azure managed identity tokens and Azure DevOps authentication tokens that could provide access to cloud resources,” and that “The second malicious release expanded the credential-stealing functionality to GitHub Actions.”

BleepingComputer reported that version 1.26.1 “harvested secrets from environment variables, local configuration files, and other running processes where permissions allowed, targeting Azure, AWS, GitHub, Docker, Hugging Face, OpenAI, and other services.” It said version 1.26.2 “added GitHub Actions OIDC token requests and searches of GitHub runner directories.” OIDC here is OpenID Connect.

#How does it compare?

This is a package-release compromise on PyPI in which a credential stealer ran in the background of an otherwise working install. In October 2026, a similar pattern appeared in the LiteLLM 1.107.0 supply-chain compromise, where a malicious release also carried a credential stealer and maintainers told users to pin a last known-clean version and rotate secrets. A follow-up on that incident, including a signing-key change, is in our coverage of the LiteLLM cosign key update.

Our analysis: The version numbers and the clean release are not in dispute: 1.26.1 and 1.26.2 are the affected releases, and 1.26.0 is the last clean one. The GitHub advisory and the Amazon Inspector entry on the same page describe the package in different terms. The practical step does not depend on resolving that difference. Anyone who installed 1.26.1 or 1.26.2 should rebuild from 1.26.0 and rotate every cloud, CI and GitHub Actions secret the environment could reach.

#What is still unclear?

The sources leave open how the attacker published the releases, how widely 1.26.1 and 1.26.2 were installed, and what Microsoft’s investigation will find.

  • How did the attacker gain access to publish the compromised releases? BleepingComputer and SecurityWeek report that the method is unknown.
  • How many times were 1.26.1 and 1.26.2 downloaded? The monthly figures from BleepingComputer and SecurityWeek are for the package as a whole.
  • What will the investigation find? SecurityWeek reported that a maintainer said an investigation was underway.