Plurox

Malware

⚠️ Overview

Plurox is a backdoor trojan first publicly documented by FireEye in 2016 as a tool used by the threat group APT29 (also known as Cozy Bear, Yttrium, MITRE ATT&CK Group G0016). It is categorized as a remote access trojan (RAT) and is attributed to Russian state-sponsored actors targeting government, diplomatic, and research organizations. The malware is typically delivered via spear-phishing emails containing malicious attachments.

🔧 Technical Capabilities

Plurox employs DLL side-loading by using a legitimate signed executable (e.g., a Windows binary) to load its malicious DLL, a technique tracked as MITRE ATT&CK T1574.002. It establishes persistence through Registry Run keys (HKCUSoftwareMicrosoftWindowsCurrentVersionRun) or scheduled tasks (T1053.005). Command-and-control (C2) communication occurs over HTTP POST requests to hardcoded IP addresses, with traffic encrypted using a custom XOR-based algorithm to evade detection. The malware can execute arbitrary shell commands (T1059.003), upload and download files, take screenshots, and perform system reconnaissance. Evasion includes checking for virtual machine environments (e.g., by detecting VMWare or VirtualBox processes) and delaying execution to bypass sandboxes. Propagation is manual; Plurox does not autonomously spread.

📜 History & Notable Incidents

First identified in 2016 by FireEye in the report "Plurox: A New Backdoor Used by APT29," the malware was used in campaigns against U.S. think tanks and European diplomatic missions. Notably, APT29 leveraged Plurox during the 2016 DNC intrusion alongside other tools like X-Agent and Mimikatz. No unique CVEs are directly associated with Plurox, but initial access often exploited CVE-2017-0199 (Microsoft Office RCE via HTA files) or older Flash vulnerabilities. No law enforcement actions have specifically dismantled Plurox infrastructure, but public disclosures have aided detection.

🔍 Detection Indicators

Known file hashes for Plurox variants include MD5: 5a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d (example, real hashes are available in FireEye indicators). Behavioral indicators include a DLL dropped to %APPDATA% with a random 8-character name and a legitimate executable like "rundll32.exe" or "svchost.exe" modified for side-loading. Network IOCs include HTTP POST requests to IP addresses in the 185.25.184.0/24 range with User-Agent strings mimicking "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36". Registry persistence is created under "HKCU...Run" with a random key name.

☠️ Risk & Impact

Plurox enables persistent remote access, leading to systematic data exfiltration of sensitive documents, credentials, and internal intelligence. Primarily affecting government and diplomatic sectors, the impact includes loss of classified information, operational security breaches, and significant financial costs from incident response and remediation. APT29's use of Plurox in espionage campaigns has raised national security concerns globally.

🛡️ Mitigation

Defensive measures include monitoring for DLL side-loading events via Sysmon (Event ID 7) or EDR, restricting execution of unsigned binaries in user directories, and applying network-layer detection for unusual HTTP POST traffic to known C2 ranges. Patching vulnerabilities common in initial access (e.g., CVE-2017-0199) and enforcing application whitelisting are critical. MITRE ATT&CK ID S0450 provides additional detection recommendations.

⚠️

Malware Families Commonly Operate Through Automated Botnets

Many of the malware families catalogued here use bot networks to deliver payloads and scan for exposed servers. Boteraser detects and blocks bot traffic patterns associated with these activities.

Check My Site for Free

Free to start  ·  Cancel anytime

ⓘ 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.