explainx.ai350K+ learn from us
TrendingAI News TodayPathwaysSkills
Pricing
explainx.ai

Upskill in AI — 16 free pathways, live workshops & bootcamps, and 50+ courses from practitioners. Plus the skills, tools, and MCP servers to practice on.

follow us

follow on google

Add explainx.ai as a preferred source

corporate training

support@explainx.ai

get started

Find your pathTake Free Evaluation

community

Join the community

learn

mind: share how you thinkpathways — start freeworkshopsbootcampscoursescompare Explainxcertificationsmock testsexplainx universitycorporate traininglearn skills & mcp

discover

skillsmcp serversexplainx mcpestacktoolsmdx readeragentsllmsdesignsdictionarypeopleagi trackerfelony benchranks

company

aboutvisionmissionteaminstructorsteach on explainxpartnershipscommunityhackathonscareers

content

daily AI newsstate of AI — live resultsblogreleasespromptsgeneratorsresource libraryfor LLMsexplainx.ai kids

solutions

all solutionsdeveloper upskillingmarketing upskillingproduct manager upskillingleadership upskilling

newsletter · weekly

Get AI news, tools, and insights in your inbox.

supportcontactprivacytermsdata rightshow we create contentsubmission guidelines

© 2026 AISOLO Technologies Pvt Ltd

explainx.ai

On this page

  • Timeline: what happened on November 17, 2026
  • Mechanism: why .pth hooks are nasty
  • What Microsoft’s clean release actually ships
  • Incident response checklist
  • How to protect agent pipelines going forward
  • What Socket and Upwind saw in the payload
  • Why this hit agent teams especially hard
  • PyPI mirrors and delayed registries
  • Developer FAQ: pip, poetry, and containers
  • Longer-term controls for agent pipelines
  • Pair with the week’s other agent attacks
  • Microsoft Agent Framework in your stack
  • Legal and communications notes
  • Hunting queries (conceptual)
  • What this is not
  • Related reading
← Back to blog

explainx / blog

Microsoft agent-framework PyPI 1.26.1 Hijack: Azure and GitHub Token Stealer

Security, Microsoft, PyPI, Supply Chain, Agents

Part of AI Security

Malicious agent-framework 1.26.1 and 1.26.2 wheels on PyPI used .pth startup hooks to steal Azure, GitHub OIDC, and CI secrets. Pin 1.26.0 and rotate credentials.

Nov 18, 2026·8 min read·Yash Thakker
add explainx.ai
go deep
Microsoft agent-framework PyPI 1.26.1 Hijack: Azure and GitHub Token Stealer

Malicious agent-framework wheels hit PyPI on November 17, 2026 with code that steals Azure, GitHub Actions, and CI/CD credentials via Python .pth startup hooks. Socket’s analysis and Wiz’s incident write-up are the technical sources; Microsoft’s last verified release is python-1.26.0 on GitHub from November 13, 2026.

Daily briefFrom Yash · 350K+ students taught

Catch up on AI

One AI story explained in plain English, plus one thing to try. Every day, free. Unsubscribe anytime.

Timeline: what happened on November 17, 2026

table · 2 cols
Time (UTC, per vendors)Event
~20:351.26.1 wheel published to PyPI
~20:54Upwind reports issue on Microsoft’s GitHub tracker
~21:081.26.2 follows with modified payload
~21:30PyPI quarantines both versions
LaterMicrosoft repo maintainer confirms pull; investigation ongoing

Unlike a typical dependency confusion typo, agent-framework is the real Microsoft package name with substantial weekly download volume. That makes this a publisher-account or release-pipeline compromise question, not an impersonation package with a misspelled name.

agent-framework PyPI compromise — supply chain link audit illustrationagent-framework PyPI compromise — supply chain link audit illustration

Mechanism: why .pth hooks are nasty

