Havex
Table of Contents
Overview
Trojan:Win32/Havex is a highly specialized, sophisticated Remote Access Trojan (RAT) famously utilized by the 'Dragonfly' (or Energetic Bear) Advanced Persistent Threat (APT) group. Havex is critical because it was specifically engineered to target Industrial Control Systems (ICS) and SCADA networks, primarily focusing on espionage within the energy and aviation sectors.
Understanding Havex (ICS/SCADA APT)
To standard enterprise users, Havex might look like a typical RAT. However, to OT (Operational Technology) security engineers, Havex represents a catastrophic breach. It was designed not just to steal office documents, but to map the internal architecture of physical control systems, potentially paving the way for physical sabotage (similar to Stuxnet).
Execution and ICS Espionage Mechanics
Initial infection was often achieved through strategic 'Watering Hole' attacks (`T1189`)—the attackers compromised legitimate websites of ICS software vendors and replaced legitimate SCADA software installers with trojanized versions (Supply Chain Compromise - `T1195.002`). Once deployed on an engineering workstation, Havex establishes persistence and communicates with its C2 server via HTTP (`T1071.001`). Crucially, Havex includes a specialized module designed to scan the local network for devices communicating via OPC (OLE for Process Control) (`T0836`), a standard protocol used in industrial automation. It harvests data from these OPC servers to build a map of the physical controllers (PLCs) running the facility.
Indicators of Compromise & Impact
The impact is extreme espionage targeting critical national infrastructure. Host-based IoCs include the presence of known Havex DLLs (often masquerading as legitimate system files) and unexpected outbound HTTP traffic from highly restricted OT networks to known C2 domains. Network IoCs within the OT environment include anomalous, unauthorized OPC network scanning (`T0846`) originating from engineering workstations, attempting to enumerate connected industrial devices.
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 |
|---|---|---|---|
T0836 | Modify Parameter (ICS specifically: OPC Network Scanning/Enumeration) | Discovery | ATT&CK ↗ |
T1195.002 | Supply Chain Compromise: Compromise Software Supply Chain (Trojanized SCADA installers) | Initial Access | ATT&CK ↗ |
T1189 | Drive-by Compromise (Watering hole attacks on vendor sites) | Initial Access | ATT&CK ↗ |
T1071.001 | Application Layer Protocol: Web Protocols (C2 communication) | 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.
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-RBI | Remote Browser Isolation | Isolate | T1189 | Execute untrusted web browsing sessions in disposable cloud containers to isolate drive-by exploits from local endpoints. |
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_HAVEX_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Havex"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "havex" 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 - Havex (Trojan) Execution & Triage
id: 11f30cff-aefd-5bc9-a006-db4efeacb75a
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Havex 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/havex
- 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.t1195_002
- attack.t1189
- attack.t0836
- attack.t1071_001
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: mediumTier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_HAVEX_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Havex 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 = "havex" 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.
- If detected in an OT/ICS environment, immediately sever the connection between the corporate IT network and the industrial control network.
- Isolate the infected engineering workstations; do not immediately reboot them, as forensic memory analysis is critical for APT attribution.
- Analyze network traffic for unauthorized OPC scanning activity to determine how far the attackers mapped the industrial process.
- Engage specialized ICS/SCADA incident response teams; standard IT remediation is insufficient and potentially dangerous in OT environments.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not apply standard IT automated remediation (like aggressive AV quarantine) to active SCADA servers, as it may crash physical industrial processes.
- Avoid assuming the attack is limited to the IT network; Havex specifically targets the bridge between IT and OT.
References & External Analysis
- Search "havex" on VirusTotal (External Analysis)
- Search "havex" on Any.Run (Sandbox Sandbox)
- Search "havex" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Havex and what threat category does it belong to?
Havex 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 Havex establish persistence and evade defensive controls?
Havex 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 Havex compromise?
Security teams responding to Havex 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 Havex?
Havex 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 Havex across enterprise endpoints?
Defenders should hunt for Havex 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 Havex Trojan from Windows?
Manual removal of Havex 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 Havex a virus or a Trojan?
Havex is classified as a Trojan. Unlike traditional viruses that infect files, modern malware like Havex typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Havex infection?
Symptoms of Havex 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 Havex 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/havex.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.