Hematite
Overview
Backdoor:Win32/Hematite is a stealthy, targeted Remote Access Trojan (RAT) often utilized in sustained espionage campaigns to establish deep persistence and exfiltrate sensitive data.
Understanding Hematite
To an end-user, Hematite operates completely invisibly. For threat intelligence analysts, Hematite represents a highly capable backdoor designed for long-term intelligence gathering. Unlike noisy, commercially available RATs, Hematite is often custom-compiled for specific targets, utilizing advanced obfuscation and encrypted C2 channels to evade detection by standard Endpoint Detection and Response (EDR) solutions.
Execution and Evasion Strategies
Hematite is typically delivered via highly tailored spearphishing campaigns containing weaponized Office documents or PDF exploits. Upon execution, it drops a malicious DLL into the <code>%SystemRoot%\System32 or %AppData% directories. It establishes persistence by registering itself as a hidden Windows Service or via DLL Search Order Hijacking against legitimate system executables. Hematite communicates with its C2 infrastructure using custom encryption over HTTPS (Port 443) to blend in with normal corporate web traffic.
Indicators of Compromise & Impact
The impact of Hematite is a total compromise of confidentiality and endpoint control. The attacker can execute arbitrary commands, steal credentials, and pivot laterally across the network. Incident responders should hunt for anomalous, persistent HTTPS connections originating from legitimate processes (like svchost.exe) to unknown or newly registered IP addresses. Memory forensics is critical to extract the decrypted Hematite payload and identify the specific C2 domains.
MITRE ATT&CK Techniques
Observed techniques used by this family, mapped to the MITRE ATT&CK framework:
| Technique | Name | Tactic |
|---|---|---|
T1055.001 | Process Injection: Dynamic-link Library Injection | Defense Evasion |
T1543.003 | Create or Modify System Process: Windows Service | Persistence |
T1573.001 | Encrypted Channel: Symmetric Cryptography | Command and Control |
T1056.001 | Input Capture: Keylogging | Collection |
T1105 | Ingress Tool Transfer | Command and Control |
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- T1056.001: Implement Endpoint Detection and Response (EDR) to monitor for suspicious API calls related to keystroke interception. Enforce Multi-Factor Authentication (MFA) to render stolen passwords useless.
- T1105: Implement network intrusion detection systems (NIDS) and host-based firewalls to block unauthorized inbound or outbound file transfers.
Generated Detections (Boilerplate)
These YARA and Sigma rules are auto-generated based on the family name and aliases. They must be heavily tuned before deployment in a production environment.
YARA Rule
rule MALWARE_WIN_HEMATITE {
meta:
description = "Detects Hematite (trojan_generic)"
author = "SystemHelpdesk Boilerplate Generator"
date = "2026-07-06"
strings:
$s1 = "hematite" ascii wide nocase
condition:
uint16(0) == 0x5a4d and any of them
}Sigma Rule
title: Suspicious Hematite Activity
id: 4b278b0860879c7c185eb860cddc4a09
status: experimental
description: Detects generic indicators of the hematite malware family.
logsource:
category: process_creation
product: windows
detection:
selection:
Image|endswith:
- '\cmd.exe'
- '\powershell.exe'
CommandLine|contains:
- "*hematite*"
condition: selection
level: mediumContainment & Response Steps
Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.
- Immediately isolate the compromised endpoint from the network to sever the attacker's interactive, remote-control session.
- Capture a full forensic memory image of the machine to extract the decrypted Hematite payload and its C2 configuration.
- Identify the specific C2 IP address and implement immediate blocks at the perimeter firewall and proxy servers.
- Perform a clean OS rebuild and force password resets for all accounts that accessed the machine, assuming total endpoint compromise.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not leave the machine connected to the network during triage; the attacker has live access and will likely destroy evidence or move laterally.
- Avoid relying solely on static signatures to detect Hematite, as it is frequently re-packed and obfuscated for each targeted campaign.
References & External Analysis
- Search "hematite" on VirusTotal (External Analysis)
Frequently Asked Questions
How do I remove the Hematite Trojan_Generic from Windows?
Manual removal of Hematite 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 Hematite a virus or a Trojan_Generic?
Hematite is classified as a Trojan_Generic. Unlike traditional viruses that infect files, modern malware like Hematite typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Hematite infection?
Symptoms of Hematite 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.
Related Families (Category: trojan_generic)
Explore other malware families in the same category:
Protect Your Network Against Trojan_Generics
Want to prevent Hematite and similar threats from compromising your organization? Read our comprehensive defensive guide: Banking Trojan Protection.
Machine-readable
Get this profile as JSON: https://jordan123234-malware-families-explorer.static.hf.space/api/hematite.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.