MuddyWater is an Iranian threat group that has primarily targeted Middle Eastern nations, and has also targeted European and North American nations. The group's victims are mainly in the telecommunications, government (IT services), and oil sectors. Activity from this group was previously linked to FIN7, but the group is believed to be a distinct group possibly motivated by espionage.[1][2][3][4][5]
Name | Description |
---|---|
Earth Vetala | |
MERCURY | |
Static Kitten | |
Seedworm | |
TEMP.Zagros |
Domain | ID | Name | Use | |
---|---|---|---|---|
Enterprise | T1548 | .002 | Abuse Elevation Control Mechanism: Bypass User Account Control |
MuddyWater uses various techniques to bypass UAC.[3] |
Enterprise | T1087 | .002 | Account Discovery: Domain Account |
MuddyWater has used |
Enterprise | T1583 | .006 | Acquire Infrastructure: Web Services |
MuddyWater has used file sharing services including OneHub to distribute tools.[7][6] |
Enterprise | T1071 | .001 | Application Layer Protocol: Web Protocols |
MuddyWater has used HTTP for C2 communications.[4][6] |
Enterprise | T1560 | .001 | Archive Collected Data: Archive via Utility |
MuddyWater has used the native Windows cabinet creation tool, makecab.exe, likely to compress stolen data to be uploaded.[2] |
Enterprise | T1547 | .001 | Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder |
MuddyWater has added Registry Run key |
Enterprise | T1059 | .001 | Command and Scripting Interpreter: PowerShell |
MuddyWater has used PowerShell for execution.[8][11][9][2][3][10][5][6] |
.003 | Command and Scripting Interpreter: Windows Command Shell |
MuddyWater has used a custom tool for creating reverse shells.[2] |
||
.005 | Command and Scripting Interpreter: Visual Basic |
MuddyWater has used VBScript files to execute its POWERSTATS payload, as well as macros.[8][11][9][2][3][4][5][6] |
||
.006 | Command and Scripting Interpreter: Python |
MuddyWater has used developed tools in Python including Out1.[6] |
||
.007 | Command and Scripting Interpreter: JavaScript |
MuddyWater has used JavaScript files to execute its POWERSTATS payload.[3][8] |
||
Enterprise | T1555 | Credentials from Password Stores |
MuddyWater has performed credential dumping with LaZagne and other tools, including by dumping passwords saved in victim email.[1][2][6] |
|
.003 | Credentials from Web Browsers |
MuddyWater has run tools including Browser64 to steal passwords saved in victim web browsers.[2][6] |
||
Enterprise | T1132 | .001 | Data Encoding: Standard Encoding |
MuddyWater has used tools to encode C2 communications including Base64 encoding.[4][6] |
Enterprise | T1140 | Deobfuscate/Decode Files or Information |
MuddyWater decoded base64-encoded PowerShell commands using a VBS file.[8][11][3] |
|
Enterprise | T1041 | Exfiltration Over C2 Channel |
MuddyWater has used C2 infrastructure to receive exfiltrated data.[5] |
|
Enterprise | T1203 | Exploitation for Client Execution |
MuddyWater has exploited the Office vulnerability CVE-2017-0199 for execution.[4] |
|
Enterprise | T1083 | File and Directory Discovery |
MuddyWater has used malware that checked if the ProgramData folder had folders or files with the keywords "Kasper," "Panda," or "ESET."[9] |
|
Enterprise | T1589 | .002 | Gather Victim Identity Information: Email Addresses |
MuddyWater has specifically targeted government agency employees with spearphishing e-mails.[7] |
Enterprise | T1562 | .001 | Impair Defenses: Disable or Modify Tools |
MuddyWater can disable the system's local proxy settings.[6] |
Enterprise | T1105 | Ingress Tool Transfer |
MuddyWater has used malware that can upload additional files to the victim’s machine.[9][3][5][6] |
|
Enterprise | T1559 | .001 | Inter-Process Communication: Component Object Model |
MuddyWater has used malware that has the capability to execute malicious code via COM, DCOM, and Outlook.[9][4] |
.002 | Inter-Process Communication: Dynamic Data Exchange |
MuddyWater has used malware that can execute PowerShell scripts via DDE.[9] |
||
Enterprise | T1036 | .005 | Masquerading: Match Legitimate Name or Location |
MuddyWater has disguised malicious executables and used filenames and Registry key names associated with Windows Defender.[8][10][7] |
Enterprise | T1104 | Multi-Stage Channels |
MuddyWater has used one C2 to obtain enumeration scripts and monitor web logs, but a different C2 to send data back.[10] |
|
Enterprise | T1027 | Obfuscated Files or Information |
MuddyWater has used Daniel Bohannon’s Invoke-Obfuscation framework and obfuscated PowerShell scripts.[1][12] The group has also used other obfuscation methods, including Base64 obfuscation of VBScripts and PowerShell commands.[1][8][9][10][4][6] |
|
.003 | Steganography |
MuddyWater has stored obfuscated JavaScript code in an image file named temp.jpg.[3] |
||
.004 | Compile After Delivery |
MuddyWater has used the .NET csc.exe tool to compile executables from downloaded C# code.[3] |
||
Enterprise | T1588 | .002 | Obtain Capabilities: Tool |
MuddyWater has made use of legitimate tools ConnectWise and RemoteUtilities for access to target environments.[7] |
Enterprise | T1137 | .001 | Office Application Startup: Office Template Macros |
MuddyWater has used a Word Template, Normal.dotm, for persistence.[5] |
Enterprise | T1003 | .001 | OS Credential Dumping: LSASS Memory |
MuddyWater has performed credential dumping with Mimikatz and procdump64.exe.[1][2][6] |
.004 | OS Credential Dumping: LSA Secrets |
MuddyWater has performed credential dumping with LaZagne.[1][2] |
||
.005 | OS Credential Dumping: Cached Domain Credentials |
MuddyWater has performed credential dumping with LaZagne.[1][2] |
||
Enterprise | T1566 | .001 | Phishing: Spearphishing Attachment |
MuddyWater has compromised third parties and used compromised accounts to send spearphishing emails with targeted attachments to recipients.[1][8][9][4][7][6] |
.002 | Phishing: Spearphishing Link |
MuddyWater has sent targeted spearphishing e-mails with malicious links.[7][6] |
||
Enterprise | T1057 | Process Discovery |
MuddyWater has used malware to obtain a list of running processes on the system.[9][4] |
|
Enterprise | T1090 | .002 | Proxy: External Proxy |
MuddyWater has controlled POWERSTATS from behind a proxy network to obfuscate the C2 location.[2] MuddyWater has used a series of compromised websites that victims connected to randomly to relay information to command and control (C2).[5][6] |
Enterprise | T1219 | Remote Access Software |
MuddyWater has used a legitimate application, ScreenConnect, to manage systems remotely and move laterally.[6][7] |
|
Enterprise | T1053 | .005 | Scheduled Task/Job: Scheduled Task |
MuddyWater has used scheduled tasks to establish persistence.[5] |
Enterprise | T1113 | Screen Capture |
MuddyWater has used malware that can capture screenshots of the victim’s machine.[9] |
|
Enterprise | T1218 | .003 | Signed Binary Proxy Execution: CMSTP |
MuddyWater has used CMSTP.exe and a malicious INF to execute its POWERSTATS payload.[8] |
.005 | Signed Binary Proxy Execution: Mshta |
MuddyWater has used mshta.exe to execute its POWERSTATS payload and to pass a PowerShell one-liner for execution.[8][9] |
||
.011 | Signed Binary Proxy Execution: Rundll32 |
MuddyWater has used malware that leveraged rundll32.exe in a Registry Run key to execute a .dll.[9] |
||
Enterprise | T1518 | Software Discovery |
MuddyWater has used a PowerShell backdoor to check for Skype connectivity on the target machine.[6] |
|
.001 | Security Software Discovery |
MuddyWater has used malware to check running processes against a hard-coded list of security tools often used by malware researchers.[9] |
||
Enterprise | T1082 | System Information Discovery |
MuddyWater has used malware that can collect the victim’s OS version and machine name.[9][10][5][6] |
|
Enterprise | T1016 | System Network Configuration Discovery |
MuddyWater has used malware to collect the victim’s IP address and domain name.[9] |
|
Enterprise | T1049 | System Network Connections Discovery |
MuddyWater has used a PowerShell backdoor to check for Skype connections on the target machine.[6] |
|
Enterprise | T1033 | System Owner/User Discovery |
MuddyWater has used malware that can collect the victim’s username.[9][6] |
|
Enterprise | T1552 | .001 | Unsecured Credentials: Credentials In Files |
MuddyWater has run a tool that steals passwords saved in victim email.[2] |
Enterprise | T1204 | .001 | User Execution: Malicious Link |
MuddyWater has distributed URLs in phishing e-mails that link to lure documents.[7][6] |
.002 | User Execution: Malicious File |
MuddyWater has attempted to get users to enable macros and launch malicious Microsoft Word documents delivered via spearphishing emails.[1][8][9][10][4][5][7][6] |
||
Enterprise | T1102 | .002 | Web Service: Bidirectional Communication |
MuddyWater has used web services including OneHub to distribute remote access tools.[7] |
Enterprise | T1047 | Windows Management Instrumentation |
MuddyWater has used malware that leveraged WMI for execution and querying host information.[9][3][10] |