Miasma worm is a self‑replicating supply‑chain malware campaign and Mitigation

-


The Miasma worm is a self‑replicating supply‑chain malware campaign that struck 73 Microsoft GitHub repositories across four major Microsoft organizations — Azure, Azure‑Samples, Microsoft, and MicrosoftDocs — in early June 2026. It represents one of the most significant escalations in modern software‑supply‑chain attacks, especially because it targets AI‑assisted developer tools rather than traditional package‑install mechanisms.

What Happened

  • A malicious commit was pushed into the Azure/durabletask repository using previously compromised contributor credentials.

  • GitHub responded by disabling 73 Microsoft repositories in an automated sweep lasting 105 seconds.

  • The commit did not modify source code. Instead, it added configuration files designed to auto‑execute a 4.3–4.6 MB obfuscated JavaScript payload when opened in:

    • Claude Code

    • Gemini CLI

    • Cursor

    • Visual Studio Code

    • npm test script

Why This Attack Is Different

Traditional supply‑chain attacks rely on poisoning package registries (npm, PyPI).
Miasma bypasses that entirely by triggering execution when a developer opens a folder in an AI coding agent or IDE.

This shift from “execute on package install” to “execute on folder open” is a major evolution in supply‑chain threat tactics.

What the Payload Does

Once triggered, the worm:

  • Harvests credentials for AWS, Azure, GCP, Kubernetes, npm, GitHub, and 90+ developer tool configurations.

  • Uses stolen tokens to self‑propagate into any repository the victim can write to.

  • Creates new public repos containing stolen secrets under names like:

    • Miasma: The Spreading Blight

    • Hades – The End for the Damned

This makes it a self‑replicating worm, not just a one‑off compromise.

Connection to Earlier Attacks

The same contributor account was used in May 2026 to upload malicious durabletask PyPI packages (versions 1.4.1–1.4.3), which delivered an information‑stealer.
The June attack appears to be a re‑compromise, suggesting the attacker never lost access to the stolen credentials.

Impacted Microsoft Repositories

Examples include:

  • durabletask (.NET, Go, JS, MSSQL, Java, Netherite, protobuf)

  • azure-search-openai-demo

  • functions-container-action

  • llm-fine-tuning

  • windows-driver-docs

These are widely used in Azure Functions, Durable Functions, and AI integration workflows — meaning downstream developers may have unknowingly opened compromised repos.

Why This Matters for Developers

If a developer cloned or opened any affected repository after June 2, 2026, their workstation credentials may be compromised.
StepSecurity recommends immediate credential rotation for all cloud and GitHub tokens.

What Miasma Actually Is

  • A variant of the Mini Shai‑Hulud worm, publicly released by TeamPCP in mid‑May 2026.

  • Continues to mutate and spread across ecosystems (GitHub, PyPI, npm).

The most important mitigation for the Miasma worm is credential rotation and workstation cleanup, because the worm’s entire propagation mechanism depends on stolen cloud, GitHub, and developer‑tool tokens. All major sources agree that any developer who opened an affected Microsoft repository after June 2, 2026 must assume compromise. 

Below is a consolidated, authoritative mitigation plan based strictly on the published incident analyses.

1. Immediately Rotate All Credentials

This is the #1 required action.

Rotate every credential that may have been accessible on any machine that opened an affected repo:

  • GitHub PATs, SSH keys, fine‑grained tokens

  • Azure, AWS, GCP CLI credentials

  • Kubernetes kubeconfigs

  • npm tokens

  • Vault tokens

  • Any cloud or CI/CD secrets stored locally

StepSecurity and multiple security researchers explicitly warn that developers should rotate credentials if affected repositories were opened after June 2. 

The worm steals over 90 developer‑tool configurations, so assume broad exposure. 

2. Clean and Rebuild Developer Workstations

Because the payload executes automatically when a repo is opened in tools like Claude Code, Gemini CLI, Cursor, or VS Code, the workstation itself may be compromised.

