MLTBackdoor
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.
Techniques & procedures
12 distinct techniques documented for this family, organized by ATT&CK tactic.
Execution
1 technique
Execution
Stealth
7 techniques
Stealth
MLTBackdoor hinders analysis by using indirect system calls and API hashing, along with different obfuscation methods applied at compilation time using an LLVM-based obfuscator.
The Mixed Boolean-Arithmetic (MBA) obfuscation technique takes a normal arithmetic expression like x + y and rewrites it as something mathematically equivalent but much more difficult to follow.
MLTBackdoor resolves everything at runtime (Win32 APIs, system calls, and Beacon Object File symbols) using DJB2 hashing.
MLTBackdoor uses a custom encrypted binary protocol over TLS on port 443 with a fixed path ( /api/v1/telemetry ) and User-Agent ( Microsoft-Delivery-Optimization/10.1 ) to masquerade as legitimate traffic.
MLTBackdoor includes multiple anti-analysis techniques to detect debuggers and sandboxed environments, but detection does not halt execution. Instead, MLTBackdoor aggregates the results of 10 distinct checks into a bitmask and sends it as part of its initial request
Checks whether the hypervisor bit is set; if so, queries leaf 0x40000000 to get the vendor ID... Performs a minimum of 5 RDTSC + CPUID + RDTSC loops... Checks if RAM is below 2GB. Checks if the number of processors is 1. Checks whether the uptime is less than 5 minutes.
Discovery
4 techniques
Discovery
MLTBackdoor includes a small set of built-in commands: download : Grabs a file from the victim’s machine. upload : Drops a file on the victim’s machine. ls : Lists files in a directory. delete : Deletes a file or folder. rename : Renames or moves a file or folder. mkdir : Creates a new folder.
MLTBackdoor includes multiple anti-analysis techniques to detect debuggers and sandboxed environments, but detection does not halt execution. Instead, MLTBackdoor aggregates the results of 10 distinct checks into a bitmask and sends it as part of its initial request
Checks whether the hypervisor bit is set; if so, queries leaf 0x40000000 to get the vendor ID... Performs a minimum of 5 RDTSC + CPUID + RDTSC loops... Checks if RAM is below 2GB. Checks if the number of processors is 1. Checks whether the uptime is less than 5 minutes.
Command and Control
3 techniques
Command and Control
MLTBackdoor uses a custom encrypted binary protocol over TLS on port 443 with a fixed path ( /api/v1/telemetry ) and User-Agent ( Microsoft-Delivery-Optimization/10.1 ) to masquerade as legitimate traffic.
IOCs tracked for this family
3 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Full values are available in Mallory.
IPs, domains, and DNS infrastructure linked to this family.
Other indicator types observed in public reporting.
Recent activity
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
The version that knows your environment.
Match every observed IP, domain, and hash against your live telemetry.
Named campaigns wielding this family, with evidence pinned to each claim.
CVEs this family uses for access and lateral movement.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Every documented technique, ranked by evidence weight.
Reddit, Mastodon, and CTI community discussion around this family.