Sponsored by Unbiased HeadlinesFacts. Not Spin.
← All Posts

There you have it! Microsoft's own official agent-framework package on PyPI shipped a credential …

November 18, 2026 · 0 likes · 0 comments
AI Cybersecurity
There you have it! Microsoft's own official agent-framework package on PyPI shipped a credential stealer this week.

Full story, just the facts: https://lnkd.in/eguWpRHB

By the way, if you can't keep up, check out UBHCyber.com!

Two poisoned versions, 1.26.1 and 1.26.2, went up on Tuesday, Nov. 17, 33 minutes apart, and both were quarantined within about 45 minutes. This was not some typosquat with a funny name. It came through Microsoft's own PyPI account on a package that pulls around 200,000 downloads a month, so lock files and trust in the project name did nothing for anyone who resolved those versions.

And look at what it went after. Environment variables with TOKEN, SECRET, KEY, AZURE, AWS, GITHUB and OPENAI in the name, up to 60 credential files, Hugging Face tokens, .env files, secrets from other running processes, and then it asked the platform for fresh Azure managed identity and OIDC tokens on top of that. It dropped a .pth file so it ran every time Python started, even pip itself, while the framework kept working like nothing happened.

That is exactly the kit people use to build AI agents, and agents are the thing we load up with API keys, cloud credentials and access to everything. I run agents every day that hold keys to real systems, so when the official toolkit from Microsoft becomes the delivery vehicle, the agent stack is now the target and every builder pulling dependencies automatically is in the blast radius.

Microsoft has not said how the attacker got publishing access. One security firm, OpenSourceMalware, believes that access may still be live. Microsoft and PyPI have not confirmed that. Nobody knows how many machines pulled the bad versions.

If you installed either version, the security firms are clear: treat it as a credential compromise, rebuild clean on 1.26.0 and rotate everything that environment could reach. My own view is that pinning versions and checking hashes should be mandatory for any agent you run in production, because "official" clearly is not a security control anymore.

How many of your agent pipelines would have pulled 1.26.1 on Tuesday without anyone noticing?
View original on LinkedIn →