Miragefox
Table of Contents
Overview
Executive Summary
MirageFox is a highly specialized, sophisticated Remote Access Trojan (RAT) and backdoor utilized exclusively by the Chinese state-sponsored cyber-espionage group known as APT15 (also tracked as Vixen Panda or Ke3chang). It is a heavily upgraded, stealthier evolution of the group's older "Mirage" malware, designed specifically to infiltrate high-value government, diplomatic, and defense contractor networks while evading modern endpoint detection systems.Technical Architecture and Capabilities
MirageFox is engineered for prolonged, undetected presence within a compromised environment. It is typically deployed post-exploitation, after the attackers have already gained initial access via spear-phishing and established a foothold. Key technical features of the MirageFox framework include:- DLL Hijacking and Sideloading: To execute stealthily, MirageFox frequently utilizes DLL sideloading. The attackers drop a legitimate, digitally signed executable (often associated with legitimate security software or common enterprise applications) alongside a malicious DLL containing the MirageFox payload. When the legitimate executable runs, it unwittingly loads the malicious code.
- Covert C2 Communication: MirageFox employs highly customized, encrypted command-and-control (C2) communication protocols. It often communicates over HTTPS (Port 443) to blend in with normal web traffic, or utilizes DNS tunneling to bypass strict firewall outbound rules.
- Espionage Capabilities: Once active, it provides the APT operators with a full suite of espionage tools, including remote shell access, file system manipulation, credential harvesting (specifically targeting domain administrator accounts), and the ability to exfiltrate highly sensitive documents.
Threat Impact
The presence of MirageFox on a network is a definitive indicator of a targeted, state-sponsored espionage campaign. The primary objective is the theft of classified intelligence, geopolitical communications, and advanced defense blueprints, representing a critical breach of national security.Detection and Eradication
- EDR and Behavioral Analytics: Standard static antivirus signatures are useless against custom APT tools. Deploy EDR solutions tuned to detect DLL sideloading techniques (e.g., unsigned DLLs loading into signed processes) and anomalous parent-child process relationships.
- Network Traffic Analysis: Monitor edge firewalls and DNS servers for persistent, anomalous outbound connections (beaconing) to unknown IP addresses or unusually large, repetitive DNS queries indicative of tunneling.
- Complete Environment Rebuild: Because MirageFox is utilized by advanced operators who deeply embed themselves within the network infrastructure, eradication often requires a complete, coordinated rebuild of the compromised network segment from a known good baseline to ensure all persistence mechanisms are destroyed.
Known aliases
Threat reports may refer to this family under multiple names:
MITRE ATT&CK Techniques
Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:
| Technique | Name | Tactic | Official Spec |
|---|---|---|---|
T1574.002 | DLL Side-Loading | defense-evasion | ATT&CK ↗ |
T1071.004 | Application Layer Protocol: DNS (Exfiltrating stolen card data via DNS tunneling) | Command and Control | ATT&CK ↗ |
T1071.001 | Application Layer Protocol: Web Protocols (C2 Communication) | Command and Control | ATT&CK ↗ |
T1105 | Ingress Tool Transfer | Command and Control | ATT&CK ↗ |
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- T1071.001: Implement web filtering and SSL/TLS inspection to detect malicious command and control (C2) traffic hiding in HTTP/HTTPS.
- T1071.004: Monitor network traffic for anomalous application layer protocols like non-standard HTTP/S patterns or unexpected DNS requests.
- T1105: Implement network intrusion detection systems (NIDS) and host-based firewalls to block unauthorized inbound or outbound file transfers.
MITRE D3FEND™ Defensive Countermeasures
Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):
| D3FEND ID | Countermeasure Name | Tactic | Countered ATT&CK | Defensive Guidance |
|---|---|---|---|---|
D3-WAF | Web Content Filtering & Inspection | Filter | T1071.001 | Block newly registered domains (NRDs) and inspect HTTP Host and URI headers for known C2 profiles. |
D3-ALPA | Application Layer Protocol Analysis | Detect | T1071.004 | Fingerprint application traffic structures and enforce TLS inspection for external outbound sessions. |
D3-NTI | Network Traffic Inspection | Detect | T1105 | Inspect deep packet payloads for anomalous staging binaries and unauthorized egress protocols. |
Tiered Detection Rules (Cisco CAIRN Model)
Modern threat detection requires multi-layered rule engineering. We classify detections into three operational tiers based on signal fidelity:
Tier 1 Primitive Artifact Rule (Fast Triage)
Matches raw strings and file markers. Vulnerable to binary repacking and simple obfuscation.
rule MALWARE_WIN_MIRAGEFOX_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Miragefox"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "miragefox" ascii wide nocase
$s2 = "trojan.miragefox" ascii wide nocase
$s3 = "backdoor.miragefox" ascii wide nocase
$s4 = "apt15 tool" ascii wide nocase
condition:
uint16(0) == 0x5a4d and any of them
}
Tier 2 Behavioral Context Rule (Process Chains & Sigma)
Tracks parent-child process anomalies and suspicious scripting telemetry. Resilient against file renames.
title: SystemHelpDesk Detection - Miragefox (Trojan) Execution & Triage
id: 2ba0591d-7f67-5983-b7d9-db19d2ae62bd
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Miragefox malware family. Detects suspicious execution from temporary user
directories with hidden window flags and background transfer utilities.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/miragefox
- https://malware-families-catalog.systemhelpdesk.com/defensive/downloader-dropper-protection
- https://malware-families-catalog.systemhelpdesk.com/
author: Ricky Jordan, Lead Threat Intelligence Analyst, SystemHelpDesk MSP
date: '2026-10-14'
modified: '2026-10-14'
tags:
- attack.trojan
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1574_002
- attack.t1071_004
- attack.t1071_001
- attack.t1105
logsource:
category: process_creation
product: windows
detection:
selection_process:
Image|endswith:
- \cmd.exe
- \powershell.exe
- \cscript.exe
- \wscript.exe
CommandLine|contains:
- AppData\Local\Temp
- -WindowStyle Hidden
- /e:jscript
- bitsadmin /transfer
condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: medium
Tier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_MIRAGEFOX_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Miragefox tradecraft"
tier = "T3 - Attribution Fingerprint"
confidence = "High (Confirmed Family Signature)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
// Core family identifier & heuristic payload signatures
$attrib_str = "miragefox" ascii wide nocase
$pe_magic = "MZ" ascii
$net_marker = "http" ascii nocase
condition:
uint16(0) == 0x5a4d and ($attrib_str and $net_marker) and filesize < 15MB
}
Containment & Response Steps
Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.
- Sever network connectivity for the flagged endpoint to terminate persistent command-and-control (C2) communication channels and stop Miragefox from retrieving secondary stage payloads.
- Capture process memory triage to detect and terminate malicious threads injected by Miragefox into legitimate system processes such as explorer.exe or svchost.exe.
- Audit Windows Registry Run keys (HKCU\Software\Microsoft\Windows\CurrentVersion\Run) and Task Scheduler entries to locate and purge Miragefox persistence hooks.
- Deploy updated enterprise EDR detection signatures and conduct an out-of-band endpoint scan to isolate dropped binaries and staged payloads.
- Rotate all credentials, domain user passwords, and session cookies active on the system during the Miragefox execution timeframe.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not assume the incident is resolved simply because an antivirus tool removed the initial Miragefox dropper; always verify that secondary payloads and persistence hooks have been eradicated.
- Avoid logging in with Domain Admin or privileged credentials on a machine suspected of running Miragefox until memory triage is complete.
- Do not delay host isolation; automated lateral movement and credential dumping can occur within minutes of initial execution.
References & External Analysis
- Search "miragefox" on VirusTotal (External Analysis)
- Search "miragefox" on Any.Run (Sandbox Sandbox)
- Search "miragefox" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Miragefox and what threat category does it belong to?
Miragefox is classified as a Trojan. Documented across security telemetry, it is engineered to execute unauthorized operations, establish persistent footholds on target endpoints, and facilitate malicious campaigns targeting enterprise and individual environments.
How does Miragefox establish persistence and evade defensive controls?
Miragefox typically establishes persistence through registry run keys, scheduled tasks, or service installations, while evading signature-based antivirus solutions through code obfuscation, memory injection, or anti-analysis sandbox checks.
What are the essential incident response steps for mitigating a Miragefox compromise?
Security teams responding to Miragefox should immediately isolate affected endpoints from the network, perform memory triage to capture volatile forensic artifacts, audit registry and startup persistence mechanisms, revoke exposed user credentials, and restore systems from verified, clean backups.
What secondary payloads and staging behaviors are commonly associated with Trojan.MirageFox?
Trojan.MirageFox frequently operates as a loader or dropper designed to establish a foothold before downloading and executing secondary high-impact malware payloads. Depending on the threat actor's objectives, these dropped modules can range from ransomware and banking injects to modular infostealers and remote management backdoors.
How can security operations teams effectively detect and hunt for Trojan.MirageFox across enterprise endpoints?
Defenders should hunt for Trojan.MirageFox by deploying behavioral endpoint detection and response (EDR) rules that monitor suspicious process spawning (such as cmd.exe or powershell.exe spawned from office documents or temporary directories), anomalous outbound network connections from non-browser binaries, and unauthorized modifications to Windows Run keys and scheduled task registries.
How do I remove the Miragefox Trojan from Windows?
Manual removal of Miragefox is highly discouraged as it may leave persistence mechanisms intact. We recommend disconnecting the device from the internet and utilizing a professional incident response service or enterprise-grade EDR software to conduct a full forensic sweep.
Is Miragefox a virus or a Trojan?
Miragefox is classified as a Trojan. Unlike traditional viruses that infect files, modern malware like Miragefox typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Miragefox infection?
Symptoms of Miragefox can include unexpected system slowness, unauthorized outbound network traffic to unknown IP addresses, disabled security software, and suspicious background processes running from AppData or Temp directories.
Protect Your Network Against Trojans
Want to prevent Miragefox and similar threats from compromising your organization? Read our comprehensive defensive guide: Banking Trojan Protection for Businesses.
📣 Threat Intel Correction or Update?
Notice an outdated IOC, unlisted alias, or disputed attribution? Threat researchers are invited to propose an update on GitHub or contact the SystemHelpDesk research desk. All community revisions are credited in our public CHANGELOG.
Machine-readable
Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/miragefox.json
Ecosystem & Interactive Environments
This profile is part of the Malware Families Catalog, a public dataset of 2,899 malware families. The catalog is also published across our ecosystem: Hugging Face, Kaggle, Zenodo, Replit, StackBlitz, CodeSandbox, and CodePen.