Executive Summary
On November 17, 2026, threat actors published two malicious versions (1.26.1 and 1.26.2) of the widely-used Microsoft agent-framework PyPI package within a 33-minute window, compromising a package with roughly 190,000 monthly downloads. The tampered releases injected Python startup hooks via .pth files that silently executed a credential stealer on every Python interpreter launch—regardless of whether the package was explicitly imported. The stealer harvested Azure CLI tokens, managed-identity tokens, Azure DevOps OIDC tokens, GitHub Actions OIDC tokens, environment variables, and configuration files, then exfiltrated all data Base64-encoded and zlib-compressed to a hard-coded webhook.site endpoint. This marks the second Microsoft-related PyPI compromise in 2026, following the TeamPCP-linked durabletask attack in May. The incident exposes critical gaps in CI/CD pipeline security and cloud-identity protection across AI development workflows.
This attack signals an accelerating adversarial focus on the AI developer ecosystem and the supply chains feeding it. As agentic AI frameworks like Microsoft's agent-framework become foundational infrastructure, their PyPI packages represent high-value, low-friction targets for credential theft at scale—particularly in automated CI/CD environments where identities carry broad cloud permissions.
Why This Matters Now
AI agent frameworks are rapidly becoming critical infrastructure in enterprise cloud environments, yet their open-source supply chains receive far less scrutiny than production code. With two Microsoft PyPI packages compromised in a single year and attackers actively targeting CI/CD-issued cloud-identity tokens, organizations building or deploying agentic AI systems face immediate, concrete credential exposure risk that traditional perimeter controls do not address.
Attack Path Analysis
Attackers compromised Microsoft's agent-framework PyPI package by obtaining unauthorized publishing access to inject a credential-stealing payload into versions 1.26.1 and 1.26.2, which executed on every Python interpreter start via malicious .pth files. The stealer silently harvested Azure CLI tokens, managed-identity tokens, OIDC tokens, CI/CD secrets, and cloud metadata, then exfiltrated all collected data to a hard-coded webhook.site endpoint via HTTPS POST, enabling downstream account takeover, unauthorized cloud resource access, and potential persistent access to Azure and GitHub environments.
Kill Chain Progression
This analysis maps confirmed threat intelligence to the full cloud kill chain to show where defensive gaps would emerge as an attack progresses.
Initial Compromise
Description
Threat actors obtained unauthorized publishing credentials or hijacked the wheel build pipeline for the agent-framework PyPI package. Two malicious versions (1.26.1 and 1.26.2) were published 33 minutes apart on November 17, 2026. Each version embedded a credential-stealing payload delivered via Python startup hook (.pth files in site-packages), causing the malware to execute on every Python interpreter start in any environment that installed the compromised package. With approximately 190,000 monthly downloads, the blast radius was significant across developer and CI/CD environments.
MITRE ATT&CK® Techniques
Supply Chain Compromise: Compromise Software Dependencies and Development Tools
Event Triggered Execution: Unix Shell Configuration Modification
Unsecured Credentials: Credentials In Files
Unsecured Credentials: Container API
Steal Application Access Token
Exfiltration Over C2 Channel
Obfuscated Files or Information
Valid Accounts: Cloud Accounts
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
NIST SP 800-53 Rev 5 – Supply Chain Controls and Processes
Control ID: SR-3
CISA Zero Trust Maturity Model 2.0 – Continuous Monitoring of Application Behavior and Credential Usage
Control ID: Applications & Workloads – Pillar: Visibility and Analytics
NIS2 Directive – Supply Chain Security and Incident Handling
Control ID: Article 21(2)(a) and 21(2)(d)
DORA (EU 2022/2554) – Third-Party Software Dependency Risk Controls
Control ID: Article 28 – ICT Third-Party Risk Management
PCI DSS 4.0 – Software Integrity and Third-Party Component Review
Control ID: Requirement 6.3.3 and 12.3.4
ISO/IEC 27001:2022 – Secure Software Supply Chain and Cloud Credential Governance
Control ID: Annex A 8.30 – Outsourced Development / A 5.23 – Information Security for Use of Cloud Services
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Information Technology/IT
Supply-chain compromise of Microsoft's PyPI agent-framework package exposes IT environments to cloud credential exfiltration via Python startup hooks, targeting Azure CLI tokens, managed identities, and CI/CD pipeline secrets.
Computer Software/Engineering
Software engineering teams using the 190,000-monthly-download agent-framework package face infostealer risk targeting .git-credentials, .npmrc, Docker configs, and GitHub Actions OIDC tokens across affected build pipelines.
Financial Services
Financial sector cloud workloads face credential theft of Azure managed-identity tokens and IMDS metadata, violating PCI 4.0 and NIST 800-53 egress and zero-trust compliance controls mapped in validated threat intelligence.
Health Care / Life Sciences
Healthcare organizations running Azure-hosted Python workloads risk HIPAA-regulated credential exposure through compromised agentic AI pipelines, with exfiltrated environment variables and identity tokens enabling unauthorized cloud lateral movement.
Sources
- Attackers Compromise Microsoft's Agent Framework PyPI Package to Steal Cloud Credentialshttps://thehackernews.com/2026/11/attackers-compromise-microsofts-agent.htmlVerified
- Two Malicious agent-framework Releases Hit PyPI in 33 Minuteshttps://www.aikido.dev/blog/two-malicious-agent-framework-releases-hit-pypi-in-33-minutesVerified
- Microsoft agent-framework Compromised on PyPI - November 2026https://www.chainguard.dev/unchained/microsoft-agent-framework-compromised-on-pypi-november-2026Verified
- agent-framework Compromised Software Supply Chain Attackhttps://www.endorlabs.com/learn/agent-framework-compromised-software-supply-chain-attackVerified
- Breaking: Hijacked Releases of Microsoft's Official agent-framework Steals Azure and CI Credentialshttps://www.ox.security/blog/breaking-hijacked-releases-of-microsofts-official-agent-framework-steals-azure-and-ci-credentials/Verified
- agent-framework PyPI Package Compromised with Credential Stealerhttps://socket.dev/blog/agent-framework-pypi-package-compromised-with-credential-stealerVerified
- Malicious Version of Microsoft's agent-framework Published to PyPIhttps://www.wiz.io/blog/malicious-version-of-microsofts-agent-framework-published-to-pypiVerified
- Microsoft agent-framework PyPI Package Compromisedhttps://www.stepsecurity.io/blog/microsoft-agent-framework-pypi-package-compromisedVerified
- Microsoft agent-framework PyPI Compromise - SafeDep Analysishttps://safedep.io/blog/microsoft-agent-framework-pypi-compromiseVerified
- Defending New Vectors: Threat Actors Attempt SQL Server to Cloud Lateral Movementhttps://www.microsoft.com/en-us/security/blog/2023/10/03/defending-new-vectors-threat-actors-attempt-sql-server-to-cloud-lateral-movement/Verified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.
Aviatrix Zero Trust CNSF is directly relevant because this supply chain compromise depended on unrestricted outbound egress, open east-west reachability across cloud workloads, and uncontrolled access to metadata services to succeed at scale. By enforcing workload-level segmentation and identity-aware egress controls, Aviatrix would likely have constrained the attacker's ability to harvest credentials across environments and exfiltrate them to an external webhook endpoint.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: CNSF fabric-level visibility across cloud workload environments could help surface anomalous runtime behavior introduced by the malicious package, and segmentation boundaries around build and CI/CD environments would likely limit how far the initial execution foothold could reach across connected workloads or shared infrastructure.
Control: Zero Trust Segmentation
Mitigation: Zero Trust segmentation enforced around compute environments running these workloads could reduce the scope of token acquisition by limiting which identities and metadata endpoints a given workload is permitted to reach, making it harder for the malicious payload to freely query IMDS or federated token endpoints across multiple pipeline contexts.
Control: East-West Traffic Security
Mitigation: East-west traffic enforcement across cloud environments would likely reduce the attacker's ability to use harvested credentials to freely traverse service boundaries, as segmentation policies between workloads, pipelines, and cloud services could constrain which authenticated paths are permitted even when valid tokens are presented.
Control: Multicloud Visibility & Control
Mitigation: Multicloud visibility and control over outbound traffic could make the anomalous HTTPS POST to webhook.site more detectable, and enforced egress policies that restrict permitted outbound destinations by FQDN or category would likely reduce the attacker's ability to reliably reach an external callback endpoint from within cloud workload environments.
Control: Egress Security & Policy Enforcement
Mitigation: Enforced egress security policies that restrict outbound HTTPS connections to approved destinations would likely constrain or disrupt the single-POST exfiltration to webhook.site, reducing the attacker's ability to successfully transmit harvested credentials and tokens out of the compromised environment even when the payload has already executed.
If prior CNSF controls had constrained egress and reduced east-west reachability, the residual risk would likely be scoped to environments where tokens were acquired before segmentation or egress policies interrupted the attacker's workflow, reducing but not eliminating the risk of unauthorized Azure subscription access or pipeline manipulation.
Impact at a Glance
Affected Business Functions
- AI/ML Development Pipelines and Agent Orchestration Workflows
- Cloud Identity and Access Management (Azure IAM, Managed Identity, OIDC)
- CI/CD Pipeline Integrity (Azure DevOps, GitHub Actions)
- Developer Credential and Secret Management
Estimated downtime: 3 days
Estimated loss: N/A
Broad credential exfiltration affecting any environment that installed agent-framework versions 1.26.1 or 1.26.2 between approximately 20:35 and 21:20 UTC on November 17, 2026. Stolen data categories include: Azure CLI credentials and configuration JSON files (~/.azure/*.json), Azure DevOps SYSTEM_ACCESSTOKEN and OIDC federated tokens, Azure Managed Identity access tokens harvested from IMDS at 169.254.169.254 as well as IDENTITY_ENDPOINT and MSI_ENDPOINT on App Service and Functions, GitHub Actions OIDC tokens (version 1.26.2), environment variables across the entire process environment including secrets injected by CI runners, credential files including .npmrc, pip.conf, .netrc, .git-credentials, .docker/config.json, Hugging Face tokens, and .env files. The package had approximately 190,000 monthly downloads, meaning the blast radius could span thousands of organizations using Python-based AI agent development workflows. All harvested data was compressed, Base64-encoded, and exfiltrated to a hard-coded webhook.site endpoint. Because the malware also issues new OIDC and managed-identity token requests at runtime, rotating stored secrets alone is insufficient without also revoking issued tokens and auditing sign-in logs. The incident is the second Microsoft-related PyPI supply chain compromise in 2026, following the TeamPCP durabletask compromise in May 2026.
Recommended Actions
Key Takeaways & Next Steps
- • Enforce egress security and FQDN-level policy (Egress Security & Policy Enforcement): Deploy cloud-native egress controls that restrict outbound HTTPS traffic to approved destinations only. Webhook.site and other generic data-relay domains should be explicitly blocked via FQDN filtering, preventing credential exfiltration even when a malicious payload executes successfully within a cloud workload or CI/CD runner.
- • Apply Zero Trust Segmentation to CI/CD and compute workloads (Zero Trust Segmentation): Enforce identity-based, least-privilege microsegmentation policies on Azure DevOps agents, App Service environments, and Azure Functions so that managed-identity tokens are scoped to the minimum required resources and workloads cannot freely access IMDS or cross-service endpoints without explicit policy allowance.
- • Enable multicloud visibility and anomaly detection on outbound traffic patterns (Multicloud Visibility & Control): Instrument centralized traffic observability across all cloud environments to detect anomalous outbound HTTPS POST requests to unexpected external endpoints, particularly those carrying compressed or encoded payloads. Baselining normal egress patterns enables rapid identification of data-relay callout behavior characteristic of credential stealers.
- • Deploy inline IPS with threat signatures for known malicious payload patterns (Inline IPS / Suricata): Use inline intrusion prevention with up-to-date signatures to inspect outbound traffic for known stealer exfiltration patterns, zlib-compressed Base64 payloads, and connections to known malicious or suspicious webhook infrastructure, adding a detection and blocking layer independent of application-level controls.
- • Leverage CNSF fabric for agentic AI and cloud-native enforcement context (Cloud Native Security Fabric): As AI agent frameworks become critical supply chain components, apply real-time inline enforcement policies that monitor and control the network behavior of AI development toolchains. Treat PyPI-sourced packages executing in cloud environments as untrusted until verified, enforcing runtime policy that prevents unauthorized credential file reads and outbound data transmission from Python interpreter contexts.



