Microsoft package attacker appears to have used certificate, Wiz says


Wiz says an attacker appears to have used a Microsoft release-pipeline certificate and private key to publish malicious agent-framework versions 1.26.1 and 1.26.2, which were subsequently quarantined.
An attacker appears to have used a compromised client certificate and private key for Microsoft’s release pipeline to publish two malicious versions of its agent-framework Python package, cloud security company Wiz says. The pipeline is the internal service Microsoft uses to sign and publish the package. How the attacker obtained the credentials remains unknown.
The releases were published through Microsoft’s account on the Python Package Index (PyPI) and later quarantined. The package supports Microsoft Agent Framework, which is designed for building superintelligence (SI) agents and applications that use multiple agents.
According to Wiz’s timeline, clean version 1.26.0 was published on 12 November at 18:25 UTC. Malicious version 1.26.1 followed on 17 November at 20:35 UTC and 1.26.2 at about 21:08 UTC; both were unavailable on PyPI by about 21:30 UTC.
A Microsoft Agent Framework maintainer said the compromised releases had been removed and an investigation was underway, SecurityWeek reported. Wiz said it shared its findings with Microsoft on 17 November and updated its analysis on 18 November at 14:00 UTC with an updated root cause and analysis of exfiltrated data.
Microsoft’s durabletask Python package was compromised in May after its PyPI token was stolen. Wiz says it has not linked the two incidents.
Earlier: PyPI quarantines two malicious Microsoft package releases

Researchers identified agent-framework versions 1.26.1 and 1.26.2, published on 17 November 2026, as malicious. Endor Labs says their startup hooks run a credential stealer whenever Python starts in an affected environment.
Wiz said the attacker’s first publishing attempt, from Amazon Web Services, was blocked by the pipeline’s address filtering. A second attempt from Microsoft-owned address space succeeded.
The malicious packages installed a startup file that ran a credential stealer whenever Python started in an affected environment, even if the framework was never imported. The malware sought secrets in environment variables and credential files, including those for Azure, npm, Git, Docker and Hugging Face. It also requested Azure managed-identity and Azure DevOps tokens; version 1.26.2 additionally targeted GitHub Actions identity tokens. Where an Entra ID federated credential trusts the workflow, those tokens can be exchanged for Azure access without a stored secret.
Wiz analyzed 50 retained requests sent to the attacker’s data-collection address. It said 17 represented three unique successful thefts of victim data; the others came from the attacker’s machines, sandbox environments, vendor scanning and tests. Those requests cover only part of the operation. The package’s close to 200,000 monthly downloads are for the package overall, not a count of malicious-version installations or victims.
Researchers advise anyone who installed either malicious release to treat it as a credential compromise, rebuild from clean version 1.26.0 and rotate secrets the affected systems could access. Wiz also advises checking dependency records, build logs, virtual environments and container images, then reviewing reachable Azure identities and affected GitHub Actions workflows for misuse.
3 min