Luna

Malware

⚠️ Overview

Luna is a cross-platform ransomware family first documented in August 2022 by Trend Micro, written in the Rust programming language to target both Windows and Linux systems. It is attributed to the financially motivated threat group FIN12 (also tracked as UNC1878), which operates as a ransomware-as-a-service (RaaS) affiliate and has been active since at least 2020.

🔧 Technical Capabilities

Luna propagates via compromised Remote Desktop Protocol (RDP) credentials, phishing emails with malicious attachments, and exploitation of unpatched vulnerabilities in public-facing applications. Its C2 infrastructure uses encrypted HTTPS communication to exfiltrate system data and receive encryption keys. The ransomware employs ChaCha20 for file encryption combined with RSA-4096 for asymmetric key protection, enabling rapid encryption of local and network shares. Persistence is achieved through the Windows Registry (Run key) and scheduled tasks. Evasion techniques include disabling Windows Defender via reg.exe, terminating backup and database processes (e.g., VSS, SQL), and checking for sandbox or analysis environments by detecting debuggers. Luna also deletes volume shadow copies using vssadmin.exe to prevent recovery.

📜 History & Notable Incidents

The first known attack using Luna occurred in late August 2022 against a healthcare organization in the United States, followed by campaigns targeting manufacturing and government sectors in Europe and Asia. In October 2022, the FBI and CISA issued a joint advisory warning about FIN12’s use of Luna ransomware, linking it to previous TTPs associated with the Ryuk and Conti variants. No specific CVEs are tied to Luna itself, but it exploits known vulnerabilities like CVE-2021-44228 (Log4Shell) in target environments for initial access.

🔍 Detection Indicators

Behavioral indicators include mass renaming of files to append the .luna extension, creation of ransom notes named README_LUNA.txt, and execution of commands like reg add "HKCUSoftwareMicrosoftWindowsCurrentVersionRun" /v Luna /t REG_SZ /d "C:path omalware.exe". Network IOCs include connections to IP addresses associated with known C2 servers tracked by Trend Micro (e.g., 45.155.205.xxx). File hashes are not widely published, but YARA rules are available from CrowdStrike detecting Rust-compiled binaries with embedded Luna configuration strings.

☠️ Risk & Impact

Luna encrypts critical data on both Windows and Linux servers, causing prolonged operational downtime and financial losses exceeding $1 million per incident in healthcare and industrial sectors. Data exfiltration prior to encryption has been observed, enabling double-extortion tactics where stolen data is leaked on dark web portals. The ransomware specifically targets backup files and virtual machine snapshots to maximize disruption.

🛡️ Mitigation

Defenders should implement multifactor authentication on RDP, apply patches for known vulnerabilities (e.g., Log4Shell), and maintain offline backups. Endpoint detection rules from Trend Micro and CrowdStrike flag Luna’s encryption behavior and registry modifications. The MITRE ATT&CK technique T1486 (Data Encrypted for Impact) and T1059.003 (Command and Scripting Interpreter: Windows Command Shell) are applicable. Regular audit of privileged accounts and network segmentation limit lateral movement.

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.