Wiz explains the infection path:

  1. Malicious wheel drops agent_framework_meta.pth (1.26.1) or af_runtime_diag.pth (1.26.2) into site-packages.
  2. Python’s startup loader executes every .pth line before user code runs.
  3. Hook imports _telemetry disguised as diagnostic telemetry (af-runtime-diagnostics/1 user-agent string).
  4. Collector forks a detached process (or daemon thread) and scans:
    • Environment keys matching TOKEN, SECRET, AZURE, GITHUB, OPENAI, HF_, and similar substrings.
    • Up to 60 credential files (Azure CLI JSON, .npmrc, .docker/config.json, .env, Azure DevOps agent credentials).
    • Other processes’ /proc/*/environ entries (hundreds of PIDs).
  5. Requests Azure managed identity and Azure DevOps OIDC tokens; 1.26.2 adds GitHub Actions OIDC.
  6. zlib + base64 payload POSTed once to webhook[.]site/d381fd80-ec62-42ad-8f5c-d1b15103c9bb.

You do not need import agent_framework for step 2–6 to run—any python CLI invocation in the venv triggers collection.

What Microsoft’s clean release actually ships

The legitimate python-1.26.0 release notes mention routine dependency range bumps (for example Anthropic 2.x support). There is no python-1.26.1 tag in that repository at the time of writing.

Analysts note 1.26.1 was wheel-only and still depended on agent-framework-core==1.26.0, suggesting an upload outside the project’s paired wheel+sdist workflow.

Builders using Microsoft Foundry agent previews or MAI Code harness news should audit any Python worker that installed agent-framework during the exposure window.

Incident response checklist

1. Find exposure

  • Grep lockfiles, Dockerfiles, devcontainer specs, and CI logs for agent-framework==1.26.1 or 1.26.2.
  • Search images built November 17, 2026 UTC evening.

2. Confirm execution artifacts

On disk inside affected virtualenvs:

  • site-packages/agent_framework_meta.pth
  • site-packages/agent_framework_meta/_telemetry.py (1.26.1)
  • site-packages/af_runtime_diag.pth (1.26.2)

3. Network forensics

Proxy or DNS logs for the webhook.site UUID above. Vendors note HTTP 200 implies acceptance; 410/429 may mean the sink rejected data—but do not treat absence of logs as safety.

4. Rotate secrets

Prioritize:

  • Azure service principals and managed identities on the host.
  • GitHub Actions OIDC and ACTIONS_ID_TOKEN scopes (1.26.2).
  • Azure DevOps SYSTEM_ACCESSTOKEN pipelines.
  • Hugging Face, OpenAI, and npm tokens in developer homedirs named in Socket’s IOC list.

5. Rebuild environments

  • Delete venvs; reinstall from agent-framework==1.26.0 with hash pinning.
  • Ban floating >= pins on agent-framework until Microsoft publishes hardening guidance.

CI and container rebuild paths after a poisoned Python wheelCI and container rebuild paths after a poisoned Python wheel

How to protect agent pipelines going forward

Supply-chain attacks on agent runtimes are now recurring:

  • Compare with Postman shipping Codex plugins by default and GTIG IDE backdoors.

Minimum practices:

table · 2 cols
ControlRationale
Hash-pinned PyPIBlocks retroactive malicious wheels
Internal mirror with delayLets Socket/Chainguard block lists propagate
Ephemeral CI runnersShrinks secret residence time
OIDC audience restrictionLimits token utility if stolen

Teams running autonomous coding agents should read AgentBeam’s incident companion for detection patterns aimed at agent hosts.

What Socket and Upwind saw in the payload

Socket’s reverse engineering is the most granular public write-up. Highlights that matter for your runbook:

  • Disguised telemetry — module names like _telemetry and user-agent af-runtime-diagnostics/1 mimic legitimate SDK diagnostics.
  • Substring env harvesting — not a fixed allowlist; any variable containing TOKEN, SECRET, KEY, AZURE, GITHUB, OPENAI, HF_, FOUNDRY, or ARM_ may be copied.
  • Cross-process reads — up to 300 /proc/*/environ scans hunting SYSTEM_ACCESSTOKEN, IDENTITY_HEADER, and GitHub ACTIONS_ID_TOKEN patterns in 1.26.2.
  • Azure file globs — ~/.azure/**/*.json, /home/*/.azure, and /root/.azure JSON stores.
  • Single-shot exfil — one POST, no retry; failures are swallowed, so defenders cannot assume “failed upload means safe.”

Cybersixt’s timeline adds repository color: a Microsoft maintainer commented on GitHub within hours that compromised versions were removed and investigation continues—use that issue thread for official status, not rumor forums.

Why this hit agent teams especially hard

agent-framework is not an obscure typo-squat. It is the Python entry point for Microsoft’s Agent Framework used in samples that pair with Azure AI Foundry, Semantic Kernel-style orchestration, and multi-agent demos.

If your platform team ran pip install -U agent-framework on November 17 evening UTC to chase features, you may have pulled a wheel never tagged python-1.26.1 on GitHub. That mismatch is your smoking gun in SBOM audits:

table · 3 cols
SignalBenign 1.26.0Malicious 1.26.1 / 1.26.2
Git tag python-1.26.xPresent for 1.26.0Absent for 1.26.1
PyPI artifact shapeWheel and sdist with aligned coreWheel-only per Wiz
Startup side effectNo rogue .pth telemetry.pth executes every Python launch

Compare with AgentCorruption on Bedrock AgentCore—different cloud, same lesson: agent hosts are secret vaults.

PyPI mirrors and delayed registries

If your org uses delayed PyPI mirrors or private caches, ensure block lists include 1.26.1 and 1.26.2 wheel hashes even after PyPI removal. Socket and Wiz published IOC hashes the same evening; mirrors that do not ingest third-party advisories may still serve quarantined builds until you pin explicitly.

Developer FAQ: pip, poetry, and containers

I use Poetry/pip-tools—am I safe? Only if lockfiles never resolved during the exposure window. Re-lock against 1.26.0 and diff hashes.

I only build containers on Mondays. Check intermediate layers baked after 2026-11-17 20:35 UTC for the bad version strings.

Does uninstalling fix it? Remove the package and delete leftover .pth files; rebuild the venv. Assume secrets already left the host if Python ran once.

Should I ban webhook.site outright? Many legitimate testers use it; for production agents, egress allow lists are safer than domain blocks alone.

Longer-term controls for agent pipelines

  1. Two-person release on PyPI publish tokens for any package that touches cloud SDKs.
  2. Sigstore or company signing attestation on wheels before internal mirrors ingest.
  3. OIDC federation scopes narrowed so a stolen Actions token cannot reach production subscriptions.
  4. Runtime monitoring on hosts that run unattended python -m workers so unexpected child Python processes and egress to paste-bin domains surface quickly.

Pair with the week’s other agent attacks

This compromise landed the same week as:

  • FBI ARTEX FLASH verification (offensive agent framework abuse).
  • Google GTIG SomberMeme IDE backdoor (developer workstation social engineering).
  • Spillway prompt-injection guard launches (defensive tooling).

Treat them as one November cluster: attackers target where agents load code—PyPI, IDE settings, and autonomous pentest consoles.

Microsoft Agent Framework in your stack

If you are standardizing on Microsoft’s agent abstractions, map where agent-framework appears:

table · 3 cols
LayerTypical install pathRisk if poisoned
Local dev venvpip install agent-framework[all]Developer laptop secrets
CI test runnerCached wheels between jobsGITHUB_TOKEN, Azure federated creds
AKS / App Service workerContainer pip install during buildManaged identity tokens
Foundry sample notebooksTutorial requirements.txtSubscription-scoped keys

None of those layers should use floating latest on a package that can invoke cloud control planes. Pin ==1.26.0 until Microsoft ships a signed 1.26.3+ with an explicit compromise postmortem.

Legal and communications notes

Security teams often debate whether to email customers about a transitive dependency. For agent-framework, assume direct intent: attackers chose a high-trust vendor namespace. If you shipped any service whose Dockerfile upgraded Python deps on November 17 UTC evening, issue an internal severity-1 rotation even without external breach evidence.

Vendors such as Ox Security and Wiz published parallel analyses within hours—use them as secondary citations in tickets, but Socket + GitHub release tag remain the technical anchors for engineering.

Hunting queries (conceptual)

Adapt to your SIEM; these are patterns, not vendor signatures:

  • Filesystem: new files matching agent_framework_meta.pth or af_runtime_diag.pth under site-packages.
  • Process: short-lived child python after parent shell invoked in CI, with _AF_TEL=1 in environment snapshots.
  • Network: HTTPS POST bodies with base64+zlib blobs to webhook.site subdomains from build agents.
  • Identity: sudden Azure AD token minting for multiple resources from one runner IP within seconds.

Pair hunting with NIST-NSA-CISA agent control guidance if your program is still immature.

Rotation priority: start with cloud control-plane credentials that can create new users or export storage—those keys monetize fastest for attackers. Developer OpenAI and Hugging Face tokens matter next for LLM abuse, but they rarely grant domain takeover by themselves. Document every rotation ticket with the exact wheel hash you removed so auditors can close the incident.

What this is not

  • Not a vulnerability in Microsoft’s agent source code on GitHub 1.26.0—IOC focuses on PyPI contents.
  • Not proof that GitHub Copilot or Foundry clouds were breached; impact is environments that installed the bad wheel.
  • Not related to FBI ARTEX offensive framework abuse except in the broad sense of November agent threat volume.

Related reading

  • Microsoft Copilot harness in Foundry
  • MCP tool-provider misbinding risks
  • AgentCorruption Bedrock hijack pattern
  • November 2026 cyberattacks tracker
  • External sandboxes for coding agents
  • FBI ARTEX FLASH on autonomous intrusions
Spotted something out of date? Let us know.
Daily briefFrom Yash · 350K+ students taught

Catch up on AI

One AI story explained in plain English, plus one thing to try. Every day, free. Unsubscribe anytime.

  • ✓ Free
  • ✓ One email a day, no spam
  • ✓ Unsubscribe anytime
Yash Thakker

Written by

Yash Thakker

Yash is an AI expert with over 300K learners. Join his workshops →

View Yash Thakker in People in AI →

Related posts

Oct 21, 2026

LiteLLM 1.107.0 on PyPI Is Malicious: What the Credential Stealer Takes and How to Clean Up

On October 21, 2026, researchers found that all seven wheels of LiteLLM 1.107.0 on PyPI, and the official Docker image, shipped a credential stealer and an hourly remote-code loader that run whenever Python starts. This is the second LiteLLM hijack of the year. Here is what was found, what is still unknown, and the order to clean up in.

Nov 17, 2026

Sapper v2: Open Autonomous Pentest Legion on the Nüwa Agent Framework

GitHub trending sapper-v2 packages an evolvable pentest legion: a commander that dispatches scouts and soldiers in tmux, a scripted watchdog for crashes, and competition results showing 80.18 points on 1 billion tokens.

Nov 15, 2026

Pax Silica Joint AI Supply Chain List: What the San Francisco Declaration Adds

Financial Times reporting summarized on November 15, 2026 says Pax Silica partners including Japan, the UK, India, and South Korea will jointly identify AI technologies and supply chains that need protection from theft and unauthorized transfer. The step layers on the State Department San Francisco Declaration text teams can already read at state.gov.