MuddyWater Uses Chaos Ransomware as Decoy in Microsoft Teams Credential Theft Campaign

·

Rapid7 researchers have attributed a false flag ransomware operation to MuddyWater — an Iranian advanced persistent threat group operating under the Ministry of Intelligence and Security (MOIS). The campaign, active since early 2026, used Chaos ransomware as a decoy to mask the group's actual objective: credential theft and cyber-espionage via manipulated Microsoft Teams sessions.

The intrusion chain began with external Teams chat requests to employees, progressed to interactive screen-sharing sessions, and resulted in credential harvesting and MFA setting modifications. In select cases, the attackers deployed AnyDesk or DWAgent for persistent remote access, followed by a custom backdoor. Chaos ransomware was deployed last — not for financial gain, but to trigger incident response procedures that would overwrite forensic artifacts and complicate attribution.

As of late March 2026, Chaos had claimed 36 victims on its leak site, predominantly US organizations in construction, manufacturing, and business services. Any organization with external Microsoft Teams access enabled should treat this as an active threat requiring immediate review of Teams external communication policies.

◈ Table of Contents

01Threat Actor Profile 02Victims & Targeting 03TTPs & Kill Chain 04Indicators of Compromise 05Detection Logic 06Hunt Recommendations 07Sources & References
🕵️

Phase 1 — Threat Actor Profile

APT / MOIS
AttributeDetail
Primary NameMuddyWater
AliasesMango Sandstorm, Seedworm, Static Kitten, MERCURY, TA450
SponsorIranian Ministry of Intelligence and Security (MOIS)
Active Since2017 (ongoing; increased tempo in 2026)
Primary ObjectiveCyber-espionage, credential theft, pre-positioning for disruptive operations
Primary TargetsUS, Israeli, and Western European organizations; government, defense, critical infrastructure, construction, manufacturing
Signature ToolsLigolo-ng, DWAgent, AnyDesk, pythonw.exe injection, custom PowerShell loaders
False Flag TacticChaos ransomware deployed post-espionage to overwrite forensic artifacts and generate misleading attribution

MuddyWater has a documented history of false flag operations — they previously used BlackShadow and DEV-0228 personas. Chaos ransomware does not represent a pivot to financially motivated crime; it is an operational security tool used to burn evidence and misdirect incident response.

🎯

Phase 2 — Victims & Targeting

36 confirmed

As of late March 2026, the Chaos ransomware leak site listed 36 victims. Rapid7's assessment is that a subset of these were actual MuddyWater intrusions masked under the Chaos brand. Targeting skews heavily toward US organizations across sectors where sensitive project, contract, and personnel data has intelligence value to Iranian state interests.

Chaos ransomware victim sector distribution 2026
Chaos ransomware victim sector breakdown — approximate distribution based on Rapid7 and leak site data (Q1 2026)
🏗️

Construction & Engineering

Defense contractor subcontractors and engineering firms hold sensitive project specifications, personnel clearance data, and government contract details — high-value targets for MOIS.

🏭

Manufacturing

Industrial manufacturers with US Department of Defense supply chain relationships represent strategic intelligence value. Credentials from these environments can enable lateral access to prime contractors.

🏛️

Government Contractors

Organizations providing services to US federal agencies face direct targeting. MuddyWater prioritizes credential access to cloud environments hosting government data.

⚔️

Phase 3 — TTPs & Kill Chain

T1566 → T1486
MuddyWater 2026 attack chain — Teams lure through Chaos ransomware false flag deployment
MITRE TechniqueIDObserved Behavior
Phishing via ServiceT1566.003External Teams chat requests to employees from attacker-controlled accounts
Valid Account AbuseT1078Harvested credentials used to authenticate to corporate cloud and VPN resources
Remote Access SoftwareT1219AnyDesk and DWAgent deployed for persistent interactive access
Input CaptureT1056Victims tricked into typing credentials into local text files during screen-sharing
Modify Auth ProcessT1556MFA settings modified to add attacker-controlled authentication methods
Process InjectionT1055pythonw.exe used to inject code into suspended processes
Data Encrypted for ImpactT1486Chaos ransomware deployed as final-stage false flag to destroy forensic artifacts
Indicator RemovalT1070Ransomware deployment triggers victim IR response that inadvertently destroys evidence
🔍

Phase 4 — Indicators of Compromise

Rapid7 Research

These IOCs are sourced from Rapid7's published research. Threat actor infrastructure rotates frequently — treat domains and IPs as high-confidence historical indicators, not guaranteed live C2. Block and hunt; do not rely solely on this list.

TypeIndicatorContext
Domain (C2)moonzonet[.]comMuddyWater C2 domain active in early 2026 campaigns targeting Israeli and Western organizations
Malware Loaderms_upd.exeDrops custom backdoor; disguised as a Microsoft update component
BackdoorGame.exeCustom backdoor disguised as Microsoft WebView2 application; supports 12 C2 commands including PowerShell execution, file upload/delete, persistent shell
RAT / PersistenceDWAgent, AnyDeskLegitimate remote management tools abused for persistent interactive access post-compromise
Injection Processpythonw.exeSignature MuddyWater technique — pythonw.exe used to inject shellcode into suspended processes
RansomwareChaos ransomware variantsDeployed as terminal false flag; not used for ransom collection — used to destroy forensic artifacts
📄
Rapid7 Threat Research — Muddying the Tracks: Full IOC List and Analysis
rapid7.com — Detailed IOC tables, behavioral indicators, and network signatures
→
🛡️

