What Happened
The Microsoft Agent Framework PyPI compromise hit a popular AI agent library on Tuesday evening. Attackers published agent-framework versions 1.26.1 and 1.26.2 on November 17, 33 minutes apart, The Hacker News reports. Each release dropped a .pth file into site-packages. Python runs these files on every interpreter start, even when no code imports the package. The exposure window ran from about 8:35 to 9:20 p.m. UTC.
The stealer collected environment variables, Azure CLI files, .npmrc, pip.conf, .git-credentials, Docker configs, and Hugging Face tokens. It pulled Azure managed-identity and Azure DevOps OIDC tokens and requested fresh ones. Version 1.26.2 added theft of GitHub Actions OIDC tokens. Data went to a hard-coded webhook.site URL. Aikido, Socket, Wiz, StepSecurity, and other firms flagged the releases independently, and PyPI quarantined both. The package draws about 190,000 downloads a month.
Why This Matters for Canadian Organizations
Canadian banks, insurers, government digital teams, and startups build AI agents on Azure. Many CI pipelines install the latest version of a dependency on every run. Any build server or developer laptop pulling the package during the window handed over cloud identities, not only static secrets. Because the stealer minted new tokens, rotating stored keys alone leaves gaps.
Under PIPEDA and Quebec’s Law 25, a stolen Azure identity with access to customer data triggers a breach assessment. OSFI Guideline B-13 expects federally regulated financial institutions to control third-party software risk, and unpinned AI packages fall squarely inside it.
What to Do
Search lockfiles, build logs, and package caches for agent-framework 1.26.1 or 1.26.2. Isolate affected hosts and CI runners. Pin to 1.26.0 and rebuild from a clean image. Search proxy and DNS logs for webhook.site traffic on November 17. Rotate exposed credentials from a clean machine. Review Entra ID sign-in logs, managed-identity activity, and Azure DevOps service connections. Audit GitHub Actions workflows deploying to Azure. Require pinned versions and hash checks for every Python dependency. Read our Trends coverage and today’s Daily Brief for related stories.






