Miasma Blight Reaches Microsoft: 73 Repos Disabled in 105 Seconds

What it is

A follow-up on the June 5, 2026 GitHub takedown of 73 Microsoft repos, adding the detail the summary lacks: the specific PyPI compromise, the mutable-tag failure mode that broke pipelines, and Microsoft's own recommended workarounds during the outage.

How it works

The recurring root is the durabletask PyPI package (Microsoft's official Azure Durable Task SDK, ~417,000 downloads/month). On May 19, three malicious versions — 1.4.1, 1.4.2, 1.4.3 — were pushed to PyPI inside a 35-minute window with no matching tags, releases, or CI runs in the GitHub repo, indicating direct publishing via stolen GitHub Actions secrets rather than the normal build path. Those were yanked within hours. A month later the same ecosystem became the hub of the takedown, which the author reads as the May credentials never having been fully revoked.

The CI blast radius comes from mutable tags: Azure/functions-action@v1 floats, so when GitHub disabled the source repo the tag simply stopped resolving and every referencing workflow broke. A pinned commit SHA would have kept resolving (or failed predictably) rather than evaporating.

Preconditions / Affected

• Any pipeline referencing Azure/functions-action@v1 or functions-container-action — these are actions that run inside other people's workflows, so they can't be pinned around by consumers of a library.
• Anyone who installed durabletask versions 1.4.1, 1.4.2, or 1.4.3 during the May 19 window.

What to do

• Check for the malicious durabletask versions 1.4.1, 1.4.2, 1.4.3 in any environment that pulled from PyPI around May 19.
• Pin GitHub Actions to a full commit SHA rather than a floating tag like @v1, so a disabled source fails loudly instead of vanishing.
• While functions-action is down, Microsoft's staff recommended alternative deployment methods: Azure CLI, Azure DevOps Pipelines, VS Code deployment, Zip Deploy, or Azure Pipelines instead of GitHub Actions.

Caveats

• The re-compromise link is the author's inference ("plausibly never fully lost them"), not confirmed root cause — GitHub's banner cites only a terms-of-service violation.
• Microsoft's public messaging was contradictory: a staffer first cited "GitHub policy violations (malware, phishing…)," then revised twelve minutes later to "an internal management issue" — so the official cause is unsettled.
• The May attribution to threat actor TeamPCP comes from Wiz, Endor Labs, and StepSecurity (per the summary); this post asserts continuity but does not independently establish the June mechanism.