Skip to main content
Back
IntrusionAzure · Microsoft Entra · SaaS
5 min read

Microsoft agent-framework releases on PyPI carry a credential stealer

Victim
Users of the two tampered releases. Wiz confirmed data theft in three cases. The victims were not named.
When
Nov 17, 2026Disclosed Nov 17, 2026
Entry
Someone published two altered releases on PyPI. Wiz suspects that credentials for Microsoft’s release system were compromised. How the uploader gained access remains unknown.

On November 17, 2026, two tampered releases of Microsoft’s agent-framework were removed from PyPI, the public registry for Python packages. With version 1.26.1 or 1.26.2 installed, starting Python was enough to run code designed to steal credentials from the machine and request access tokens for Azure and automated builds.

Wiz confirmed three cases in which victim data reached the attacker’s collection address, but the public reports did not establish whether anyone used a stolen token.

What happened

External Parties
webhook.site
Socket and Aikido
Internet
Azure Identity EndpointIMDS, IDENTITY_ENDPOINT
CI Pipelines
Installing Hosts
+ agent-framework project
+ releases 1.26.1 and 1.26.2
+ installs from the index
PyPI
PyPI Project
CI Job
Azure DevOps OIDC
GitHub Actions OIDC
Python Interpreter
.pth Collector
Credential Files
Process Environments

Replaying the agent-framework November 2026 intrusion

  1. 1

    Poisoned releases

    November 17, 2026, 20:35 to about 21:08 UTC

    Aikido says the uploader likely used valid publishing credentials to distribute two tampered Python packages. The added code was set to run when Python started.

  2. 2

    Local harvest

    From November 17, 2026, 20:35 UTC

    The collector is built to read environment variables whose names suggest secrets, the environments of up to 300 processes and up to 60 credential files, 80 in 1.26.2.

  3. 3

    Token requests

    From November 17, 2026, 20:35 UTC

    The payload asks the Azure identity endpoint for managed identity tokens for 12 resources, asks Azure DevOps for an OIDC token and, in 1.26.2, asks GitHub Actions for two; no source says a token was issued or used.

  4. 4

    Exfiltration and removal

    November 17, 2026, until about 21:20 UTC

    PyPI had stopped serving both releases by about 21:20 UTC. The next day Wiz reported that 17 of the 50 requests it examined came from three cases of victim data theft.

Impact

The two altered releases were available on PyPI for about 45 minutes. On November 18, Wiz reported that 17 of the 50 requests it examined represented three distinct cases of victim data theft. The number of installations and any subsequent use of stolen tokens remain unknown.

Could this have been prevented?

The assessed controls could have limited the impact of this incident.

Incident control assessments

0
Prevented
7
Contained
7
Not covered

How it could have been prevented

The same replay with the controls in place. Green marks where a step is refused, blue where it is bounded, and red where no control reaches it. Open a row to read the control, why it acts, and its caveat.

External Parties
webhook.site
Socket and Aikido
Internet
Azure Identity EndpointIMDS, IDENTITY_ENDPOINT
CI Pipelines
Installing Hosts
+ agent-framework project
+ releases 1.26.1 and 1.26.2
+ installs from the index
PyPI
PyPI Project
CI Job
Azure DevOps OIDC
GitHub Actions OIDC
Python Interpreter
.pth Collector
Credential Files
Process Environments

Replaying the agent-framework November 2026 intrusion

1 · Poisoned releases

2 Not covered

2 · Local harvest

1 Not covered

3 · Token requests

5 Contained3 Not covered3 on other clouds

4 · Exfiltration and removal

2 Contained1 Not covered3 on other clouds

Key facts

  • agent-framework 1.26.1 was published to PyPI at 20:35 UTC on November 17, 2026, and 1.26.2, a wheel only, at about 21:08 UTC, per Aikido and the PyPI project page
  • Aikido traced the uploads to edited wheels. A Microsoft maintainer confirmed both removals and said the team was investigating, according to the reply reproduced by FourWeekMBA. How the uploader gained access remains unknown
  • The .pth hook was built to run the collector at every Python start, reading up to 60 credential files (80 in 1.26.2) and the environments of up to 300 processes, per Aikido
  • The payload was written to request managed identity tokens for 12 Azure resources, an Azure DevOps OIDC token and, in 1.26.2, GitHub Actions OIDC tokens, per Aikido and Socket; no source said a token was issued, exchanged or used
  • On November 18, 2026, Wiz reported that 17 of the 50 requests it examined represented three distinct cases of victim data theft
  • Aikido reported about 190,000 monthly package downloads on November 17, 2026. The number of installations of the two tampered releases remains unknown

Sources

Every fact in this breakdown comes from the public reporting below. The replay is a model of that reporting, not a reconstruction of the environment it describes.

  1. 1.
    Malicious Microsoft Agent Package Was Live on PyPI ~60 MinFourWeekMBA · Nov 17, 2026 · NewsReproduces the Microsoft maintainer’s confirmation that both releases were removed and quotes the researcher’s warning about cached copies.
  2. 2.
    Microsoft agent-framework Compromised: Credential Stealer Targets Azure and CI PipelinesWiz Research · Nov 17, 2026 · ResearchAnalysis of 50 captured requests, including 17 requests attributed to three cases of victim data theft
  3. 3.
    MAL-2026-20101: Malicious code in agent-framework (PyPI)Open Source Vulnerabilities · Nov 17, 2026 · AdvisoryBoth affected versions and the startup hooks they installed
  4. 4.
    agent-framework PyPI package compromised with credential stealerSocket · Nov 17, 2026 · Researchpayload mechanics, credential targets, token audiences, exfiltration, IOCs
  5. 5.
    Two malicious agent-framework releases hit PyPI in 33 minutesAikido Security · Nov 17, 2026 · Researchtimeline, exposure window, packaging anomalies, payload mechanics, indicators, response
  6. 6.
    agent-framework project pagePython Package Index · Nov 18, 2026 · Status pagerelease dates, quarantine

The estate in the replay is illustrative and drawn at the level of attack stages; the victim's real environment is not public. Verdicts describe what a control does when it is in place before the incident. They are not an assessment of the victim's security program.

More cloud attack breakdowns

All breakdowns