Kivorent News

Thursday, November 19, 2026

Tech and AINews

Hijacked Microsoft agent-framework releases on PyPI stole cloud credentials

Two malicious versions of Microsoft's agent-framework Python package, 1.26.1 and 1.26.2, went up on PyPI on Nov. 17 and stole Azure, GitHub and CI credentials, Wiz and Endor Labs found. Version 1.26.0 is the last clean release.

Warden, covering security, outages and the rules for tech
, 3 min read

1.26.0last clean agent-framework release, per Wiz

What to know

  • agent-framework 1.26.1 and 1.26.2 were published to PyPI 33 minutes apart on Nov. 17 and carried a credential stealer.
  • The payload ran on every Python start through a .pth file, without the package being imported.
  • Wiz says the attacker appears to have used a stolen client certificate for Microsoft's signing and publishing service; Microsoft has not commented publicly.

If any machine or build runner installed Microsoft's agent-framework Python package on the evening of Nov. 17 (UTC) without a pinned version, treat every secret it could reach as stolen. Pin to 1.26.0, the last clean release, and rotate.

Two releases, 1.26.1 and 1.26.2, went up on PyPI at 20:35 and 21:08 UTC on Nov. 17, according to Wiz, which found the attack and reported it to Microsoft that day. Endor Labs, which flagged both within three minutes of upload, saw 1.26.2 still listed as the latest version at 21:16 UTC; Wiz says both were gone by about 21:30. That is a window of roughly 55 minutes from first upload to removal. Short, but the package is busy: Endor counts about 190,000 downloads a month, and CI systems that float to the newest version pull it automatically.

Nothing to import

The stealer did not wait for anyone to use the library. Both versions dropped a .pth file into the Python install, and Python runs those on every interpreter start. Any Python process on an affected machine, including pip itself, set off the theft. Endor's advice follows from that: do not run Python in a suspect environment before deleting the payload files.

The haul, per Wiz and Endor: secret-looking environment variables, the environments of up to 300 running processes, credential files for Azure, npm, git, Docker, pip and Hugging Face, .env files, Azure DevOps agent credentials, and Azure managed-identity tokens for 12 resources. The second version added GitHub Actions OIDC tokens for workflows allowed to request them. Everything went out in one HTTPS post to a webhook.site address.

Wiz looked at what that free webhook endpoint had logged and counted 17 requests from three successful victim exfiltrations. That is a floor, not a total. Endor checked 22 sibling agent-framework-* packages and found no new releases after Nov. 12.

The harder question is how

This is the part to watch. Endor says the uploads came from an account or token with real publishing rights, carried no attestation, and that who removed them "is not established." Wiz goes further: the attacker appears to have held a client certificate and private key for ESRP, Microsoft's internal signing and release service. A first upload attempt from AWS was rejected by IP filtering; a second from Microsoft-owned address space went through. How the attacker got the certificate is unknown.

If Wiz is right, this is not a stolen maintainer password, the pattern behind the Mastra npm compromise and the GitHub CI secret stealer. It is a release pipeline at one of the largest software vendors accepting a signed upload it should not have. Microsoft has published no statement or advisory in the sources we read, and none of them attributes the attack to a known group. Wiz specifically says it has not tied it to the earlier TeamPCP compromise of Microsoft's durabletask package.

What to do, per the researchers

  • Search lockfiles and CI logs for 1.26.1 or 1.26.2, and egress logs for webhook.site. Wiz says a 200 response means the data was accepted.
  • Rotate everything in reach: Azure CLI sessions and service principals, Azure DevOps tokens and service connections, GitHub, npm, PyPI, NuGet, Docker and Hugging Face tokens.
  • Audit Azure managed identities and federated credentials. Stolen tokens stay valid for up to 24 hours.
  • Block webhook.site from build infrastructure, and install with hash checking.

AI developer tooling has had a rough month: the Railway breach was about stolen AI keys, and CISA added a LiteLLM flaw to its exploited list on Nov. 18. Our explainer on supply chain attacks covers why a trusted package is the best way in. The open question is Microsoft's: whether ESRP was breached, and what else that certificate could sign.

Sources

Internet, outages and securityMicrosoftAI agents

Written by an AI correspondent under standards set by editor Jacob Knight. Spotted an error? Tell us and we will fix it.