Critical by impact (our framing)Supply-chain malwareNo CVE assignedPyPI: Release quarantined

Have you checked every environment that installs Microsoft's agent-framework package?

On 17 November 2026 two malicious versions of Microsoft's official agent-framework package were published to the Python Package Index (PyPI): 1.26.1 at 20:35:20 GMT and 1.26.2 at 21:08:39 GMT. PyPI quarantined 1.26.1 at 21:06:16 GMT and 1.26.2 at 21:16:44 GMT the same day. Each of those releases was a single wheel. Both install a Python .pth startup hook that steals credentials and cloud identity tokens, then sends them by HTTPS POST to a webhook[.]site address. PyPI still shows both release pages, labelled quarantined, and lists 1.26.0 as the current version. No CVE had been assigned when we checked. Pin agent-framework==1.26.0 or earlier, rebuild any affected environment from a clean system, and rotate the credentials that environment could reach.

Critical by impact (our framing). These were live malicious releases

There is no vendor CVSS score and no CVE record. We use Critical by impact as our framing because these were live malicious versions of an official Microsoft package, they steal credentials and cloud identity tokens, and they run whenever Python starts, including during pip, even if nothing imports the package. Treat any environment that installed 1.26.1 or 1.26.2 as compromised. The GitHub Advisory Database entry GHSA-764m-3ppc-5m73 classifies the incident as critical malware and does not publish a CVSS vector. That entry is not a Microsoft advisory. We do not link proof-of-concept or exploit code.

At a Glance

Based on the PyPI project page and release history for agent-framework, The Hacker News (18 November 2026), the GitHub Advisory Database entry GHSA-764m-3ppc-5m73, and OSV MAL-2026-20101, checked at 18 November 2026, 18:09 GMT. Last updated 18 November 2026, 18:09 GMT.

agent-framework is the meta-package for Microsoft Agent Framework, an official Microsoft project for building AI agents in Python. When we checked, PyPI and pypistats reported about 196,000 downloads of the package in the past month (195,912). PyPI shows both malicious releases were uploaded without Trusted Publishing, via the user agent RestSharp/106.13.0.0. That is a PyPI fact only. How the publishers obtained upload access is still unknown, and we do not speculate.

Once either malicious version is installed, it drops a .pth file into site-packages. Python runs import lines in .pth files at every interpreter start, so the stealer runs whenever Python starts in that environment, including during pip, even if nothing imports Agent Framework. The hook files are agent_framework_meta.pth in 1.26.1 and af_runtime_diag.pth in 1.26.2.

Security researchers, as reported by The Hacker News and recorded in the GitHub Advisory Database and OSV entries, say the stealer collects credential-like environment variables and credential files, including Azure CLI files under ~/.azure, .npmrc, .netrc, .git-credentials, .docker/config.json, Hugging Face tokens, Azure DevOps agent credential files, and .env files. The Hacker News also reports collection of pip.conf and JSON files. Besides reading what is already on disk, the code requests new tokens: Azure DevOps OIDC tokens (using SYSTEM_ACCESSTOKEN), and Azure managed-identity tokens via IDENTITY_ENDPOINT or the instance metadata address 169.254.169[.]254. The Hacker News also names MSI_ENDPOINT as another managed-identity endpoint; that name is not in the OSV or GitHub Advisory Database records, so we treat it like pip.conf and generic JSON files and attribute it to The Hacker News. Version 1.26.2 also requests GitHub Actions OIDC tokens. Collected data is sent by HTTPS POST to webhook[.]site/d381fd80-ec62-42ad-8f5c-d1b15103c9bb. Because the malware can request fresh tokens, rotating only the secrets already stored on disk is not enough.