Recommended actions:

  • Reimage or fully rebuild affected developer machines (strongly recommended for high‑trust environments).

  • Remove any unauthorized .claude/, .gemini/, .cursor/, .vscode/, or .github/ scripts.

  • Delete any unknown JavaScript files, especially large obfuscated ones (4.3–4.6 MB). [^3]

3. Block and Quarantine Affected Repositories

GitHub already disabled the 73 Microsoft repos, but organizations should:

  • Block internal mirrors or forks of the affected repos.

  • Prevent CI/CD systems from pulling cached copies.

  • Audit any internal repos that developers could write to — the worm auto‑commits itself into any repo the victim has access to. 

4. Audit All Repositories for Unauthorized Commits

The worm uses stolen tokens to push malicious commits into any repo the victim can write to.

Look for:

  • Backdated commits

  • Commits with [skip ci] flags

  • Unexpected config files in AI‑tool directories

  • Large obfuscated JavaScript files (4.3–4.6 MB)

The attacker used a backdated commit with [skip ci] to evade detection. 

5. Review CI/CD Pipelines for Secret Exposure

The worm targets:

  • GitHub Actions runner memory

  • OIDC tokens

  • SLSA provenance signing flows

  • Passwordless sudo on Linux CI runners

Microsoft’s own analysis of the Red Hat variant shows the malware scrapes CI/CD secrets and republishes poisoned packages.

Actions:

  • Rotate all CI/CD secrets

  • Revoke OIDC tokens

  • Rebuild runners

  • Validate SLSA provenance for all artifacts

6. Harden AI‑Assisted Development Environments

This attack specifically exploited AI coding tools.

Recommended controls:

  • Disable auto‑execution of workspace tasks in VS Code

  • Block AI tool config files from executing scripts

  • Sandbox AI coding agents

  • Require manual approval for workspace‑level tasks

The worm detonates on folder open, not package install — a major shift in supply‑chain attack vectors. 

7. Verify Package Integrity Across Your Ecosystem

Miasma is a variant of the Mini Shai‑Hulud worm and has already infected:

  • Microsoft durabletask (PyPI)

  • Red Hat npm packages

  • Multiple npm repos outside registries

The Red Hat variant used authentic provenance signatures while still being malicious. 

Actions:

  • Re‑verify all dependencies with Sigstore/SLSA

  • Rebuild from trusted sources

  • Block known malicious package versions

8. Organization‑Wide Incident Response

Because this is a self‑replicating worm, treat it as a full supply‑chain compromise:

  • Notify security teams

  • Conduct enterprise‑wide credential rotation

  • Perform forensic review of developer endpoints

  • Audit cloud access logs for anomalous activity

  • Review GitHub audit logs for unexpected pushes


Comments

Post a Comment

Popular posts from this blog

Entire List Leaked for Canvas Ransomware Attack

-
Image
  ( NOTE FROM REDDITOR: All attempts at requesting edit access will be denied. If something is needed, you may email me at: storeluxorsales@gmail.com ) I am not affiliated with this group in any way - so also, please do stop asking (looking at you random press sites). - If anyone wants to save this document, feel free to make a copy. I will be deleting this copy on 10/1/2026. File from link begins below this line. _____________________ This file has been downloaded from the ShinyHunters Data Leak Site (DLS). Our DLS is accessible at these locations:     - http://shnyhntww34phqoa6dcgnvps2yu7dlwzmy5lkvejwjdo6z7bmgshzayd.onion/     - http://shinypogk4jjniry5qi7247tznop6mxdrdte2k6pdu5cyo43vdzmrwid.onion/ > These files were leaked on the ShinyHunters DLS because the victim did not pay a ransom or cooperate and comply with the ShinyHunters group. src;refs;lnks; http://web.archive.org/web/20260322033123/https://shinyhunte.rs/ http://web.archive...
Read more

WSUS CVE-2025-59287 Mitigation

