Two malicious versions of Microsoft's official Python package for its Agent Framework were published this week on the Python Package Index, exploiting a release pipeline certificate to steal cloud and developer credentials before swift removal.

  • Malicious package versions signed with Microsoft release pipeline certificate
  • Stealer targets Azure, GitHub, Docker, npm tokens and environment secrets
  • Users urged to revert to safe versions and rotate exposed credentials

What happened

Two malicious versions of Microsoft’s official Python package for the Agent Framework AI toolkit, versions 1.26.1 and 1.26.2, were uploaded to the Python Package Index using Microsoft’s own publishing account. These updates, live briefly on Tuesday, contained malware designed to steal cloud platform and developer credentials by exploiting a client certificate and private key from Microsoft’s internal Release Pipeline system.

Though quickly removed, the infected packages included a .pth file enabling credential theft even if the framework itself was never imported. The malware harvested secrets from environment variables and specific service credentials, including Azure, GitHub Actions, Docker, npm, and Hugging Face tokens. The stolen data was transmitted to an attacker-controlled webhook, demonstrating a sophisticated supply chain attack leveraging trusted Microsoft infrastructure.

Why it matters

This compromise highlights a critical vulnerability in software supply chains where attackers can misuse internal build systems and certificates to distribute malicious versions of trusted open-source software. Given the Agent Framework’s monthly installation volume near 200,000, the impact could be widespread, especially for cloud-centric development environments reliant on automated pipelines and trusted package sources.

The incident underscores the increasing risks of credential theft through Python package hijacking, which can grant attackers access to sensitive cloud resources and code repositories. Organizations using Microsoft’s Agent Framework or integrated CI/CD build systems need to assess potential exposure and mitigate risks to prevent operational and security breaches.

What to watch next

Security teams and developers should immediately verify which versions of the Agent Framework are installed in their environments and reinstall the safe 1.26.0 version if either compromised variant was deployed. Rotating all possibly exposed secrets and tokens linked to affected systems is essential to reduce ongoing risk from credential theft.

Microsoft’s response and remediation measures will be closely monitored, especially regarding safeguarding internal release pipeline certificates and strengthening publisher account security on package repositories. The broader developer community will watch for long-term changes in software supply chain defenses to counteract similar incidents. Additionally, ongoing investigation may reveal how the attacker accessed Microsoft's pipeline credentials and whether related attacks exist.

Source assisted: This briefing began from a discovered source item from SiliconANGLE. Open the original source.
How SignalDesk reports: feeds and outside sources are used for discovery. Public briefings are edited to add context, buyer relevance and attribution before they are published. Read the standards

Related briefings