A forensic analysis of the June 5, 2026 Miasma worm attack on Microsoft's Azure GitHub organizations. A compromised contributor account pushed a malicious commit to Azure/durabletask containing five configuration files targeting four developer tools: Claude Code, Gemini CLI, Cursor, and VS Code. Each file triggers automatic execution of a 4.6 MB obfuscated credential-harvesting JavaScript payload when a developer opens the repository. GitHub disabled 73 Microsoft repositories in a 105-second automated sweep, including Azure/functions-action, breaking CI/CD pipelines for developers worldwide. The attack marks a significant evolution from package registry poisoning to editor-level hijacking, bypassing traditional supply chain defenses focused on package install hooks. The incident is linked to the TeamPCP threat group behind the broader Miasma worm campaign. Remediation steps include rotating all credentials, checking for persistence mechanisms, auditing repositories for suspicious config files, and pinning GitHub Actions to commit SHAs.
Table of contents
BackgroundThe June 5 Incident: What Happened73 Repositories Disabled in 105 SecondsGlobal CI/CD Breakage: Azure/functions-action DownThe Attack Evolution: May 19 to June 5Connection to the Broader CampaignTimelineWhat You Should Do4.5K Impressions1 Comment