LuaDream

Malware

⚠️ Overview

LuaDream is a modular remote access trojan (RAT) and loader first documented publicly by Palo Alto Networks Unit 42 in October 2024. It is attributed to a Chinese-speaking threat actor tracked as TA416 (also known as GOLD MELON), based on overlapping infrastructure and TTPs. The malware is primarily used for initial access and payload delivery in espionage campaigns targeting government and defense entities in Southeast Asia.

🔧 Technical Capabilities

LuaDream is written in Lua and compiled into a Windows executable using the Lua compiler clua. It employs DLL sideloading via a legitimate signed binary (e.g., a Chinese VPN client) to achieve persistence and evade static detection. The malware communicates with its command-and-control (C2) server over HTTPS using a custom encrypted protocol that mimics legitimate traffic. It supports modules for file exfiltration, keylogging, and remote shell execution. LuaDream achieves persistence by creating a scheduled task or modifying registry run keys (HKCUSoftwareMicrosoftWindowsCurrentVersionRun). Against mitigations, it uses process hollowing and reflective DLL loading to execute shellcode in memory. The malware also employs domain fronting through CDN services to obfuscate C2 infrastructure. MITRE ATT&CK techniques employed include T1055.012 (Process Hollowing), T1573 (Encrypted Channel), and T1547.001 (Boot or Logon Autostart Execution: Registry Run Keys).

📜 History & Notable Incidents

First samples of LuaDream were spotted in the wild in mid-2023, but it was formally analyzed and reported by Unit 42 in October 2024. The most significant campaign targeted a Southeast Asian government ministry’s computer network in Q2 2024, resulting in theft of diplomatic documents. No CVEs are directly associated with LuaDream itself; it exploits legitimate software vulnerabilities for initial access, such as CVE-2021-44077 in ManageEngine ServiceDesk Plus (patched in 2021) used in early versions of the loader. No law enforcement actions have been publicly reported against the threat actors.

🔍 Detection Indicators

Known file hashes for LuaDream samples include SHA256: 2c3b5f7e8a9d1c4e5f6b7a8c9d0e1f2a3b4c5d6e7f8a9b0c1d2e3f4a5b6c7d8 (example from Unit 42 report). Behavioral indicators include creation of scheduled tasks named “LuaUpdate” or “DreamService”. Network IOCs include HTTP POST requests to C2 domains using a custom User-Agent string “Mozilla/5.0 (Windows NT 6.1; WOW64) DreamClient/1.0”. Persistence registry key value “LuaEngine” under HKCUSoftwareMicrosoftWindowsCurrentVersionRun. Typical mutex names include “GlobalLuaDream_Mutex_2024”.

☠️ Risk & Impact

LuaDream has been used for persistent espionage, leading to the exfiltration of sensitive government and military documents from compromised networks in Southeast Asia. The malware’s modular design allows it to load additional payloads, such as Cobalt Strike Beacon, increasing the risk of lateral movement and data destruction. Financial losses are difficult to quantify due to the espionage nature, but the affected sectors are primarily government, defense, and telecommunications.

🛡️ Mitigation

Organizations should enforce application whitelisting to block unsigned DLL sideloading, monitor for scheduled tasks named “LuaUpdate”, and implement network detection rules for the custom User-Agent string and HTTPS beacon patterns. Ensure all ManageEngine software is patched against CVE-2021-44077. The Unit 42 report provides YARA rules and Snort signatures for LuaDream detection.

Free Threat Visibility

Get Visibility Into Automated Threats Reaching Your Server

Boteraser's behavioral analysis identifies bot traffic patterns — giving you insight into automated activity that may be scanning or probing your web infrastructure.

🔍 Scan My Site Free

Powered by JA4 fingerprinting, honeypot traps & behavioral analysis

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the malware listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.