MuddyWater Deploys RustyWater RAT via Spear-Phishing Campaigns Across Middle East Sectors

MuddyWater has launched a new remote access trojan (RAT) dubbed RustyWater, deploying it through targeted spear-phishing campaigns against organizations across multiple Middle Eastern sectors, according to recent threat research.

What’s happening

  • Initial access: Highly tailored phishing emails masquerade as legitimate business or government correspondence. Attachments and links are crafted to look routine, increasing open rates among regional targets.
  • Payload: RustyWater is a Rust-based RAT, a choice that helps it blend in and evade some legacy detection tooling.
  • Persistence & control: Once installed, the malware establishes persistence and communicates with command-and-control infrastructure to receive tasks and exfiltrate data.
  • Targeting: Campaigns appear focused on government, telecommunications, energy, and critical infrastructure–adjacent organizations across the Middle East.

Why Rust matters

Threat actors are increasingly turning to Rust for malware development because it:

  • Produces statically linked binaries that are harder to analyze.
  • Runs reliably across environments.
  • Can reduce signature-based detections compared to more common malware languages.

Attribution notes

MuddyWater—often assessed as an Iran-aligned espionage group—has a long track record of:

  • Regionally focused cyber-espionage.
  • Using phishing as a primary access vector.
  • Rapidly iterating tooling to bypass defenses.

RustyWater appears consistent with this pattern: lightweight, purpose-built, and designed for stealthy access rather than noisy disruption.

Defensive recommendations

  • Email security: Harden phishing defenses (attachment sandboxing, URL rewriting, DMARC/DKIM/SPF enforcement).
  • Endpoint protection: Ensure EDR rules cover Rust-compiled binaries and abnormal child-process behavior.
  • User awareness: Refresh spear-phishing training for staff handling external correspondence.
  • Network monitoring: Watch for unusual outbound connections and low-and-slow C2 traffic.
  • Patch & least privilege: Reduce post-compromise impact by limiting privileges and keeping systems current.