Phase 5 — Detection Logic

KQL / Sigma
KQL — Microsoft Sentinel: Detect External Teams Chat Initiation from New Domains
// Hunt for external Teams messages from domains not seen in last 30 days // Requires Microsoft 365 Defender / Sentinel M365D connector TeamsMessages | where Timestamp > ago(7d) | where SenderType == "External" | summarize FirstSeen=min(Timestamp), MsgCount=count() by SenderDomain, RecipientUPN | where FirstSeen > ago(7d) | where MsgCount between (1 .. 5) // Low-volume, new-domain external contacts are MuddyWater's preferred lure pattern | join kind=leftouter ( EmailEvents | where Timestamp > ago(30d) | summarize KnownDomain=count() by SenderDomain ) on SenderDomain | where isempty(KnownDomain) | project FirstSeen, SenderDomain, RecipientUPN, MsgCount
KQL — Detect AnyDesk / DWAgent Installation Post-Teams Contact
// Flag remote access tool installs within 24h of an external Teams contact DeviceProcessEvents | where Timestamp > ago(7d) | where FileName in~ ("anydesk.exe", "DWAgent.exe", "dwagent.exe", "dwrcs.exe") | where InitiatingProcessFileName !in~ ("msiexec.exe", "setup.exe") // Combine with Teams events on same DeviceId to correlate | project Timestamp, DeviceId, DeviceName, FileName, InitiatingProcessCommandLine, AccountName
Sigma Rule — pythonw.exe Process Injection (MuddyWater Signature)
title: MuddyWater pythonw.exe Process Injection status: stable description: Detects pythonw.exe spawning suspended child processes consistent with MuddyWater injection technique logsource: category: process_creation product: windows detection: selection: ParentImage|endswith: '\pythonw.exe' CommandLine|contains: - 'CREATE_SUSPENDED' - '-c "import ctypes' condition: selection falsepositives: - Legitimate Python automation scripts using subprocess with CREATE_SUSPENDED level: high
🔎

Phase 6 — Hunt Recommendations

Blue Team
01
Audit External Microsoft Teams Access Policies
Immediate
MuddyWater's initial access vector is external Teams chat. If your organization does not require external Teams communication with unknown domains, disable it. At minimum, enable notifications to users when an external sender initiates chat for the first time.
Actions
  • 1In Teams Admin Center, navigate to Users > External Access and restrict to allow-listed domains only.
  • 2Enable External access warnings so employees see a banner when chatting with non-organizational accounts.
  • 3Block screen sharing requests from external participants in meeting policies unless explicitly whitelisted.
02
Review MFA Configuration for Suspicious Device Additions
24h
MuddyWater manipulates MFA settings during the intrusion window to add attacker-controlled authentication factors. Audit all MFA device additions in the past 30 days, especially those added outside business hours or from unknown IP ranges.
  • 1In Entra ID (Azure AD) audit logs, query Add registered owner to device and Register user device for anomalous additions.
  • 2Alert on MFA registration from IPs that do not match the user's normal access geography.
  • 3Implement Privileged Identity Management (PIM) requiring approval for MFA method changes.
03
Hunt for Unauthorized Remote Access Tool Installation
48h
AnyDesk and DWAgent are legitimate tools that are trivially abused. Run an inventory sweep for any instances installed in the last 90 days that are not in your approved software catalog. Correlate installation timestamps with Teams chat events on the same host.
  • 1Query your EDR for anydesk.exe, DWAgent.exe, dwrcs.exe with installation timestamps in the past 90 days.
  • 2Cross-reference against your approved software inventory — any unlisted installation warrants immediate investigation.
  • 3Check for outbound connections from these processes to IPs or domains outside your normal operational geography.

If you discover Chaos ransomware artifacts on a host during investigation, do NOT immediately conclude this is a financially motivated ransomware incident. Preserve forensic copies of affected volumes before any remediation — the ransomware is a terminal stage false flag deployed to destroy evidence of prior espionage activity. Treat the encrypted host as potentially the least important system; the real damage occurred earlier in the intrusion.

📚

Phase 7 — Sources & References

7 sources
Rapid7 Threat Research — Muddying the Tracks: The State-Sponsored Shadow Behind Chaos Ransomware BleepingComputer — MuddyWater hackers use Chaos ransomware as a decoy in attacks (May 6, 2026) The Hacker News — MuddyWater Uses Microsoft Teams to Steal Credentials in False Flag Ransomware Attack Security Affairs — Iranian cyber espionage disguised as a Chaos Ransomware attack Infosecurity Magazine — Iran-Linked APT Posed as Chaos Ransomware Member in Espionage Campaign CyberSecurity News — Hackers Use Microsoft Teams to Steal Credentials and Manipulate MFA MITRE ATT&CK — MuddyWater (G0069) Group Profile

🚨 THREAT ACTOR TRACKING

Use the CyberHawk Threat Intel actor database to track MuddyWater IOCs, campaign timelines, and affiliated infrastructure. New indicators from this campaign are being added in real time.

→ CyberHawk Threat Intel — Actor Profiles & IOC Tracking

◈ Stay Connected

Follow CyberHawk Threat Intel for threat intelligence, deployment guides and hands-on SOC tooling content.

🌐 Website ▶️ YouTube ▶️ YouTube (2) 𝕏 Twitter / X ♪ TikTok ✈️ Telegram
🔍 IOC Scanner 🛠️ Live Tools 📚 Courses 🚨 Threat Intel 📝 Blog 📋 SOPs

"They can't exploit you if you are the Exploit."