Cybersecurity Research

Malicious Microsoft Agent Framework Packages on PyPI Steal Azure and CI Credentials

Wiz Research · 18 Nov 2026
Key Takeaway If any system installed agent-framework 1.26.1 or 1.26.2, treat every secret and cloud identity it could reach as stolen and rotate them.

Wiz Research has reported that two malicious versions of the Microsoft Agent Framework package, agent-framework, were uploaded to PyPI on November 17, 2026. Version 1.26.1 appeared at 20:35 UTC and 1.26.2 followed at 21:08 UTC, 33 minutes apart. Both had been removed by 21:30 UTC. According to The Hacker News, the versions have been quarantined on PyPI, and several security firms reported the incident, including Aikido, Chainguard, Endor Labs, OX Security, SafeDep, Socket, StepSecurity and Wiz.

The two reports give different download figures. Wiz puts the package at about 41,000 downloads a week, while The Hacker News says about 190,000 a month. The Hacker News describes agent-framework as the meta-package for Microsoft Agent Framework, an open-source toolkit for building and orchestrating AI agents in Python.

The malicious versions drop a .pth file into the Python site-packages folder. According to The Hacker News, it is named agent_framework_meta.pth. Python runs these files every time it starts, so the stealer executes whenever Python launches in that environment, even if the package is never imported. The Hacker News adds that this includes when pip itself runs. The code is disguised as SDK telemetry. It collects environment variables with names suggesting secrets, secret-looking values from other processes, and common credential files such as .npmrc, pip.conf, .netrc, .git-credentials and Docker config. It also requests Azure managed-identity and Azure DevOps OIDC tokens. Everything is sent in a single HTTPS request to a webhook.site address. The Hacker News says the data is compressed and encoded first, and cites SafeDep as noting that in an Azure DevOps pipeline the access token and OIDC request URI are enough to request a federated token, while on Azure compute the malware queries the managed identity endpoint and instance metadata service.

Version 1.26.2 changed the trigger file names, so searching only for the 1.26.1 names will miss it. It also added theft of GitHub Actions OIDC tokens in workflows with id-token: write. The Hacker News says it also widens the search for credential-related environment variables. Where an Entra ID federated credential trusts the workflow, those tokens can be exchanged for Azure access without any stored secret.

The root cause is unconfirmed, and The Hacker News likewise says it is unclear how the attacker got publishing access. Wiz notes there is no matching release or tag in the Microsoft repository, and 1.26.1 was a wheel only, suggesting it was built outside the normal release process. According to The Hacker News, OX Security suggested the attackers hijacked the wheel creation flow, and said the incident shows attackers targeting the AI developer ecosystem and its CI pipelines. The Hacker News adds this is the second Microsoft-related PyPI package compromised this year, after three malicious versions of durabletask were pushed in May 2026 by the TeamPCP group. Wiz confirmed the attacker's webhook was on a free tier that accepts at most 100 requests, and a maximum of 50 were captured. Even so, those requests can contain working cloud, CI and registry credentials.

Why it matters

Teams that treat stored secrets as the main risk will be caught out, because the stealer also pulls short-lived managed-identity and OIDC tokens that need no stored secret. Because the code runs on every Python start, checking whether the package was imported is not enough to rule out exposure. The focus on AI developer tooling and CI pipelines means build and runtime hosts need review for which cloud identities they can reach.

What to do

  • Check build and runtime hosts for agent-framework 1.26.1 or 1.26.2 and for .pth files in site-packages, including agent_framework_meta.pth and the changed 1.26.2 names.
  • Rotate any credentials, tokens and registry logins that were present on affected hosts, including .npmrc, .netrc, .git-credentials and Docker config contents.
  • Review Entra ID federated credentials and GitHub Actions workflows with id-token: write to see which identities affected hosts could reach.
  • Review outbound HTTPS logs for connections to webhook.site from build and runtime hosts.
supply chain PyPI Azure credential theft CI/CD GitHub Actions
Also reported by The Hacker News
Answering to more than one framework? Run them as one security and AI governance programme ->

Summarised by CISO AI from Wiz Research, with the same story also reported by The Hacker News, written with Claude Sonnet 5.5. We link back to every original so you can read it yourself.