Iranian Government-Sponsored Actors Conduct Cyber Operations Against Global Government and Commercial Networks
Actions to Take Today to Protect Against Malicious Activity
* Search for indicators of compromise.
* Use antivirus software.
* Patch all systems.
* Prioritize patching known exploited vulnerabilities.
* Train users to recognize and report phishing attempts.
* Use multi-factor authentication.
Note: this advisory uses the MITRE Adversarial Tactics, Techniques, and Common Knowledge (ATT&CK®) framework, version 10. See the ATT&CK for Enterprise for all referenced threat actor tactics and techniques.
The Federal Bureau of Investigation (FBI), the Cybersecurity and Infrastructure Security Agency (CISA), the U.S. Cyber Command Cyber National Mission Force (CNMF), and the United Kingdom’s National Cyber Security Centre (NCSC-UK) have observed a group of Iranian government-sponsored advanced persistent threat (APT) actors, known as MuddyWater, conducting cyber espionage and other malicious cyber operations targeting a range of government and private-sector organizations across sectors—including telecommunications, defense, local government, and oil and natural gas—in Asia, Africa, Europe, and North America. Note: MuddyWater is also known as Earth Vetala, MERCURY, Static Kitten, Seedworm, and TEMP.Zagros.
MuddyWater is a subordinate element within the Iranian Ministry of Intelligence and Security (MOIS). This APT group has conducted broad cyber campaigns in support of MOIS objectives since approximately 2018. MuddyWater actors are positioned both to provide stolen data and accesses to the Iranian government and to share these with other malicious cyber actors.
MuddyWater actors are known to exploit publicly reported vulnerabilities and use open-source tools and strategies to gain access to sensitive data on victims’ systems and deploy ransomware. These actors also maintain persistence on victim networks via tactics such as side-loading dynamic link libraries (DLLs)—to trick legitimate programs into running malware—and obfuscating PowerShell scripts to hide command and control (C2) functions. FBI, CISA, CNMF, and NCSC-UK have observed MuddyWater actors recently using various malware—variants of PowGoop, Small Sieve, Canopy (also known as Starwhale), Mori, and POWERSTATS—along with other tools as part of their malicious activity.
This advisory provides observed tactics, techniques, and procedures (TTPs); malware; and indicators of compromise (IOCs) associated with this Iranian government-sponsored APT activity to aid organizations in the identification of malicious activity against sensitive networks.
FBI, CISA, CNMF, NCSC-UK, and the National Security Agency (NSA) recommend organizations apply the mitigations in this advisory and review the following resources for additional information. Note: also see the Additional Resources section.
- Malware Analysis Report – MAR-10369127-1.v1: MuddyWater
- IOCs – AA22-052A.stix and MAR-10369127-1.v1.stix
- CISA's webpage – Iran Cyber Threat Overview and Advisories
- NCSC-UK MAR – Small Sieve
- CNMF's press release – Iranian intel cyber suite of malware uses open source tools
Click here for a PDF version of this report.
FBI, CISA, CNMF, and NCSC-UK have observed the Iranian government-sponsored MuddyWater APT group employing spearphishing, exploiting publicly known vulnerabilities, and leveraging multiple open-source tools to gain access to sensitive government and commercial networks.
As part of its spearphishing campaign, MuddyWater attempts to coax their targeted victim into downloading ZIP files, containing either an Excel file with a malicious macro that communicates with the actor’s C2 server or a PDF file that drops a malicious file to the victim’s network [T1566.001, T1204.002]. MuddyWater actors also use techniques such as side-loading DLLs [T1574.002] to trick legitimate programs into running malware and obfuscating PowerShell scripts [T1059.001] to hide C2 functions [T1027] (see the PowGoop section for more information).
Additionally, the group uses multiple malware sets—including PowGoop, Small Sieve, Canopy/Starwhale, Mori, and POWERSTATS—for loading malware, backdoor access, persistence [TA0003], and exfiltration [TA0010]. See below for descriptions of some of these malware sets, including newer tools or variants to the group’s suite. Additionally, see Malware Analysis Report MAR-10369127.r1.v1: MuddyWater for further details.
MuddyWater actors use new variants of PowGoop malware as their main loader in malicious operations; it consists of a DLL loader and a PowerShell-based downloader. The malicious file impersonates a legitimate file that is signed as a Google Update executable file.
- A DLL file renamed as a legitimate filename,
Goopdate.dll, to enable the DLL side-loading technique [T1574.002]. The DLL file is contained within an executable,
- A PowerShell script, obfuscated as a .dat file,
goopdate.dat, used to decrypt and run a second obfuscated PowerShell script,
config.txt, an encoded, obfuscated PowerShell script containing a beacon to a hardcoded IP address.
These components retrieve encrypted commands from a C2 server. The DLL file hides communications with MuddyWater C2 servers by executing with the Google Update service.
According to a sample analyzed by NCSC-UK, Small Sieve is a simple Python [T1059.006] backdoor distributed using a Nullsoft Scriptable Install System (NSIS) installer,
gram_app.exe. The NSIS installs the Python backdoor,
index.exe, and adds it as a registry run key [T1547.001], enabling persistence [TA0003].
MuddyWater disguises malicious executables and uses filenames and Registry key names associated with Microsoft's Windows Defender to avoid detection during casual inspection. The APT group has also used variations of Microsoft (e.g., "Microsift") and Outlook in its filenames associated with Small Sieve [T1036.005].
Small Sieve provides basic functionality required to maintain and expand a foothold in victim infrastructure and avoid detection [TA0005] by using custom string and traffic obfuscation schemes together with the Telegram Bot application programming interface (API). Specifically, Small Sieve’s beacons and taskings are performed using Telegram API over Hypertext Transfer Protocol Secure (HTTPS) [T1071.001], and the tasking and beaconing data is obfuscated through a hex byte swapping encoding scheme combined with an obfuscated Base64 function [T1027], T1132.002].
Note: cybersecurity agencies in the United Kingdom and the United States attribute Small Sieve to MuddyWater with high confidence.
See Appendix B for further analysis of Small Sieve malware.
MuddyWater also uses Canopy/Starwhale malware, likely distributed via spearphishing emails with targeted attachments [T1566.001]. According to two Canopy/Starwhale samples analyzed by CISA, Canopy uses Windows Script File (.wsf) scripts distributed by a malicious Excel file. Note: the cybersecurity agencies of the United Kingdom and the United States attribute these malware samples to MuddyWater with high confidence.
In the samples CISA analyzed, a malicious Excel file,
Cooperation terms.xls, contained macros written in Visual Basic for Applications (VBA) and two encoded Windows Script Files. When the victim opens the Excel file, they receive a prompt to enable macros [T1204.002]. Once this occurs, the macros are executed, decoding and installing the two embedded Windows Script Files.
The first .wsf is installed in the current user startup folder [T1547.001] for persistence. The file contains hexadecimal (hex)-encoded strings that have been reshuffled [T1027]. The file executes a command to run the second .wsf.
The second .wsf also contains hex-encoded strings that have been reshuffled. This file collects [TA0035] the victim system’s IP address, computer name, and username [T1005]. The collected data is then hex-encoded and sent to an adversary-controlled IP address,
http[:]88.119.170[.]124, via an HTTP POST request [T1041].
MuddyWater also uses the Mori backdoor that uses Domain Name System tunneling to communicate with the group’s C2 infrastructure [T1572].
According to one sample analyzed by CISA,
FML.dll, Mori uses a DLL written in C++ that is executed with
regsvr32.exe with export
DllRegisterServer; this DLL appears to be a component to another program.
FML.dll contains approximately 200MB of junk data [T1001.001] in a resource directory 205, number 105. Upon execution,
FML.dll creates a mutex,
0x50504060, and performs the following tasks:
- Deletes the file
FILENAME.oldand deletes file by registry value. The filename is the DLL file with a
- Resolves networking APIs from strings that are ADD-encrypted with the key
- Uses Base64 and Java Script Object Notation (JSON) based on certain key values passed to the JSON library functions. It appears likely that JSON is used to serialize C2 commands and/or their results.
- Communicates using HTTP over either IPv4 or IPv6, depending on the value of an unidentified flag, for C2 [T1071.001].
- Reads and/or writes data from the following Registry Keys,
This group is also known to use the POWERSTATS backdoor, which runs PowerShell scripts to maintain persistent access to the victim systems [T1059.001].
MuddyWater actors are also known to exploit unpatched vulnerabilities as part of their targeted operations. FBI, CISA, CNMF, and NCSC-UK have observed this APT group recently exploiting the Microsoft Netlogon elevation of privilege vulnerability (CVE-2020-1472) and the Microsoft Exchange memory corruption vulnerability (CVE-2020-0688). See CISA’s Known Exploited Vulnerabilities Catalog for additional vulnerabilities with known exploits and joint Cybersecurity Advisory: Iranian Government-Sponsored APT Cyber Actors Exploiting Microsoft Exchange and Fortinet Vulnerabilities for additional Iranian APT group-specific vulnerability exploits.
The following script is an example of a survey script used by MuddyWater to enumerate information about victim computers. It queries the Windows Management Instrumentation (WMI) service to obtain information about the compromised machine to generate a string, with these fields separated by a delimiter (e.g.,
;; in this sample). The produced string is usually encoded by the MuddyWater implant and sent to an adversary-controlled IP address.
Newly Identified PowerShell Backdoor
The newly identified PowerShell backdoor used by MuddyWater below uses a single-byte Exclusive-OR (XOR) to encrypt communications with the key 0x02 to adversary-controlled infrastructure. The script is lightweight in functionality and uses the InvokeScript method to execute responses received from the adversary.
MITRE ATT&CK Techniques
MuddyWater uses the ATT&CK techniques listed in table 1.
Table 1: MuddyWater ATT&CK Techniques
|Gather Victim Identity Information: Email Addresses
|MuddyWater has specifically targeted government agency employees with spearphishing emails.
|Acquire Infrastructure: Web Services
|MuddyWater has used file sharing services including OneHub to distribute tools.
|Obtain Capabilities: Tool
|MuddyWater has made use of legitimate tools ConnectWise and RemoteUtilities for access to target environments.
|Phishing: Spearphishing Attachment
|MuddyWater has compromised third parties and used compromised accounts to send spearphishing emails with targeted attachments.
|Phishing: Spearphishing Link
|MuddyWater has sent targeted spearphishing emails with malicious links.
|Windows Management Instrumentation
|MuddyWater has used malware that leveraged Windows Management Instrumentation for execution and querying host information.
|Command and Scripting Interpreter: PowerShell
|MuddyWater has used PowerShell for execution.
|Command and Scripting Interpreter: Windows Command Shell
|MuddyWater has used a custom tool for creating reverse shells.
|Command and Scripting Interpreter: Visual Basic
|MuddyWater has used Virtual Basic Script (VBS) files to execute its POWERSTATS payload, as well as macros.
|Command and Scripting Interpreter: Python
|MuddyWater has used developed tools in Python including Out1.
|Exploitation for Client Execution
|MuddyWater has exploited the Office vulnerability CVE-2017-0199 for execution.
|User Execution: Malicious Link
|MuddyWater has distributed URLs in phishing emails that link to lure documents.
|User Execution: Malicious File
|MuddyWater has attempted to get users to enable macros and launch malicious Microsoft Word documents delivered via spearphishing emails.
|Inter-Process Communication: Component Object Model
|MuddyWater has used malware that has the capability to execute malicious code via COM, DCOM, and Outlook.
|Inter-Process Communication: Dynamic Data Exchange
|MuddyWater has used malware that can execute PowerShell scripts via Dynamic Data Exchange.
|Scheduled Task/Job: Scheduled Task
|MuddyWater has used scheduled tasks to establish persistence.
|Office Application Startup: Office Template Macros
|MuddyWater has used a Word Template,
Normal.dotm, for persistence.
|Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder
|MuddyWater has added Registry Run key
KCU\Software\Microsoft\Windows\CurrentVersion\Run\SystemTextEncoding to establish persistence.
|Abuse Elevation Control Mechanism: Bypass User Account Control
|MuddyWater uses various techniques to bypass user account control.
|Credentials from Password Stores
|MuddyWater has performed credential dumping with LaZagne and other tools, including by dumping passwords saved in victim email.
|Credentials from Web Browsers
|MuddyWater has run tools including Browser64 to steal passwords saved in victim web browsers.
|Obfuscated Files or Information
|MuddyWater has used Daniel Bohannon’s Invoke-Obfuscation framework and obfuscated PowerShell scripts. The group has also used other obfuscation methods, including Base64 obfuscation of VBScripts and PowerShell commands.
|Compile After Delivery
|MuddyWater has used the
csc.exe tool to compile executables from downloaded C# code.
|Masquerading: Match Legitimate Name or Location
|MuddyWater has disguised malicious executables and used filenames and Registry key names associated with Windows Defender. E.g., Small Sieve uses variations of Microsoft (Microsift) and Outlook in its filenames to attempt to avoid detection during casual inspection.
|Deobfuscate/Decode Files or Information
|MuddyWater decoded Base64-encoded PowerShell commands using a VBS file.
|Signed Binary Proxy Execution: CMSTP
|MuddyWater has used
CMSTP.exe and a malicious
.INF file to execute its POWERSTATS payload.
|Signed Binary Proxy Execution: Mshta
|MuddyWater has used
mshta.exe to execute its POWERSTATS payload and to pass a PowerShell one-liner for execution.
|Signed Binary Proxy Execution: Rundll32
|MuddyWater has used malware that leveraged
rundll32.exe in a Registry Run key to execute a
|The Small Sieve payload used by MuddyWater will only execute correctly if the word “Platypus” is passed to it on the command line.
|Impair Defenses: Disable or Modify Tools
|MuddyWater can disable the system's local proxy settings.
|OS Credential Dumping: LSASS Memory
|MuddyWater has performed credential dumping with Mimikatz and
|OS Credential Dumping: LSA Secrets
|MuddyWater has performed credential dumping with LaZagne.
|OS Credential Dumping: Cached Domain Credentials
|MuddyWater has performed credential dumping with LaZagne.
|Unsecured Credentials: Credentials In Files
|MuddyWater has run a tool that steals passwords saved in victim email.
|System Network Configuration Discovery
|MuddyWater has used malware to collect the victim’s IP address and domain name.
|System Owner/User Discovery
|MuddyWater has used malware that can collect the victim’s username.
|System Network Connections Discovery
|MuddyWater has used a PowerShell backdoor to check for Skype connections on the target machine.
|MuddyWater has used malware to obtain a list of running processes on the system.
|System Information Discovery
|MuddyWater has used malware that can collect the victim’s OS version and machine name.
|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."
|Account Discovery: Domain Account
|MuddyWater has used
cmd.exe net user/domain to enumerate domain users.
|MuddyWater has used a PowerShell backdoor to check for Skype connectivity on the target machine.
|Security Software Discovery
|MuddyWater has used malware to check running processes against a hard-coded list of security tools often used by malware researchers.
|MuddyWater has used malware that can capture screenshots of the victim’s machine.
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.
|Command and Control
|Application Layer Protocol: Web Protocols
|MuddyWater has used HTTP for C2 communications. e.g., Small Sieve beacons and tasking are performed using the Telegram API over HTTPS.
|Proxy: External Proxy
MuddyWater has controlled POWERSTATS from behind a proxy network to obfuscate the C2 location.
MuddyWater has used a series of compromised websites that victims connected to randomly to relay information to C2.
|Web Service: Bidirectional Communication
|MuddyWater has used web services including OneHub to distribute remote access tools.
|MuddyWater has used one C2 to obtain enumeration scripts and monitor web logs, but a different C2 to send data back.
|Ingress Tool Transfer
|MuddyWater has used malware that can upload additional files to the victim’s machine.
|Data Encoding: Standard Encoding
|MuddyWater has used tools to encode C2 communications including Base64 encoding.
|Data Encoding: Non-Standard Encoding
|MuddyWater uses tools such as Small Sieve, which employs a custom hex byte swapping encoding scheme to obfuscate tasking traffic.
|Remote Access Software
|MuddyWater has used a legitimate application, ScreenConnect, to manage systems remotely and move laterally.
|Exfiltration Over C2 Channel
|MuddyWater has used C2 infrastructure to receive exfiltrated data.
Protective Controls and Architecture
- Deploy application control software to limit the applications and executable code that can be run by users. Email attachments and files downloaded via links in emails often contain executable code.
Identity and Access Management
- Use multifactor authentication where possible, particularly for webmail, virtual private networks, and accounts that access critical systems.
- Limit the use of administrator privileges. Users who browse the internet, use email, and execute code with administrator privileges make for excellent spearphishing targets because their system—once infected—enables attackers to move laterally across the network, gain additional accesses, and access highly sensitive information.
- Enable antivirus and anti-malware software and update signature definitions in a timely manner. Well-maintained antivirus software may prevent use of commonly deployed attacker tools that are delivered via spearphishing.
- Be suspicious of unsolicited contact via email or social media from any individual you do not know personally. Do not click on hyperlinks or open attachments in these communications.
- Consider adding an email banner to emails received from outside your organization and disabling hyperlinks in received emails.
- Train users through awareness and simulations to recognize and report phishing and social engineering attempts. Identify and suspend access of user accounts exhibiting unusual activity.
- Adopt threat reputation services at the network device, operating system, application, and email service levels. Reputation services can be used to detect or prevent low-reputation email addresses, files, URLs, and IP addresses used in spearphishing attacks.
Vulnerability and Configuration Management
- Install updates/patch operating systems, software, and firmware as soon as updates/patches are released. Prioritize patching known exploited vulnerabilities.
- For more information on Iranian government-sponsored malicious cyber activity, see CISA's webpage – Iran Cyber Threat Overview and Advisories and CNMF's press release – Iranian intel cyber suite of malware uses open source tools.
- For information and resources on protecting against and responding to ransomware, refer to StopRansomware.gov, a centralized, whole-of-government webpage providing ransomware resources and alerts.
- The joint advisory from the cybersecurity authorities of Australia, Canada, New Zealand, the United Kingdom, and the United States: Technical Approaches to Uncovering and Remediating Malicious Activity provides additional guidance when hunting or investigating a network and common mistakes to avoid in incident handling.
- CISA offers a range of no-cost cyber hygiene services to help critical infrastructure organizations assess, identify, and reduce their exposure to threats, including ransomware. By requesting these services, organizations of any size could find ways to reduce their risk and mitigate attack vectors.
- The U.S. Department of State’s Rewards for Justice (RFJ) program offers a reward of up to $10 million for reports of foreign government malicious activity against U.S. critical infrastructure. See the RFJ website for more information and how to report information securely.
The information you have accessed or received is being provided “as is” for informational purposes only. The FBI, CISA, CNMF, and NSA do not endorse any commercial product or service, including any subjects of analysis. Any reference to specific commercial products, processes, or services by service mark, trademark, manufacturer, or otherwise, does not constitute or imply their endorsement, recommendation, or favoring by the FBI, CISA, CNMF, or NSA.
This document was developed by the FBI, CISA, CNMF, NCSC-UK, and NSA in furtherance of their respective cybersecurity missions, including their responsibilities to develop and issue cybersecurity specifications and mitigations. This information may be shared broadly to reach all appropriate stakeholders. The United States’ NSA agrees with this attribution and the details provided in this report.
Appendix A: IOCs
The following IP addresses are associated with MuddyWater activity:
Appendix B: Small Sieve
Note: the information contained in this appendix is from NCSC-UK analysis of a Small Sieve sample.
Table 2: Gram.app.exe Metadata
|NSIS installer that installs and runs the index.exe backdoor and adds a persistence registry key
|2021-09-25 21:57:46 UTC
Table 3: Index.exe Metadata
|The final PyInstaller-bundled Python 3.9 backdoor
|2021-08-01 04:39:46 UTC
Small Sieve is distributed as a large (16MB) NSIS installer named
gram_app.exe, which does not appear to masquerade as a legitimate application. Once executed, the backdoor binary
index.exe is installed in the user’s
AppData/Roaming directory and is added as a Run key in the registry to enabled persistence after reboot.
The installer then executes the backdoor with the “Platypus” argument [T1480], which is also present in the registry persistence key:
The backdoor attempts to restore previously initialized session data from
If this file does not exist, then it uses the hardcoded values listed in table 4:
Table 4: Credentials and Session Values
|This is the Telegram Channel ID that beacons are sent to, and, from which, tasking requests are received. Tasking requests are dropped if they do not come from this channel. This value cannot be changed.
|Random value between 10,000,000 and 90,000,000
|This is a bot identifier generated at startup that is sent to the C2 in the initial beacon. Commands must be prefixed with
/com[Bot ID] in order to be processed by the malware.
|This is the initial token used to authenticate each message to the Telegram Bot API.
Small Sieve beacons via the Telegram Bot API, sending the configured Bot ID, the currently logged-in user, and the host’s IP address, as described in the Communications (Beacon format) section below. It then waits for tasking as a Telegram bot using the python-telegram-bot module.
Two task formats are supported:
/start– no argument is passed; this causes the beacon information to be repeated.
/com[BotID] [command]– for issuing commands passed in the argument.
The following commands are supported by the second of these formats, as described in table 5:
Table 5: Supported Commands
|This command causes the backdoor to exit; it does not remove persistence.
|The URL will be fetched and saved to the provided filename using the Python urllib module
|The backdoor will reconnect to the Telegram Bot API using the provided token
newtoken. This updated token will be stored in the encoded
|The original connection to Telegram is terminated. It is likely used after a
change token command is issued.
Any commands other than those detailed in table 5 are executed directly by passing them to
cmd.exe /c, and the output is returned as a reply.
Figure 1: Execution Guardrail
Threat actors may be attempting to thwart simple analysis by not passing “Platypus” on the command line.
Internal strings and new Telegram tokens are stored obfuscated with a custom alphabet and Base64-encoded. A decryption script is included in Appendix B.
Before listening for tasking using CommandHandler objects from the python
-telegram-bot module, a beacon is generated manually using the standard
Figure 2: Manually Generated Beacon
The hex host data is encoded using the byte shuffling algorithm as described in the “Communications (Traffic obfuscation)” section of this report. The example in figure 2 decodes to:
admin/WINDOMAIN1 | 10.17.32.18
Although traffic to the Telegram Bot API is protected by TLS, Small Sieve obfuscates its tasking and response using a hex byte shuffling algorithm. A Python3 implementation is shown in figure 3.
Figure 3: Traffic Encoding Scheme Based on Hex Conversion and Shuffling
Table 6 outlines indicators of compromise.
Table 6: Indicators of Compromise
|Telegram Session Persistence File (Obfuscated)
|Installation path of the Small Sieve binary
|Registry value name
|Persistence Registry Key pointing to index.exe with a
String Recover Script
Figure 4: String Recovery Script
To report suspicious or criminal activity related to information found in this joint Cybersecurity Advisory, contact your local FBI field office at www.fbi.gov/contact-us/field-offices, or the FBI’s 24/7 Cyber Watch (CyWatch) at (855) 292-3937 or by email at CyWatch@fbi.gov. When available, please include the following information regarding the incident: date, time, and location of the incident; type of activity; number of people affected; type of equipment used for the activity; the name of the submitting company or organization; and a designated point of contact. To request incident response resources or technical assistance related to these threats, contact CISA at Central@cisa.dhs.gov. For NSA client requirements or general cybersecurity inquiries, contact the Cybersecurity Requirements Center at Cybersecurity_Requests@nsa.gov. United Kingdom organizations should report a significant cyber security incident: ncsc.gov.uk/report-an-incident (monitored 24 hours) or for urgent assistance call 03000 200 973.
February 24, 2022: Initial Version