Hancitor

Overview

TrojanDownloader:Win32/Hancitor (also widely known as **Chanitor**) is a highly prolific and dangerous Initial Access Broker (IAB) and downloader trojan. It is infamous for facilitating massive malspam campaigns that deliver devastating secondary payloads, most notably the **Cuba Ransomware**, FickerStealer, and various banking trojans (like Zeus Panda or Ursnif). Hancitor operators specialize in compromising corporate networks and selling that access to the highest bidder.

Understanding Hancitor (Initial Access Broker)
To an end-user, a Hancitor infection usually starts with an urgent-looking email (fake invoices, DocuSign requests, or FedEx tracking). For a security team, Hancitor is a 'Level 1' emergency. If Hancitor executes, the network is on a countdown to a major ransomware deployment. Hancitor itself does very little damage; its entire purpose is to quietly establish a foothold, profile the domain (`T1082`), and pull down the 'heavy artillery'.

Execution and Evasion Mechanics
Hancitor is almost exclusively distributed via Phishing (`T1566.001`), utilizing weaponized Microsoft Word documents. When the user enables macros (`T1059.005`), the VBA code drops a malicious DLL to the disk and executes it via `rundll32.exe` (`T1218.011`), effectively bypassing application control policies. Once active in memory (`T1055`), Hancitor reaches out to hardcoded, often compromised WordPress sites acting as C2 servers (`T1102`). It communicates via HTTP POST requests containing basic system profiling data, and receives instructions to download and execute shellcode or secondary executables (`T1105`) directly into memory.

Indicators of Compromise & Impact
The impact is almost always a severe secondary infection, usually enterprise-wide ransomware. Host-based IoCs include EDR alerts for `winword.exe` spawning `rundll32.exe`, or `rundll32.exe` establishing outbound network connections. Network IoCs involve HTTP POST requests to suspicious, newly registered domains or compromised sites, often with specific URL structures associated with the Chanitor campaign.

MITRE ATT&CK Techniques

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

Tactical Mitigations

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

• T1059.005: Restrict execution of scripting languages such as PowerShell, VBScript, or Python to authorized administrators. Enforce Script Block Logging.
• T1105: Implement network intrusion detection systems (NIDS) and host-based firewalls to block unauthorized inbound or outbound file transfers.
• T1566.001: Scan email attachments for malicious macros, scripts, or suspicious archive files.

MITRE D3FEND™ Defensive Countermeasures

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

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:

rule MALWARE_WIN_HANCITOR_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Hancitor"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "hancitor" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Hancitor (Ransomware) Execution & Triage
id: 1c057cee-f5fb-5b0f-8ce7-23b6e5627f9f
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Hancitor malware family. Detects volume shadow copy deletion, boot status
  tampering, and recovery inhibition characteristic of modern ransomware operations.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/hancitor
- https://malware-families-catalog.systemhelpdesk.com/defensive/ransomware-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.ransomware
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1105
- attack.t1059_005
- attack.t1218_011
- attack.t1566_001
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \vssadmin.exe
    - \wmic.exe
    - \wbadmin.exe
    - \bcdedit.exe
    CommandLine|contains:
    - delete shadows
    - shadowcopy delete
    - resize shadowstorage
    - recoveryenabled no
    - ignoreallfailures
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: critical

rule MALWARE_WIN_HANCITOR_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Hancitor 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 = "hancitor" 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.

1. IMMEDIATELY isolate the infected endpoint from the network to prevent the deployment of Cuba ransomware or lateral movement.
2. Check all network telemetry and EDR logs to verify if Hancitor successfully downloaded and executed a secondary payload before isolation.
3. Initiate an enterprise-wide password reset for the compromised user, assuming credential dumping tools were deployed.
4. Block the identified C2 domains and IP addresses at the perimeter firewall.

What to Avoid

Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.

1. Do not treat a Hancitor alert as a simple 'commodity malware' cleanup; it is almost always the precursor to a targeted ransomware attack.
2. Avoid wiping the machine immediately; forensic analysis of the memory is crucial to identify what secondary payloads were downloaded.

References & External Analysis

• Search "hancitor" on VirusTotal (External Analysis)
• Search "hancitor" on Any.Run (Sandbox Sandbox)
• Search "hancitor" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Ransomware)

Explore other documented threats in the same operational category:

• Olympicdestroyer
• Whiteice
• Kate
• Pasta
• Graz
• Burnwoo
• Shepher
• Cfms

Machine-readable

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