AIThis post was created with the assistance of artificial intelligence (AI).

TL;DR

The Python package agent-framework briefly had two malicious releases on PyPI on November 17, 2026, according to security advisories. Organizations that installed either version should treat affected environments as exposed, rebuild them from a clean base and rotate credentials they could access. Microsoft’s investigation and the full scope of any exposure remain unclear.

Two releases of Microsoft’s official Agent Framework Python package on PyPI contained credential-stealing code on November 17, according to the GitHub Advisory Database and security researchers. The affected versions, 1.26.1 and 1.26.2, were quarantined, but developers and organizations that installed them must assess exposed systems and credentials; Microsoft has said it is investigating.

Before you orderOffer from Amazon

Get privacy and security gear delivered free with Prime

  • Fast, free delivery on millions of items
  • Prime Video, Amazon Music and more included
  • Member-only deals all year
Start your free Prime trial Free trial for eligible customers · Cancel anytime
As an affiliate, we earn on qualifying purchases.

The GitHub Advisory Database says the malicious code was absent from the preceding clean release, version 1.26.0. PyPI records show 1.26.1 was published at 20:35 UTC and 1.26.2 at 21:08 UTC on November 17. StepSecurity reports that PyPI quarantined the first release at 21:06 UTC, then quarantined the second at 21:16 UTC. Both affected releases have since been removed from PyPI, where 1.26.0 was listed as current when the source material was checked on November 19.

The package continued to provide the framework, so an installation could appear to work normally. The advisory says the malicious code ran when Python started in an affected environment, even if the framework itself was not imported. That means exposure could extend to developer machines, build servers, continuous integration systems and container images that installed either release, including through automated updates.

Security advisories recommend treating environments that installed 1.26.1 or 1.26.2 as exposed: rebuild them from a clean base using version 1.26.0, then rotate credentials the environments could access. The GitHub advisory specifically names CI and GitHub Actions secrets among credentials to rotate. Quarantining a release prevents further installation through PyPI, but does not remove copies already held in caches, mirrors or images.

At a glance
reportWhen: Incident on November 17, 2026; current…
The developmentTwo malicious releases of Microsoft’s official Agent Framework Python package were published to PyPI on November 17, prompting security advisories and calls for affected users to rebuild environments and rotate credentials.
Bar chart titled 50 stored requests: who sent them? Based on Wiz's analysis of the requests stored by the attacker's free collection service: 29 from sandboxes, vendor scans and tests; 17 carrying real victim data; 4 from the attacker's own machines. Highlighted: behind the 17 requests, 3 victim cases, which Wiz counts as unique, successful thefts of victim data. Note: only what the free service stored, at most 50 requests; no install count has been published
What the attacker's collection service stored, per Wiz Research (researchers' claim, updated November 18, 2026). Chart: Thorsten Meyer AI.

The Response Falls to Every Exposed Environment

The package is the one Microsoft’s installation instructions direct users to, rather than an unrelated lookalike, according to the source material. Wiz says it receives almost 200,000 downloads a month, though that figure does not establish how many downloads occurred during the incident or how many users installed the malicious versions.

Responsibility for the immediate response is distributed. Developers and organizations must identify whether their environments installed either affected version, replace those environments and rotate reachable credentials. Teams responsible for CI, cloud infrastructure and AI services should include their secrets in that review. Security teams can coordinate the inventory and credential rotation; package consumers still need to check their own dependency records and build artifacts.

The incident also shows why removing a release from a registry is only one part of containment. StepSecurity says the attacker published 1.26.2 shortly after the first release was quarantined, indicating that the initial quarantine did not immediately end the attacker’s ability to publish. That sequence makes review of publishing access and downstream copies relevant to the response, while the available material does not establish how that access was obtained.

Products Worth Considering

Apple MacBook Pro 2026 14.2 Laptop with M5 Pro chip, 15‑core CPU, 16‑core GPU, 24 GB Unified Memory, 1 TB SSD, Wi‑Fi 7 – Silver

