On November 17, 2026, malicious code acting as a secret spy was embedded in Microsoft's official Python package 'agent-framework'. We review the nature of this download-and-execute attack and essential security knowledge.
Imagine receiving a cooking ingredient kit from a famous major corporation that you usually trust and use. What if you simply opened the box and placed it on the dining table, only to discover that a memo containing your home safe key and front door password was secretly transmitted to someone else—even though you haven’t started cooking or even unpacked the ingredients?
A strikingly similar event actually occurred in the software development world. Someone secretly planted an “information thief” inside the official toolset provided by global tech giant Microsoft [Source 18]. Let’s break down the details of this security incident that shocked developers worldwide in a very easy-to-understand way.
Why Is This Important?
Just as we download apps verified for safety from the Apple App Store or Google Play Store when using our smartphones, programmers also build programs by pulling in countless open-source tools. In this case, malicious code was hidden inside ‘agent-framework’, an official Microsoft package registered on the Python Package Index (PyPI), the official software repository for the Python programming language used by developers [Source 3, Source 18].
To put it in perspective, it is as if someone mixed impurities into the core food distribution network jointly used by catering chains worldwide. This package is widely used across global development environments, being downloaded nearly 200,000 times every month [Source 3]. The moment a version containing malicious code is installed on a company’s or developer’s computer or automated server (CI/CD environment, continuous integration and deployment environment) using this tool, a nerve-wracking situation unfolds where sensitive information like cloud service access credentials and secret keys can be entirely stolen [Source 17, Source 18]. Beyond a developer’s simple personal mistake, this was a major supply chain security accident that threatened the digital safety of numerous end-users relying on the services they built.
Understanding Made Easy: A Micro-Spy Hiding in the Delivery Box
A software supply chain attack is like intercepting a delivery vehicle from a trusted major distributor and secretly slipping a meticulously disguised wiretapping device inside an authentic box.
Put simply, the operation mechanism of this incident can be broken down into everyday analogies:
- The Trap of Trust: Developers downloaded the necessary tools as usual (
pip installcommand), trusting the brand reliability of Microsoft and its official repository [Source 18]. - Invisible Infiltration: Normally, malicious code operates when a program is directly executed or a specific function is invoked. However, this malicious code utilized a Python startup hook called a
.pthfile (a technology that automatically runs code when a program starts) [Source 7, Source 18]. This was like an ultra-miniature wiretap that operates automatically just by bringing the delivery box into a room without even opening it, meaning the malicious code executed automatically in the Python environment simply by installing the package, even if the developer never imported or explicitly called it in their code [Source 18]. - Secret Information Leakage: The spy program, awakened stealthily in this manner, rapidly scraped passwords stored in computer environment variables or critical configuration files, along with cloud control permissions (such as Azure DevOps, Azure managed identity, and GitHub Actions secrets), transmitting them instantly to an attacker’s external server via a webhook [Source 7, Source 17, Source 18].
Current Situation and Incident Details
According to the security industry and foreign media reports, this meticulous supply chain compromise occurred on November 17, 2026 [Source 3].
- Time of Occurrence and Versions: Microsoft’s official metapackage
agent-frameworkversions 1.26.1 and 1.26.2 were registered sequentially on PyPI with just a 33-minute interval [Source 3, Source 16, Source 18]. Hidden inside both versions was a credential stealer designed to stealthily intercept user authentication credentials [Source 3]. - Swift Response: Fortunately, thanks to rapid detection by global security experts and automated monitoring systems, the two malicious files were urgently quarantined and removed by Microsoft and repository administrators just 45 minutes after appearing [Source 3, Source 16].
- Scope of Impact and Targets: This malicious code specifically targeted Azure-related authentication information and automated secret keys in GitHub Actions, which are widely used in cloud infrastructure environments [Source 7, Source 17, Source 18].
What Happens Next? (Secure Response Methods)
This lightning-fast supply chain attack delivers a stark reminder of the security maxim: “In the digital world, no one can be 100% trusted.” Developers or companies that handled the affected package during this period must immediately take the following response actions [Source 7]:
- Version Pinning: Thoroughly avoid the vulnerable versions in question and firmly pin the version back to the verified safe previous release, 1.26.0 [Source 7].
- Comprehensive Secret Rotation: If the package was installed even once in a development environment containing the malicious version, Azure-related credentials and GitHub Actions secrets must be immediately rotated to new values to guard against potential leakage [Source 7].
- Strengthened Supply Chain Monitoring: Moving forward, the adoption of advanced security solutions that verify package integrity in real-time across the entire CI/CD pipeline is accelerating globally, moving beyond complacency rooted merely in famous open-source branding.
AI Perspective
Easy to dismiss as a problem concerning only developers, this incident serves as a representative slice showing how intricately connected the foundation of trust is in modern digital society. Behind the smartphone apps, web services, and cloud systems we use every day lie thousands of open-source packages intertwined like a spiderweb. If a single small screw (package) shakes, the entire giant building (service) can be threatened. Moving forward, a supply chain security framework that transparently and rigorously verifies the reliability of the tools we import is more urgent than ever, matching the importance of coding skills themselves.
References
- Microsoft’s agent-framework PyPI package Compromised with Credential Stealer [Source 1]
- Secure PyPI Packages - 16K+ Projects From PyPI [Source 2]
- Microsoft agent-framework Compromised: Credential Stealer … [Source 3]
- PyPI agent-framework 1.26.1: Credential Stealer Fix … [Source 7]
- Inside the LiteLLM 1.107.0 supply chain compromise: Credential theft… [Source 11]
- Download Microsoft Visual C++ 2010 Service Pack 1 Redistributable… [Source 14]
- LiteLLM PyPI Supply Chain Attack — Credential Stealer in… — al-ice.ai [Source 15]
- Microsoft’s agent-framework on PyPI shipped a credential … [Source 16]
- Two malicious agent-framework releases on PyPI carried a … [Source 17]
- Microsoft agent-framework Compromised Twice on PyPI [Source 18]
- agent-framework
- azure-sdk
- microsoft-ai-tools
- Yes, it only executed when explicitly imported in code.
- No, it executed automatically when Python started or upon installation.
- It only ran when opening the smartphone app.
- Format and reinstall the computer
- Pin version to 1.26.0 and rotate major passwords and secrets
- Delete Microsoft account