Microsoft Agent Framework Attack: Check These Two Python Package Versions

Malicious Microsoft Agent Framework releases targeted cloud and CI credentials. Check affected versions, understand the startup trigger, and plan your response.

Escrito por
Matt Gonzales
Matt Gonzales
Nov 19, 2026
Microsoft Agent Framework Attack: Check These Two Python Package Versions

The compromised package releases targeted credentials available to developer and build environments. Image: Generated via OpenAI/ChatGPT

A poisoned AI development package could steal cloud credentials before a developer even used it.

Two malicious releases of Microsoft’s agent-framework Python package appeared on PyPI on Nov. 17, targeting credentials accessible to developer machines and automated build systems. Versions 1.26.1 and 1.26.2 have since been removed, according to a GitHub security advisory published Nov. 18.

For teams that installed either version, removing the package is only the beginning. The urgent question is which credentials the affected environment could reach and whether those credentials remain usable.

Two malicious releases, 33 minutes apart

Endor Labs’ analysis places the first upload at 20:35 UTC and the second at 21:08 UTC. The researchers found malicious additions to the distributed package rather than a replacement of the framework’s core functionality.

The distinction matters: Software can keep working while its installation introduces a separate threat. Endor said the releases retained their dependency on agent-framework-core version 1.26.0.

Advertisement

Machine-learning tools have faced supply-chain attacks before, including a compromised PyTorch dependency that TechRepublic covered. That earlier incident is context, not evidence of a shared attacker or technique. The sources reviewed do not establish how access to publishing was obtained in this case.

Why launching Python could trigger the theft

Endor found that both releases added executable .pth startup hooks. Python processes executable lines in these files during normal interpreter startup, allowing the malicious helper to run without the developer having to import Agent Framework.

The second release moved its payload into different files while leaving the package’s initialization file identical to the clean version, Endor reported. Reviewing only that file could therefore miss the malicious additions.

The GitHub advisory describes the collection of environment variables and credential files, alongside Azure and build-system tokens. The second release also targeted GitHub Actions tokens. This is a risk to affected development and cloud environments, not evidence that every Microsoft account or Windows device was compromised.

Advertisement

Must-read security coverage

Check exposure, then revoke access

The advisory identifies 1.26.1 and 1.26.2 as malicious and 1.26.0 as the last clean release. It advises treating environments that installed either malicious version as exposed and rotating credentials reachable from them.

Security teams should coordinate that response across development, cloud operations, and identity owners:

  • Identify affected installations. Review dependency records, build logs, and deployed images for the two versions. Check automated pipelines as well as developer workstations.
  • Contain before rebuilding. Preserve relevant evidence and keep suspect environments from receiving replacement secrets. Rebuild from verified dependencies rather than assuming package removal reverses credential theft.
  • Scope the credentials. Establish which accounts and services the environment could access, then revoke or rotate exposed credentials from a trusted system.
  • Review subsequent activity. Look for unexpected cloud actions, repository changes, and pipeline activity associated with those identities.
Advertisement

Reduce the access an infected build can inherit

The broader lesson is permission scope. TechRepublic’s coverage of enterprise AI agent security gaps examines why access controls deserve as much scrutiny as new capabilities. This incident reaches the development tools behind those systems, making the build environment part of that review.

For IT leaders, a useful follow-up is to map which development jobs can reach production services. Separate test credentials from production access, document who owns each service identity, and avoid giving experimental projects the same privileges as established applications. These are risk-reduction measures, not substitutes for investigating an affected installation.

TechRepublic’s reporting on long-lived cloud credentials also explains why reusable secrets can extend an attacker’s opportunity. Review credential lifetime and permissions together: Reducing either can limit exposure, but neither makes a compromised environment safe to keep using.

Advertisement

Removing a malicious release from a registry prevents some future installations. It does not invalidate secrets already taken. For affected teams, recovery ends with restored trust in the environment and its credentials, not simply a clean dependency list.

Related reading: Learn why AI agents create insider-security blind spots and where identity governance can fall short.

Matt Gonzales

Matt Gonzales is a technology journalist, editor, and content strategist with more than a decade of experience covering emerging technologies, enterprise IT, cybersecurity, artificial intelligence, and workplace innovation. As Managing Editor for eWeek and TechRepublic, he leads editorial strategy and newsroom operations while helping business and IT leaders navigate an evolving technology landscape. Throughout his career, Matt has held leadership roles overseeing content development, editorial planning, and newsroom operations across digital publications and enterprise media organizations. Before joining TechnologyAdvice, he served as an editor at SHRM, where he covered workplace trends and emerging technologies, and as Lead Writer and Editor for Marine Corps Systems Command, where he reported on defense technologies, innovation initiatives, and government technology programs. Matt's expertise spans cybersecurity, enterprise technology, AI, B2B software, technical writing, and digital publishing. He has reported on major technology developments, including the rapid evolution of generative AI, helping readers understand both the opportunities and risks associated with emerging technologies. His work combines deep research, editorial rigor, and practical business insights to make complex technical topics accessible to a broad audience. An award-winning journalist, Matt has earned recognition for excellence in reporting and editorial leadership. He holds a Bachelor of Science in Communication with a concentration in Journalism from East Carolina University and continues to focus on delivering trusted analysis and actionable insights for technology, cybersecurity, and business professionals.