Apple MacBook Pro 2026 14.2 Laptop with M5 Pro chip, 15‑core CPU, 16‑core GPU, 24 GB Unified Memory, 1 TB SSD, Wi‑Fi 7 – Silver

Logitech MX Keys S Combo Wireless Keyboard and Mouse, Graphite

Logitech MX Keys S Combo Wireless Keyboard and Mouse, Graphite

As an affiliate, we earn on qualifying purchases.

Two Releases After a Clean Update

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 serves as an umbrella package for the framework’s core code and integrations.

The documented timeline begins with clean version 1.26.0, published November 12. Version 1.26.1 appeared on November 17 at 20:35 UTC. After PyPI quarantined it at about 21:06 UTC, the attacker uploaded 1.26.2 roughly two minutes later, according to StepSecurity. PyPI quarantined that release at 21:16 UTC, the firm reports.

The OpenSSF malware database listed the case as MAL-2026-20101 on November 17, and the GitHub Advisory Database published GHSA-764m-3ppc-5m73 on November 18. The source material also names Socket, Wiz, JFrog and Endor Labs among firms that analyzed the releases. Their analyses and the advisories provide the documented account available to package users.

“We have made some repositories private while we investigate malicious content.”

— Microsoft, in a statement to The Register

Exposure and Publishing Access Remain Unclear

The available source material does not establish how the attacker obtained publishing access, whether credentials were successfully stolen or used, or how many environments installed the two releases. Wiz’s monthly download estimate is not a count of affected installations, and the number of downloads during the brief exposure window is not given.

Microsoft’s statement says it is investigating and has made some repositories private, but no Microsoft security advisory was identified in the source material. The precise scope of the repository changes, the investigation’s conclusions and any confirmed downstream misuse of credentials remain unknown.

Audit Installations and Rotate Secrets

Organizations should check dependency lockfiles, package installation records, build logs and container images for versions 1.26.1 and 1.26.2. If an environment installed either version, the cited guidance is to rebuild it from a clean base with 1.26.0 and rotate every credential it could reach, including CI and GitHub Actions secrets. Teams should also account for cached packages and images, which may persist after PyPI quarantine.

Further clarity depends on Microsoft’s investigation and any subsequent advisories from Microsoft, PyPI or security researchers. Until they provide more detail, affected users cannot infer that credentials were or were not misused from the package’s normal behavior or from the releases’ removal.

Key Questions

Which package versions were affected?

The GitHub Advisory Database identifies agent-framework 1.26.1 and 1.26.2 as malicious. It identifies 1.26.0 as the preceding clean release.

Who should respond?

Any developer or organization whose machine, build system, CI pipeline or container image installed either affected version should investigate. Teams that manage cloud, AI service and CI credentials should take part in the credential review and rotation.

Does PyPI quarantine remove the risk?

No. Quarantine prevents further installation from the registry, but copies may remain in caches, mirrors and container images. Existing environments and reachable credentials require separate attention.

Has Microsoft confirmed stolen credentials?

The source material does not report confirmation that credentials were successfully stolen or misused. Microsoft said it had made some repositories private while investigating malicious content.

Source: Thorsten Meyer AI

You May Also Like

216M Spy TVs – The LG Smart TV Problem [Video]

A video claims LG smart TVs may log audio and snoop on local devices, affecting 216 million units. Details are still emerging, with concerns over privacy.

Ten Days Later, Git On macOS Still Trusts The Compromised eMudhra Certificates

A community report says macOS developer tools still trust compromised eMudhra certificates as of Oct. 28, despite a manual workaround and a recent update.

Flawed Routers Flood University Of Wisconsin Internet Time Server (2003)

In 2003, flawed routers caused a flood of traffic to the University of Wisconsin’s internet time server, raising concerns about network security and device reliability.