{"schema_version":"0.10.0","id":"LR-2026-0596","record_version":1,"title":"Miasma worm supply chain attack targets Microsoft Azure repositories and AI coding tools (June 5, 2026)","verification":{"human_verified":false,"method":"automated_gate","auto_verified":true,"score":59.3,"score_breakdown":{"source_authority":12.1,"independent_corroboration":20.0,"implicated_party_confirmed":0.0,"citation_integrity":14.0,"specificity":3.0,"completeness":2.24,"unhedged_language":5.0},"checks":{"schema_valid":true,"every_field_cited":true,"quotes_verbatim":true,"source_fetched":true,"distinct_incident":true,"dates_plausible":true,"sources_agree":true,"source_describes_incident":true,"severe_backed_by_source":true,"record_integrity":true,"eligible":true,"about_this_case":true},"gate_version":"gate-2026-10-18.7","cross_check_model":null,"cross_check_agreement":null,"duplicate_of":null,"verified_by":null,"verified_at":"2026-11-01","extraction_run_id":null,"evidence_level":{"level":"confirmed","reason":"StepSecurity research","original_document":{"url":"https://www.stepsecurity.io/blog/miasma-worm-hits-microsoft-again-azure-functions-action-and-72-other-repositories-disabled-after-supply-chain-attack-targeting-ai-coding-agents","organisation":"StepSecurity","role":"researcher"},"reports_total":3,"reports_independent":2,"reports_derivative":0,"developing":false,"disputed":false,"rules_version":"evidence-2026-10-29.1","computed_at":"2026-11-01","history":[{"date":"2026-11-01","from_level":null,"to_level":"confirmed","reason":"StepSecurity research"}]},"sources_hash":"0dd1e891585409ee15d6097747417a817475722563240035d8e4593e3dfaa87d"},"system":{"model_name":null,"model_version":null,"developer":"unknown","harness":null,"tools_granted":[],"permissions_scope":null,"autonomy_level":"unknown","guardrails_present":[],"deployment_context":"unknown","tier":null,"lifecycle_stage":null,"integration_type":null,"intended_use":null,"safeguard_state":null,"production_intended":null},"event":{"date_occurred":"2026-06-05","date_disclosed":"2026-06-05","incident_class":"security_compromise","failure_class":null,"agent_involved":null,"secondary_failure_classes":[],"trigger":"unknown","duration":null,"detection_method":"unknown","summary":"A malicious commit was pushed to Microsoft's Azure/durabletask GitHub repository on June 5, 2026, using a previously compromised contributor account. The commit added configuration and payload files designed to run a credential-harvesting script when a developer opened the repository in an AI coding tool or IDE, including Claude Code, Gemini CLI, Cursor and VS Code. GitHub's automated abuse detection then disabled 73 repositories across four Microsoft GitHub organizations within a 105-second window. The disablement broke Azure/functions-action, the official GitHub Action for deploying Azure Functions, and developers reported broken CI/CD pipelines. Microsoft first described the outage as a GitHub policy violation and later as an internal management issue under investigation.","tags":[],"date_detected":null,"near_miss":null,"root_cause":null,"root_cause_detail":null,"failure_class_detail":null,"responsible_party":null,"adversarial_actor":null,"input_provenance":null,"time_to_contain":null,"operations_paused":null,"remediation":null,"precursor_events":null},"impact":{"direct_loss_usd":null,"remediation_hours":null,"records_exposed":null,"third_parties_affected_count":null,"severity":"major","severity_because":"Test: many third parties with a stated count of two or more. Fact: 20+ developers reported broken CI/CD pipelines.","harm_class":[],"affected_description":null,"protected_class_involved":null,"data_categories_exposed":[],"loss_range_usd":null,"reversibility":null,"downstream_exposure_count":null},"evidence":{"sources":[{"url":"https://www.stepsecurity.io/blog/miasma-worm-hits-microsoft-again-azure-functions-action-and-72-other-repositories-disabled-after-supply-chain-attack-targeting-ai-coding-agents","publisher":"Step Security","date":"2026-06-05","type":"press","title":"Miasma Worm Hits Microsoft Again: Azure Functions Action and 72 Other Repositories Disabled After Supply Chain Attack Targeting AI Coding Agents - Step Security","archived_url":null,"attachment":"first_report","independence":"independent"},{"url":"https://www.morphisec.com/blog/its-in-your-ai-assistant-now-shai-hulud-wave-3-and-the-miasma-worm-targeting-npm/","publisher":"Morphisec","date":"2026-06-08","type":"press","title":"It’s In Your AI Assistant Now: Shai-Hulud Wave 3 and the Miasma Worm Targeting npm - Morphisec","archived_url":null},{"url":"https://thehackernews.com/2026/06/miasma-malware-targets-npm-packages-and.html","publisher":"The Hacker News","date":"2026-06-26","type":"press","title":"Miasma Malware Targets npm Packages and GitHub Actions in Supply Chain Attack - The Hacker News","archived_url":null,"independence":"independent"}],"per_field_confidence":{"event.incident_class":"C","event.date_occurred":"C","impact.severity":"D","impact.severity_because":"D","event.summary":"C","system.autonomy_level":"D","system.deployment_context":"D","event.trigger":"D","event.detection_method":"D","context.country":"D","system.developer":"D","event.date_disclosed":"D","context.denominator_available":"D"},"field_citations":{"event.incident_class":[{"source_index":0,"quote":"On June 5, 2026, the Miasma worm campaign reached Microsoft's Azure GitHub organizations."}],"event.date_occurred":[{"source_index":0,"quote":"On June 5, 2026, the Miasma worm campaign reached Microsoft's Azure GitHub organizations."}],"impact.severity":[{"source_index":0,"quote":"Within hours, a Microsoft Learn Q&A thread opened with 20+ developers reporting broken CI/CD pipelines."}],"impact.severity_because":[{"source_index":0,"quote":"Within hours, a Microsoft Learn Q&A thread opened with 20+ developers reporting broken CI/CD pipelines."}],"event.summary":[{"source_index":0,"quote":"A commit (5f456b8) was pushed to the Azure/durabletask repository using a compromised contributor account."},{"source_index":0,"quote":"The attack planted configuration files that execute a credential-harvesting payload when a developer opens the repository in Claude Code, Gemini CLI, Cursor, or VS Code."},{"source_index":0,"quote":"Hours after the malicious commit, GitHub's automated abuse detection disabled 73 repositories across four Microsoft GitHub organizations."},{"source_index":0,"quote":"The block timestamps span from 16:00:50 to 16:02:35 UTC on June 5, a 105-second window with two distinct waves separated by a 56-second gap."},{"source_index":0,"quote":"Every workflow on GitHub referencing Azure/functions-action@v1 stopped resolving immediately."},{"source_index":0,"quote":"Within hours, a Microsoft Learn Q&A thread opened with 20+ developers reporting broken CI/CD pipelines."}]},"notes_on_gaps":"Record covers only the June 5, 2026 Azure/durabletask commit and GitHub takedown described in source 0. Source 1 is general Miasma commentary (its June 3 and May 19 references are not used as incident facts). Source 2 describes a separate June 24-26 LeoPlatform/RStreams/Verana/@immobiliarelabs wave and is excluded from this record. No AI model, developer, harness or deployment fields are stated; the AI coding tools are the victim's editors, not an autonomous agent, so no failure_class or agent_involved value was written. The sources do not state date_disclosed or date_detected, the trigger, root_cause category, responsible_party, adversarial_actor, reversibility, direct loss, records, or durations; these were left out. The 105-second span is the GitHub enforcement window, not a containment time. The source offers three possible explanations for account reuse; none is confirmed, so none is recorded as fact. The B4 'missing' outcome is my inference from the source's recommendation to add branch protection and is not directly stated. The major severity rests on the stated count of 20+ developers reporting broken pipelines. [case created by the backfill: read by claude-haiku-5-5, backfill-2026-11-01.2, 2026-11-01; not yet reviewed] [2026-11-01: evidence level set: Confirmed (StepSecurity research)]"},"context":{"industry":null,"org_size_band":null,"country":"unknown","denominator_available":false,"denominator":null,"related_incident_ids":[],"systemic_exposure":null,"shared_model_id":null,"upstream_incident_id":null,"incident_evidence":null,"regulatory":null,"coverage":null}}