-
Image
CVE-2025-59287 is a critical Remote Code Execution (RCE) vulnerability affecting Windows Server Update Services (WSUS) . Here's a detailed breakdown of what it is, how it works, and what you should do about it: Overview Disclosed: October 2025 Patch Tuesday CVSS Score: 9.8 (Critical) Affected Systems: Windows Server 2012 through 2025 (including Server Core installations) Exploitability: Microsoft rates it as “Exploitation More Likely” Technical Details The vulnerability arises from unsafe deserialization of untrusted data in WSUS. Specifically, the GetCookie() endpoint in WSUS processes encrypted AuthorizationCookie objects without proper type validation. The deserialization occurs via .NET BinaryFormatter , which is known to be insecure when handling untrusted input. Attackers can send a crafted SOAP request to WSUS over port 8530 , containing a malicious AuthorizationCookie . The cookie is decrypted using a hardcoded AES key and then deserialized, allow...
Read more

Cloud Infrastructures are Having a Bad Week

-
Image
  Today’s disruptions across Microsoft Azure and Amazon Web Services (AWS) were significant, but they’re not signs of cloud computing’s demise. Instead, they underscore the risks of centralization and the importance of designing systems that can withstand provider-level failures. What happened today? • Microsoft Azure outage: Azure’s Front Door service suffered a major disruption due to a misconfiguration, impacting services like Outlook, Xbox, Microsoft 365, and even third-party platforms like Starbucks and Alaska Airlines. The Azure website states a little more than disruption. "Azure Front Door - Connectivity issues - Observing recovery Starting at approximately 16:00 UTC on 29 October 2025, customers and Microsoft services leveraging Azure Front Door (AFD) may have experienced latencies, timeouts, and errors. We have confirmed that an inadvertent configuration change was the trigger event for this issue. Affected Azure services may have included, but were not limited to: App S...
Read more

CVE-2025-58034 Fortinet Warnings and Mitigation

-
Image
Type: OS Command Injection vulnerability (CWE-78) Affected Product: Fortinet FortiWeb (Web Application Firewall) Affected Versions: 8.0.0 – 8.0.1 7.6.0 – 7.6.5 7.4.0 – 7.4.10 7.2.0 – 7.2.11 7.0.0 – 7.0.11 [nvd.nist.gov] , [cvedetails.com] Description The vulnerability is caused by improper neutralization of special elements used in OS commands . An authenticated attacker can exploit this flaw by sending crafted HTTP requests or CLI commands , allowing them to execute arbitrary code on the underlying system. This can compromise the integrity, confidentiality, and availability of the device. [nvd.nist.gov] , [cvedetails.com] Severity CVSS v3.1 Base Score: 7.2 (High) Vector: AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H Attack Vector: Network Attack Complexity: Low Privileges Required: High User Interaction: None Impact: High on Confidentiality, Integrity, and Availability [cvedetails.com] Exploitation Status Actively Exploited: Yes. Fortinet confirmed expl...
Read more

Broadcom is dismantling of VMware Cloud Service Providers (VCSPs)

-
Image
  What Broadcom Is Doing to the VCSP Program 1. Broadcom is shutting down the existing VCSP program Multiple sources confirm that Broadcom issued formal non‑renewal notices to many VMware Cloud Service Providers, ending contracts as of January 26, 2026 . Partners may finish existing commitments but cannot renew or create new long‑term contract commitments . 2. Moving to an invite‑only VCSP ecosystem Broadcom is replacing the open VCSP model with a highly selective, invite‑only program , keeping only a small fraction of providers . For example: • Only 19 providers in the U.S. were retained out of thousands. • Hundreds of European providers are being cut loose. 3. White Label program sunset (critical for smaller providers) The White Label model—previously the path for smaller CSPs—has been terminated (or will be phased out depending on region). This effectively eliminates market access for many small providers. 4. Providers that are cut must hand off customers Broadcom directs ...
Read more

FBI Seizes RAMP Cybercrime Forum

-
Image
The FBI has taken down RAMP (Russian Anonymous Marketplace) , one of the most active cybercrime forums used by ransomware gangs, initial access brokers, malware sellers, and extortion groups . The takedown affected both the clearnet and dark‑web (Tor) domains, which now display official FBI/DOJ seizure notices. Why RAMP Was Significant RAMP was: Known as “the only place ransomware allowed.” A major hub for groups including LockBit, ALPHV/BlackCat, Conti, DragonForce, Qilin, RansomHub , and more. A high‑trust marketplace offering malware, exploits, tutorials, and escrow services . Home to 14,000+ vetted users , some paying fees for anonymity. Impact of the Seizure 1. Major Disruption to Criminal Infrastructure The takedown is seen as a meaningful blow against ransomware‑as‑a‑service communities. 2. Forced Migration to Other Forums Criminal groups are already shifting activity to alternative platforms like Rehub . These migrations are chaotic and risky for criminals due to: Loss of rep...
Read more

