Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
MalwareUsed by 2 actors

Phoenix

Phoenix is a Windows backdoor associated primarily with the Iranian state-aligned threat group MuddyWater, also tracked as Seedworm and TA450, and assessed in the provided reporting as linked to Iran’s Ministry of Intelligence and Security (MOIS). It has been used in espionage campaigns against government entities, embassies, diplomatic missions, foreign affairs ministries, consulates, international organizations, and other high-value targets across the Middle East and North Africa, with reporting also noting targeting of sectors such as energy, telecommunications, finance, maritime, and critical infrastructure.

Observed delivery has relied heavily on spear-phishing and malicious Microsoft Word documents containing VBA macros. In documented campaigns, victims were prompted to enable content, after which macro code wrote a loader to disk and installed the Phoenix backdoor. Group-IB reported malicious MuddyWater documents on VirusTotal with decoy content and embedded VBA macros designed to install Phoenix. One campaign used a compromised mailbox accessed via NordVPN to distribute the malware to more than 100 government entities and international organizations in MENA. Reporting also notes executable files disguised as PDFs and DOC files with macro code delivering Phoenix and UDPGangster.

Phoenix is described as Windows malware that enables remote control and data collection from infected systems. Reported functionality includes collection of system information such as computer name and Windows version, and in one report user credentials. Phoenix v4 communicates with command-and-control infrastructure via WinHTTP and supports commands for sleep control, file upload and download, and shell access. Group-IB reported that Phoenix v4 included an additional COM-based persistence mechanism and other functional differences from prior variants. In one documented chain, the FakeUpdate loader decrypted and installed Phoenix v4 as an AES-encrypted payload written to C:\ProgramData\sysprocupdate.exe, with persistence established through Windows Registry modifications.

Phoenix has also been referenced as part of MuddyWater’s broader malware ecosystem alongside BugSleep, StealthCache, Fooder loader, MuddyViper, RustyWater, CHAR, GhostFetch/HTTP_VIP, GhostBackDoor, and UDPGangster. Reporting states Phoenix has been used to deploy a stripped-down BugSleep variant, and a Phoenix injector was used to deploy BugSleep. Additional reporting places Phoenix in MuddyWater campaigns that also used PDQ and Action1 RMM tooling and a custom browser credential stealer targeting Chrome, Opera, Brave, and Edge.

The provided content also contains unrelated references to other malware using the same name, including a historical virus attributed to Dark Avenger and mentions of Phoenix as an Android malware codebase ancestor in reporting on Perseus. However, the dominant and high-confidence usage in the supplied material refers to the MuddyWater/Seedworm Windows backdoor.

Share:
For your environment

Hunt this family in your stack

Mallory pivots from this family to the IOCs, detections, and named campaigns that touch your stack, and pages you when something new lands.

THREAT ACTORS

Groups observed using it

2 distinct threat actors attributed by public researchers. Open in Mallory to see the full evidence chain and overlapping campaigns.

View more details
MuddyWater

Group-IB said samples of MuddyWater malicious documents obtained from VirusTotal feature decoy content and embedded VBA macros designed to install the Phoenix backdoor.

via bank info securitybankinfosecurity.com
Turla

“It also started using a new framework that we call Phoenix...”

via securelistsecurelist.com
MITRE ATT&CK

Techniques & procedures

16 distinct techniques documented for this family, organized by ATT&CK tactic.

Reconnaissance

2 techniques
T1589Gather Victim Identity InformationEvidence1

Victims are first prompted to enter their phone number to check reward status or update delivery details. After submission, they are taken through a series of pages that collect full credit card details, shipping addresses, and personally identifiable information.

T1590Gather Victim Network InformationEvidence1

When a victim clicks the link inside the SMS, the phishing page first checks the visitor’s IP address and device type. Only users from the targeted country and on approved devices can see the fraudulent page.

Resource Development

3 techniques
T1584Compromise InfrastructureEvidence1

Seedworm carried out a sophisticated spear-phishing attack that used a compromised mailbox to distribute a custom backdoor known as Phoenix

T1586Compromise AccountsEvidence1

Seedworm carried out a sophisticated spear-phishing attack that used a compromised mailbox to distribute a custom backdoor known as Phoenix.

T1586.002Email AccountsEvidence1

