العربية
🚨 BreakingSonicWall Gen 6 Firewalls Reach End of Security Patches

Microsoft Agent Framework PyPI Package Hijacked to Steal Cloud Credentials

فريق السايبر العربياقرأ بالعربية

Malicious agent-framework 1.26.1 and 1.26.2 releases on PyPI ran a stealer on every Python start, grabbing Azure and GitHub Actions tokens. 1.26.0 is safe.

Source image for: Attackers Compromise Microsoft's Agent Framework PyPI Package to Steal Cloud Credentials
Image: The Hacker News

⚡ Why it matters

The package sees roughly 190,000–200,000 monthly downloads, the malware runs even without importing the package, and it requests fresh Azure tokens, so rotating stored secrets alone is not enough.

agent-framework, the meta-package for Microsoft's open-source Agent Framework for building and orchestrating AI agents in Python, was hit by a supply chain attack on PyPI, according to reports from Socket, StepSecurity, Endor Labs, OX Security, Wiz and others.

What happened

Two releases, 1.26.1 and 1.26.2, appeared on PyPI on November 17, 2026, each carrying a credential stealer. PyPI quarantined both releases, but the second appeared shortly after the first was pulled, showing the attacker still had publishing access. How that access was obtained is not yet known.

How the malware works

  • Each release drops a .pth file into site-packages (agent_framework_meta.pth in 1.26.1, af_runtime_diag.pth in 1.26.2).
  • Python processes these files on every interpreter start, so the stealer runs with any Python command, including pip, even if the package is never imported.
  • It collects environment variables and credential files for Azure CLI, .npmrc, pip.conf, .netrc, .git-credentials, Docker, Hugging Face and .env files.
  • It requests Azure DevOps OIDC tokens and Azure managed-identity tokens; 1.26.2 also requests GitHub Actions OIDC tokens.
  • The data is compressed and sent to an attacker-controlled webhook.site endpoint.

Both releases kept their dependency on the legitimate agent-framework-core 1.26.0, so the framework kept working normally while the malware ran.

Recommendations

  1. Isolate any host or CI runner that installed either release and rebuild it from a clean environment using 1.26.0.
  2. Rotate every credential reachable from the affected environment, working from a clean machine.
  3. Review Azure identities and sign-in and activity logs, and audit GitHub Actions workflows that deploy to Azure.
  4. Search proxy and DNS logs for webhook.site requests on the evening of November 17, 2026 (UTC).
  5. Pin and verify package versions in CI/CD pipelines.

Sources: The Hacker News, BleepingComputer.

🔗 Sources

This article is original reporting by the Security World editorial team based on the sources listed above; direct quotes are kept short and marked with quotation marks. Corrections and feedback: info [at] securitywd.net.

Related stories