CodeRED emergency alert system is currently down across many regions!

-
Image
  CodeRED emergency alert system is currently down across many regions in the U.S. following a ransomware attack on its vendor, Crisis24. The incident has disrupted critical emergency communications and exposed user data. What Happened Attack Type : Ransomware Threat Actor : INC ransomware group Target : OnSolve CodeRED platform (owned by Crisis24) Impact : Emergency alerts (weather, missing persons, terror threats) are unavailable in many municipalities. Personal data compromised : names, addresses, emails, phone numbers, and passwords used to create CodeRED accounts. Key Details Date of Outage : Began in early November 2025, publicly confirmed Nov 26 Scope : Hundreds of municipalities affected nationwide Response : Crisis24 is migrating customers to a new CodeRED platform hosted in a separate, hardened environment. Some cities (e.g., Douglas County, CO) have terminated their CodeRED contracts and are seeking replacements. Others are using social media, door-...
Read more

Notepad++ update service was compromised

-
Image
  Notepad++ update service was compromised Multiple independent security investigations confirm that Notepad++’s update infrastructure was hijacked between June and December 2025 . This was a supply-chain attack originating from a compromise at the hosting‑provider level , not from Notepad++’s code. What exactly was compromised? 1. Update traffic was intercepted and redirected Attackers manipulated the update endpoint ( getDownloadUrl.php ) so that some users requesting updates were silently redirected to malicious servers serving tampered executables . 2. It was targeted , not widespread All sources emphasize that only specific users were affected, likely in an espionage‑focused campaign , not a mass malware distribution effort. 3. Hosting provider compromise, not a Notepad++ bug The attackers gained access to the shared hosting environment , losing direct access in September 2025 but maintaining stolen internal service credentials through December 2, 2025. Attribution: Likely...
Read more

SitusAMC Breached!

-
Image
  What Happened? On November 12, 2025 , SitusAMC detected unauthorized access to its systems. Hackers exfiltrated sensitive corporate and client-related data. The attack did not involve ransomware or encrypting malware , suggesting the goal was data theft rather than disruption. [techcrunch.com] Data Impacted Corporate data : Accounting records, legal agreements, and internal contracts. Client-related data : Information tied to residential mortgage loans, which may include personally identifiable information (PII) such as Social Security numbers and financial details. The exact scope and number of affected individuals is still under investigation. [ibtimes.co.uk] Who Is Affected Major U.S. banks including JPMorgan Chase, Citigroup, and Morgan Stanley were notified that their data may have been exposed. SitusAMC works with hundreds of lenders, so the potential ripple effect across the financial sector is significant. [webpronews.com] SitusAMC has contained the breach,...
Read more

Cyber Monday Fraud Alert

-
Image
Cyber Monday brings incredible deals—but it also attracts cybercriminals looking to exploit shoppers . Fraudsters use fake websites, phishing emails, and misleading ads to steal money, personal information, or identities. Common Scams Fake retailer sites : Look-alike domains with odd spellings or missing security (no HTTPS). Phishing emails & texts : “Exclusive deals” or “delivery issues” that link to malicious sites. Too-good-to-be-true offers : Deep discounts on electronics, gift cards, or luxury items. Charity scams : Fraudulent donation sites targeting Giving Tuesday generosity. How to Stay Safe Shop only on trusted, secure websites (look for HTTPS). Type retailer URLs directly— don’t click links in emails or ads. Use credit cards for stronger fraud protection. Compare prices across trusted platforms to spot fake “discounts.” Verify charities before donating. Report Fraud If you suspect a scam: Contact your bank or credit card provider immediately . Report ...
Read more