Hematite

Category: trojan · Aliases: Win.Virus.Hematite, Trojan.Hematite, Trojan:Win32/Hematite!rfn, Virus:Win32/Hematite.A, Win32/Hematite · Sample count (EMBER 2018): 616 · Enrichment: curated_sourced · Updated: 2026-10-14
Category: TrojanStatus: Automated SignaturePlatform: WINDOWS_PEStage: Execution, PersistenceFirst seen: 2014Actor: Unknown / CybercriminalIndustry: Global / OpportunisticMotivation: Financial Theft🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows 7
Executive Summary
Hematite (tracked across threat intelligence feeds as Win.Virus.Hematite, Trojan.Hematite, and Trojan:Win32/Hematite!rfn) is a dual-capability Windows file infector and trojan loader documented by Cisco Talos and Microsoft Defender.

Table of Contents

Overview

Hematite (tracked across threat intelligence feeds as Win.Virus.Hematite, Trojan.Hematite, and Trojan:Win32/Hematite!rfn) is a dual-capability Windows file infector and trojan loader documented by Cisco Talos and Microsoft Defender. The malware is engineered to systematically scan compromised local storage drives and mounted network shares for portable executable (.exe) files. Upon identifying candidate binaries, Hematite appends an encrypted shellcode block—typically around 3,000 bytes—to the final PE section and modifies the Optional Header's AddressOfEntryPoint to redirect initial process execution into the malicious shellcode. After running its payload in memory, Hematite jumps back to the original entry point (OEP), allowing the host program to launch normally to evade user suspicion. Beyond parasitic infection, Hematite acts as a modular stager, initiating outbound HTTP beaconing to download secondary banking trojans, information stealers, and ransomware loaders onto infected enterprise endpoints.

Known aliases

Threat reports may refer to this family under multiple names:

Family Pedigree & Lineage

Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:

Derived From / Upstream Ancestry: Win32_Pe_Infector_Engine

Known Derivatives & Downstream Variants: Hematite.A · Hematite!Rfn

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:

→ Explore the complete 226-Technique ATT&CK Threat Matrix

Tactical Mitigations

Based on the techniques used by this family, consider the following defensive strategies:

MITRE D3FEND™ Defensive Countermeasures

Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):

D3FEND IDCountermeasure NameTacticCountered ATT&CKDefensive Guidance
D3-DIADLL Injection AnalysisDetectT1055.001Monitor remote thread creation (CreateRemoteThread) and unauthorized DLL loading into core Windows processes (svchost.exe, explorer.exe).
D3-MFAMulti-factor AuthenticationHardenT1056.001Enforce FIDO2 / WebAuthn physical tokens to render keystroke-intercepted passwords useless.
D3-NTINetwork Traffic InspectionDetectT1105Inspect deep packet payloads for anomalous staging binaries and unauthorized egress protocols.
D3-SCMWindows Service Creation MonitoringDetectT1543.003Verify service binary image signatures and restrict standard users from creating or modifying service definitions.

Indicators of Compromise

Public indicators drawn from CISA advisories and vendor reporting. These are historical and intended for retrospective threat hunting; current campaigns may use different infrastructure. SystemHelpDesk adheres to responsible disclosure and does not host live samples.

File hashes (SHA-256, sample)

Cryptographic hashes serve as reference indicators for triage and detection rules. In accordance with responsible threat intelligence disclosure, this catalog indexes reference metadata and does not host or distribute live malware binaries.

Delivery vectors

Persistence mechanisms

SIEM / EDR Ingestion: Need these reference indicators for threat hunting?

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_HEMATITE_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Hematite"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "hematite" ascii wide nocase
        $s2 = "win.virus.hematite" ascii wide nocase
        $s3 = "trojan.hematite" ascii wide nocase
        $s4 = "trojan:win32/hematite!rfn" ascii wide nocase
        $s5 = "virus:win32/hematite.a" ascii wide nocase
        $s6 = "win32/hematite" 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 - Hematite (Trojan) Execution & Triage
id: d0bc5042-fd52-52c7-9267-b29d037f0060
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Hematite 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/hematite
- 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.t1055
- attack.t1574_002
- attack.t1027
- attack.t1547_001
- attack.t1082
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_HEMATITE_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Hematite 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 = "hematite" 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
}
SOC & SIEM Rule Downloads: ⬇ Download YARA Rule (.yar) ⬇ Download Sigma Rule (YAML) ⬇ Download Sigma Rule (JSON) ⚙ Threat Profile API (JSON)

Containment & Response Steps

Home Users: If you suspect a malware infection on your personal device, disconnect from the internet immediately and run a full system scan with your antivirus software (see our TotalAV Antivirus & Security Support Guide). The steps below are intended for IT professionals responding to enterprise incidents.

Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.

  1. Immediately isolate the compromised endpoint from the network to sever the attacker's interactive, remote-control session.
  2. Capture a full forensic memory image of the machine to extract the decrypted Hematite payload and its C2 configuration.
  3. Identify the specific C2 IP address and implement immediate blocks at the perimeter firewall and proxy servers.
  4. 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.

  1. Do not leave the machine connected to the network during triage; the attacker has live access and will likely destroy evidence or move laterally.
  2. Avoid relying solely on static signatures to detect Hematite, as it is frequently re-packed and obfuscated for each targeted campaign.

References & External Analysis

Frequently Asked Questions

What is Hematite malware?

Hematite is a Windows file infector and trojan loader documented by Cisco Talos and Microsoft Defender. It modifies portable executable (.exe) headers to execute malicious shellcode before passing execution back to the host program.

How does Hematite infect legitimate executable files?

Hematite appends an encrypted shellcode payload (approximately 3,000 bytes) to the final PE section of targeted .exe files and overwrites AddressOfEntryPoint to hijack process execution before restoring original entry points.

What secondary payloads are deployed by Hematite?

In addition to parasitic file infection, Hematite initiates outbound HTTP connections to download secondary cybercrime payloads, including banking trojans, information stealers, and modular droppers.

Which vulnerabilities does Hematite exploit during initial delivery?

Hematite campaigns frequently utilize weaponized office documents exploiting Microsoft Office memory corruption vulnerabilities CVE-2012-0158 and CVE-2017-11882 to trigger initial dropper execution.

How can defenders remediate a Hematite infection?

Because Hematite modifies legitimate system and application binaries, infected files must be restored from trusted backups or cleanly reinstalled, accompanied by running Windows System File Checker (SFC /scannow) and endpoint AV quarantine.

How do I remove the Hematite Trojan 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?

Hematite is classified as a Trojan. 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.

Protect Your Network Against Trojans

Want to prevent Hematite 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.

Need help with an active incident? Published by the SystemHelpdesk Threat Intelligence Team.

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/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.