ReadingResearchRadarInvestment framework
Sign in / Sign up
← Back to reading
NewsMaterial2 min readDisconfirmAI Editorial

Microsoft AI Agent Framework Hit by Supply Chain Attack Stealing Cloud Credentials

Malicious versions of Microsoft's official agent-framework were briefly available on PyPI, embedding code that steals Azure and CI/CD credentials from developer environments.

2026-11-18

Microsoft's official AI agent development framework, "agent-framework," suffered a supply chain attack on the Python Package Index (PyPI). Independent analyses by security firms Wiz, Socket, Aikido, and StepSecurity revealed that versions 1.26.1 and 1.26.2 contained malicious code designed to steal cloud service and Continuous Integration/Continuous Deployment (CI/CD) credentials.

The compromise occurred between 20:35 and 21:20 UTC on November 17, 2026. During this window, the infected versions were available for download. The malware exploited Python's .pth file mechanism to execute automatically whenever the Python interpreter started, without requiring an explicit import of the library. Once active, it scanned environment variables for sensitive information (such as those containing TOKEN, SECRET, KEY, AZURE, or AWS) and local configuration files (like ~/.azure, .npmrc, and .git-credentials), exfiltrating this data to external servers.

The impact extends to any development environment that installed or updated agent-framework during that timeframe. As a core tool for building multi-agent workflows, the package sees approximately 190,000 to 200,000 monthly downloads, creating a significant potential exposure surface. The latest version on PyPI has since been reverted to the clean 1.26.0 release. Microsoft has not yet issued a formal statement, though related GitHub repositories temporarily returned 404 errors, indicating ongoing investigation.

Teams potentially affected should immediately take several steps: first, check lockfiles, CI logs, and container images for versions 1.26.1 or 1.26.2; second, if infection signs are found, completely rebuild virtual environments and images rather than just deleting files; finally, rotate all secrets accessible from the affected systems, including Azure service principals, GitHub tokens, Docker credentials, and API keys. Notably, according to Wiz's analysis, stolen Azure tokens may remain valid for up to 24 hours, so even after revoking federated credentials, Entra ID login activities must be checked to confirm no unauthorized access occurred.

Sign in / Sign up
ReadingResearchRadarInvestment framework

Sources

  • kiberblick.deKIberblick↗
  • t3n.de↗
Continue researching →