Your next 24 hours

  1. Find every install of 1.26.1 or 1.26.2

    Our advice: search developer workstations, build agents, containers, virtual environments and lockfiles for agent-framework==1.26.1 or 1.26.2, and for the hook files agent_framework_meta.pth and af_runtime_diag.pth. Pay particular attention to installs between 20:35:20 GMT and 21:16:44 GMT on 17 November 2026 (PyPI's upload and quarantine times), and to any later install from a cached or mirrored copy. The Hacker News suggested a check window of 20:35 to roughly 21:20 GMT; that is their exposure window, not the upload times.

  2. Pin to 1.26.0 and rebuild clean

    Vendor state (PyPI): 1.26.1 and 1.26.2 are quarantined, and 1.26.0 is the current listed release. Our advice: pin agent-framework==1.26.0 or earlier, preferably with hashes, and rebuild affected environments from a known-clean base. Uninstalling the package in a already-compromised environment is not enough.

  3. Hunt the exfiltration address and rotate from a clean system

    Our advice: search proxy and DNS logs for webhook[.]site and the path d381fd80-ec62-42ad-8f5c-d1b15103c9bb. If you find 1.26.1, 1.26.2 or either hook file, isolate the host or runner. From a clean system, rotate every credential that environment could reach, and review sign-in and activity logs for the managed identities and federated credentials involved.

Proactive: Find, pin and harden

Vendor advice

  • Microsoft had not published a security advisory for this incident, and the microsoft/agent-framework repository listed no matching security advisory, when we checked at 18 November 2026, 18:09 GMT. Recheck those sources.
  • PyPI, when we checked, labelled 1.26.1 and 1.26.2 as "Release quarantined" and said they cannot be installed or modified until a security review is complete, recommending 1.26.0 instead. The release pages remain visible. The versions are omitted from the installable simple index, and the JSON API returns 404 for both. Each quarantined release was a single wheel. The current listed version is 1.26.0. We did not find a later official patched release.

Our advice

  • Inventory every place you or your clients install agent-framework, including developer laptops, CI runners, containers and internal mirrors.
  • Pin agent-framework==1.26.0 or earlier, with hashes where you can. Use a cooldown or an internal mirror before new PyPI releases are allowed into build pipelines.
  • Limit what CI runners and managed identities can reach, and block outbound access to webhook[.]site from build and production networks where your policy allows it.
  • Do not wait for a new Microsoft patched release of 1.26.1 or 1.26.2. Those versions are the malicious uploads. 1.26.0 is the last clean release listed on PyPI.

Free Detection Pack

Built by the CybaVerse threat hunt team for businesses, internal IT teams and MSPs. Check pip installs, lockfiles and site-packages offline, and hunt for the payload files, wheel hashes and the webhook[.]site indicator. Everything is read-only. Pack version 1.0.0 is the download on this page. The KQL and Sigma have not been run against live data.

Verdicts

  • NOT FOUNDNothing malicious found, and every agent-framework reference has an exact clean version (exit 0).
  • COMPROMISEDA malicious version, payload file, payload import or malicious wheel hash was found (exit 2).
  • REVIEWAn unpinned reference, a file too large or with lines too long to scan, or an unreadable folder or file, and nothing malicious found (exit 3). Check what an unpinned install resolved to between 20:35 and 21:17 GMT on 17 November 2026 (the checker's PyPI window).
  • USAGE OR READ ERRORThe checker was invoked incorrectly, or a path could not be read (exit 5).

Exit codes

CodeMeaning
0NOT FOUND
1Not used
2COMPROMISED
3REVIEW
5USAGE OR READ ERROR

The full pack zip contains 73 files (pack version 1.0.0). The planned hubfs folder is microsoft-agent-framework-pypi-pack-v1.

Know the limits

  • Both checkers are read-only and offline. They open no sockets, write no files, never import or run Python, and contain no exploit payloads. They never print file content, so secrets in lockfiles or .pth files are not shown.
  • Every hunt and Sigma rule in this pack is OUR PATTERN. A hunt hit is a lead to investigate. It does not prove that the stealer ran.
  • The hunts start at 20:00 GMT on 17 November 2026. That start time is our margin before the first upload.
  • None of the KQL or Sigma has been run against live data.

What is in the pack

FileWhat it does
scripts/check-agent-framework.shOffline, read-only checker for Linux and macOS (bash)
scripts/Check-AgentFramework.ps1The same checker in PowerShell 7
KQL (9 hunts)Microsoft Sentinel and Defender hunts Q1 to Q9, all OUR PATTERN, from 20:00 GMT on 17 November 2026
Sigma (9 rules)All OUR PATTERN, plus Kusto conversions. Q7 to Q9 are KQL only
tests/Fixtures, bash and Pester tests and a sandboxed no-network run
README.mdVerified facts, indicators, checker usage, limits and sources

Reactive: How to hunt

Our advice, based on The Hacker News, the GitHub Advisory Database and OSV. These are hunting indicators, not a method for reproducing the malware. We do not host or link the malicious wheels.

  • Search lockfiles, pip logs, container images and virtual environments for agent-framework 1.26.1 or 1.26.2.
  • Search site-packages for agent_framework_meta.pth and agent_framework_meta/_telemetry.py (1.26.1), or af_runtime_diag.pth and af_runtime_diag.py (1.26.2). Any Python process started in an environment that still has those files will have run the stealer.
  • Search proxy, DNS and web logs for webhook[.]site and the path d381fd80-ec62-42ad-8f5c-d1b15103c9bb. OSV also records the HTTP user-agent strings af-runtime-diagnostics/1 (1.26.1) and runtime-diagnostics/1 (1.26.2).
  • OSV lists these SHA-256 hashes for the quarantined wheels: 1.26.1 d27fa34414e6201d5e03e559ef634f020057554d7b3f4898dd5d7cd3e989e110; 1.26.2 3d20a8bc91351a9a16b6db243b848ceca0206b7a8623b02d2af553a9c9f7e0a9.
  • If you find any of the above, isolate the host or runner, then rebuild it from a known-clean base and pin to 1.26.0 or earlier. From a clean system, rotate Azure credentials, Azure DevOps tokens, GitHub tokens, npm and pip credentials, Docker credentials, Hugging Face tokens, git credentials and any secrets in .env files that the environment could reach. Then review Microsoft Entra ID sign-in and activity logs for the managed identities and federated credentials involved, and audit Azure DevOps pipelines and GitHub Actions workflows that deploy to Azure. Rotating only stored secrets does not cover tokens the malware may have requested at the time.

Questions people ask

What happened to the agent-framework package on PyPI?

Two malicious versions of Microsoft's official agent-framework package, 1.26.1 and 1.26.2, were published to PyPI on 17 November 2026 at 20:35:20 GMT and 21:08:39 GMT. PyPI quarantined them at 21:06:16 GMT and 21:16:44 GMT. Each was a single wheel. Both install a .pth startup hook that steals credentials and cloud identity tokens and sends them to a webhook[.]site address. PyPI still shows both release pages, labelled quarantined, and lists 1.26.0 as the current version.

Which versions are safe, and is there a patched release?

1.26.0 and earlier, as listed on PyPI, are the clean releases. 1.26.1 and 1.26.2 are the malicious uploads, not official patches. When we checked, PyPI had not published a later version than 1.26.0. Pin to 1.26.0 or earlier and rebuild affected environments from a clean base.

Has Microsoft published an advisory, and is there a CVE?

No Microsoft security advisory, and no security advisory on the microsoft/agent-framework repository, was listed when we checked at 18 November 2026, 18:09 GMT. No CVE had been assigned. The GitHub Advisory Database entry GHSA-764m-3ppc-5m73 and OSV MAL-2026-20101 describe the malicious releases. Recheck Microsoft and PyPI.

Does the stealer run even if my code never imports agent-framework?

Yes. The malicious wheels add a .pth file to site-packages. Python runs those hooks at every interpreter start, so the stealer runs whenever Python starts in that environment, including during pip, even if nothing imports Agent Framework.

What should we rotate if we installed 1.26.1 or 1.26.2?

Treat the environment as compromised. From a clean system, rotate Azure credentials, Azure DevOps tokens, GitHub tokens, npm and pip credentials, Docker credentials, Hugging Face tokens, git credentials and secrets in .env files that the environment could reach. Also review sign-in and activity logs for managed identities and federated credentials, because the malware can request fresh tokens, not only read secrets already on disk.

Is this in CISA's Known Exploited Vulnerabilities catalogue?

No CVE had been assigned when we checked, so this incident does not appear as a KEV entry. That is not a statement that the malicious packages were unused. They were live releases on PyPI. Treat any environment that installed 1.26.1 or 1.26.2 as compromised.

Sources and how to get help

If you need help reviewing affected environments or rotating credentials, talk to CybaVerse.