Skip to main content
Mallory
MalwareUsed by 1 actor

BugSleep

BugSleep is a custom backdoor associated with the Iranian MOIS-linked threat actor MuddyWater, also tracked as Boggy Serpens, Seedworm, Static Kitten, Mango Sandstorm, and TA450. Public reporting places its deployment beginning in May 2024, with campaigns primarily targeting Israeli organizations, though related MuddyWater activity also affected entities in Saudi Arabia, Turkey, Azerbaijan, India, Portugal, Egypt, and broader MENA diplomatic, maritime, financial, telecommunications, government, aviation, and energy sectors. BugSleep has also been reported under the alias MuddyRot.

BugSleep is described as a backdoor used to execute commands and facilitate file transfers between compromised hosts and command-and-control servers. Reporting characterizes it as under active development, with multiple versions and rapid iteration. Sources describe it as Python-based in some reporting, while Check Point’s detailed July 2024 analysis identified it as a custom C/C++ backdoor; the content also notes a Phoenix delivery lineage that deployed BugSleep via malicious macro-enabled Office documents and a Phoenix injector.

Observed infection chains rely heavily on spear-phishing. MuddyWater used compromised organizational email accounts and trusted internal mailboxes to bypass filtering, then delivered malicious Office documents that instructed users to enable macros. When enabled, VBA macros silently dropped payloads and displayed decoy content. Related campaigns also abused Egnyte subdomains and other file-sharing services for payload delivery. In some campaigns, the same lure themes were reused across regions, with Saudi Arabia receiving Atera RMM payloads while Israeli targets received BugSleep.

Documented BugSleep functionality includes command execution, file exfiltration, writing file contents, interactive cmd execution via pipes until a terminate command, updating sleep/timeout values, stopping communications, and creating or removing persistence. It sends an initial victim identifier composed of computer name and username. Communications and configuration are encrypted with a byte-shift scheme, and C2 traffic uses a [size_of_data][data] format. BugSleep decrypts embedded configuration containing the C2 IP address and port.

Anti-analysis and persistence features are also documented. BugSleep uses repeated Sleep API calls to delay execution, creates mutexes including "PackageManager" and "DocumentUpdater," and commonly establishes persistence through a scheduled task named after the mutex with the comment "sample comment," configured to run every 30 minutes daily. One version enabled ProcessSignaturePolicy (MicrosoftSignedOnly) and ProcessDynamicCodePolicy (ProhibitDynamicCode) to hinder DLL injection and dynamic code or userland hooking by EDR.

A related loader was observed decrypting shellcode and injecting BugSleep in memory using WriteProcessMemory and CreateRemoteThread into processes including msedge.exe, opera.exe, chrome.exe, anydesk.exe, "Ondedrive.exe," and powershell.exe. Reporting also ties BugSleep to the Phoenix malware lineage, with forensic analysis showing shared development artifacts between Phoenix-delivered BugSleep and other MuddyWater implants. Additional reported indicators and characteristics include TCP port 443, the mutex "DocumentUpdater," identical string obfuscation logic across samples, and the novaservice.exe path shared with related malware tracks.

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

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

View more details
MuddyWater

Recent attacks have also involved a variety of more sophisticated malware, including the BugSleep backdoor to facilitate file transfers between infected endpoints and C2 servers, a Phoenix injector for deploying BugSleep, the Fooder malware loader and an advanced backdoor tracked as Stealth Cache.

via bank info securitybankinfosecurity.com
MITRE ATT&CK

Techniques & procedures

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

Initial Access

3 techniques
T1566PhishingEvidence2

From February to July 2024, more than 50 phishing emails were observed across 10+ sectors with hundreds of recipients.

T1566.001Spearphishing AttachmentEvidence1

"Email contains a PDF attachment with an embedded link."

T1566.002Spearphishing LinkEvidence1

"Email includes a direct link to an Egnyte subdomain." | "The threat actors consistently use phishing campaigns sent from compromised organizational email accounts."

Execution