“used a compromised mailbox to distribute a custom backdoor known as Phoenix…”

Initial Access

3 techniques
T1189Drive-by CompromiseEvidence2

Dmitry “Paunch” Fedotov used his Blackhole exploit kit to spread multiple forms of malware internationally... The exploit kits Blackhole, Phoenix, and Nuclear have all come and gone, championed today by Rig, Magnitude, and Grandsoft.

T1566PhishingEvidence1

Phishing-as-a-Service, or PhaaS, has become one of the fastest-growing threats in the cybercrime world. Instead of building tools from scratch, cybercriminals now rent ready-made phishing kits that come with pre-built templates, real-time dashboards, and automated victim tracking.

T1566.001Spearphishing AttachmentEvidence4

Group-IB said samples of MuddyWater malicious documents obtained from VirusTotal feature decoy content and embedded VBA macros designed to install the Phoenix backdoor.

Execution

3 techniques
T1059.005Visual BasicEvidence1

Group-IB said samples of MuddyWater malicious documents obtained from VirusTotal feature decoy content and embedded VBA macros designed to install the Phoenix backdoor.

T1203Exploitation for Client ExecutionEvidence1

The document repeatedly lists exploit kits alongside client-side CVEs such as CVE-2013-2551, CVE-2013-0634, CVE-2013-0422, CVE-2012-0507, CVE-2011-3544, CVE-2010-0188, and many others affecting Java, Flash, Internet Explorer, Adobe Reader, QuickTime, and Windows Media Player.

T1204.002Malicious FileEvidence1

Initial Access: Spear-phishing with malicious Word docs/VBA macros (T1566.001), macro execution (T1204.002).

Persistence

1 technique
T1543Create or Modify System ProcessEvidence1

Groups such as Seedworm have used custom backdoors—such as the Phoenix malware—to maintain long-term access even after initial vulnerabilities are patched. These tools are designed for persistent espionage, allowing attackers to return to compromised environments months or even years later.

Privilege Escalation

1 technique
T1543Create or Modify System ProcessEvidence1

Groups such as Seedworm have used custom backdoors—such as the Phoenix malware—to maintain long-term access even after initial vulnerabilities are patched. These tools are designed for persistent espionage, allowing attackers to return to compromised environments months or even years later.

Stealth

2 techniques
T1036MasqueradingEvidence1

The phishing pages are crafted to closely mimic official websites of well-known brands with matching logos, layouts, and wording.

T1497.001System ChecksEvidence1

When a victim clicks the link inside the SMS, the phishing page first checks the visitor’s IP address and device type. Only users from the targeted country and on approved devices can see the fraudulent page. Everyone else is silently redirected to an error page or a default system redirect, effectively hiding the infrastructure from security researchers.

Discovery

1 technique
T1497.001System ChecksEvidence1

When a victim clicks the link inside the SMS, the phishing page first checks the visitor’s IP address and device type. Only users from the targeted country and on approved devices can see the fraudulent page. Everyone else is silently redirected to an error page or a default system redirect, effectively hiding the infrastructure from security researchers.

Lateral Movement

1 technique
T1021Remote ServicesEvidence1

“PDQ remote access tool… used for remote access and persistence… Use of the remote desktop tools AnyDesk and ScreenConnect”

Command and Control

1 technique
T1071Application Layer ProtocolEvidence1

“The command & control (C&C) server also reportedly hosted the PDQ remote access tool…”

INDICATORS OF COMPROMISE

IOCs tracked for this family

1 indicator attributed across vendor reports, sandbox runs, and researcher write-ups. Full values are available in Mallory.

View more in app
Other
1 tracked

Other indicator types observed in public reporting.

TypeValueLatest sighting
uri●●●●●●●●●●●●View more in app2 years ago
What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets match these IOCs, which detections are missing, which campaigns to expect next, and what to do in the next 30 minutes.
IOC matching1

Match every observed IP, domain, and hash against your live telemetry.

Threat actor attribution2

Named campaigns wielding this family, with evidence pinned to each claim.

Exploited vulnerabilities

CVEs this family uses for access and lateral movement.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

MITRE ATT&CK mapping16

Every documented technique, ranked by evidence weight.

Researcher chatter

Reddit, Mastodon, and CTI community discussion around this family.