4 techniques
T1053.005Scheduled TaskEvidence1

"the malware then creates a scheduled task... The scheduled task, which ensures persistence for BugSleep, runs the malware and is triggered every 30 minutes"

T1059.001PowerShellEvidence2

“use of command and scripting interpreters (T1059) like PowerShell (T1059.001)” and repeated PowerShell-based backdoors (e.g., TameCat) and command lines across groups.

T1059.003Windows Command ShellEvidence1

"Run commands through cmd pipe until the command ‘terminate’."

T1059.005Visual BasicEvidence1

When that happens, a VBA macro executes silently in the background, drops a payload, and then clears the blur to reveal a convincing, legitimate-looking document underneath.

Persistence

1 technique
T1053.005Scheduled TaskEvidence1

"the malware then creates a scheduled task... The scheduled task, which ensures persistence for BugSleep, runs the malware and is triggered every 30 minutes"

Privilege Escalation

2 techniques
T1053.005Scheduled TaskEvidence1

"the malware then creates a scheduled task... The scheduled task, which ensures persistence for BugSleep, runs the malware and is triggered every 30 minutes"

T1055Process InjectionEvidence1

"The loader injects a shellcode that loads BugSleep in-memory... writes the shellcode inside the process with the WriteProcessMemory API and invokes the shellcode with the CreateRemoteThread API."

Stealth

3 techniques
T1027Obfuscated Files or InformationEvidence1

"All the configurations and strings are encrypted... Every message exchanged between BugSleep and its C&C domain follows this format"

T1055Process InjectionEvidence1

"The loader injects a shellcode that loads BugSleep in-memory... writes the shellcode inside the process with the WriteProcessMemory API and invokes the shellcode with the CreateRemoteThread API."

T1497.003Time Based ChecksEvidence1

"starting with many calls to the Sleep API to evade sandboxes"

Discovery

1 technique
T1497.003Time Based ChecksEvidence1

"starting with many calls to the Sleep API to evade sandboxes"

Command and Control

4 techniques
T1071Application Layer ProtocolEvidence1

Sekoia TDR (July 2024) independently documented the same implant under the name MuddyRot, with matching characteristics: mutex “DocumentUpdater,” TCP port 443, and identical string obfuscation logic.

T1071.001Web ProtocolsEvidence1

Word lure (airline tickets, reports) -> HTTP_VIP -> AnyDesk (return to RMM abuse pattern).

T1102Web ServiceEvidence1

"MuddyWater has frequently used Egnyte subdomains... Upon opening the shared link, recipients can see the name of the purported sender"

T1105Ingress Tool TransferEvidence3

Recent attacks have also involved a variety of more sophisticated malware, including the BugSleep backdoor to facilitate file transfers between infected endpoints and C2 servers, a Phoenix injector for deploying BugSleep, the Fooder malware loader and an advanced backdoor tracked as Stealth Cache.

Exfiltration

1 technique
T1041Exfiltration Over C2 ChannelEvidence1

Recent attacks have also involved a variety of more sophisticated malware, including the BugSleep backdoor to facilitate file transfers between infected endpoints and C2 servers

INDICATORS OF COMPROMISE

IOCs tracked for this family

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

View more in app
Network
22 tracked

IPs, domains, and DNS infrastructure linked to this family.

Hashes
18 tracked

File hashes (MD5, SHA-1, SHA-256) from samples and reports.

Other
4 tracked

Other indicator types observed in public reporting.

TypeValueLatest sighting
domain●●●●●●●●●●●●View more in app2 months ago
hash.sha256●●●●●●●●●●●●View more in app3 months ago
hash.sha256●●●●●●●●●●●●View more in app3 months ago
hash.sha256●●●●●●●●●●●●View more in app3 months ago
hash.sha256●●●●●●●●●●●●View more in app3 months ago
hash.sha256●●●●●●●●●●●●View more in app3 months 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 matching44

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

Threat actor attribution1

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 mapping15

Every documented technique, ranked by evidence weight.

Researcher chatter

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