{
  "family": "hancitor",
  "sample_count": 3,
  "category": "ransomware",
  "description": "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.<br><br><b>Understanding Hancitor (Initial Access Broker)</b><br>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'.<br><br><b>Execution and Evasion Mechanics</b><br>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.<br><br><b>Indicators of Compromise & Impact</b><br>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.",
  "cta": "Published by the SystemHelpdesk team.",
  "aliases": [],
  "enrichment_level": "expert-seo",
  "faq": [
    {
      "@type": "Question",
      "name": "What is Hancitor and what threat category does it belong to?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Hancitor is classified as a Ransomware. 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."
      }
    },
    {
      "@type": "Question",
      "name": "How does Hancitor establish persistence and evade defensive controls?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Hancitor 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."
      }
    },
    {
      "@type": "Question",
      "name": "What are the essential incident response steps for mitigating a Hancitor compromise?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Security teams responding to Hancitor 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."
      }
    },
    {
      "@type": "Question",
      "name": "What cryptographic algorithms and file targeting techniques does Hancitor employ during execution?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Hancitor typically leverages hybrid cryptographic architectures combining symmetric stream or block ciphers (such as AES-256 or ChaCha20) for rapid file encryption with asymmetric algorithms (such as RSA-2048 or Curve25519) to securely protect the session keys. It aggressively targets sensitive file extensions including corporate documents, databases, virtual disks, and backups while systematically executing commands to delete Volume Shadow Copies (vssadmin delete shadows /all /quiet) and disable system recovery options."
      }
    },
    {
      "@type": "Question",
      "name": "Are decryptors available for Hancitor, and what is the recommended recovery procedure?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Decryption availability for Hancitor depends on whether security researchers or law enforcement (such as the No More Ransom initiative) have recovered the master private keys or discovered flaws in its key generation routines. Victims should never pay the extortion demand, as payment fuels criminal operations without guaranteeing file restoration. The recommended recovery procedure entails isolating infected hosts, conducting forensic disk imaging, identifying the root access vector, and restoring validated systems from immutable offline backups."
      }
    }
  ],
  "faq_count": 5,
  "mitre_attack": [
    "T1105",
    "T1059.005",
    "T1218.011",
    "T1566.001"
  ],
  "cisa_advisory": null,
  "last_updated": "2026-06-09",
  "mitre_attack_detail": [
    {
      "id": "T1566.001",
      "name": "Phishing: Spearphishing Attachment (Malicious Macros)",
      "tactic": "Initial Access"
    },
    {
      "id": "T1218.011",
      "name": "System Binary Proxy Execution: Rundll32",
      "tactic": "Defense Evasion"
    },
    {
      "id": "T1105",
      "name": "Ingress Tool Transfer (Downloading Ransomware/Stealers)",
      "tactic": "Command and Control"
    },
    {
      "id": "T1059.005",
      "name": "Command and Scripting Interpreter: Visual Basic (VBA)",
      "tactic": "Execution"
    }
  ],
  "containment_steps": [
    "IMMEDIATELY isolate the infected endpoint from the network to prevent the deployment of Cuba ransomware or lateral movement.",
    "Check all network telemetry and EDR logs to verify if Hancitor successfully downloaded and executed a secondary payload before isolation.",
    "Initiate an enterprise-wide password reset for the compromised user, assuming credential dumping tools were deployed.",
    "Block the identified C2 domains and IP addresses at the perimeter firewall."
  ],
  "what_to_avoid": [
    "Do not treat a Hancitor alert as a simple 'commodity malware' cleanup; it is almost always the precursor to a targeted ransomware attack.",
    "Avoid wiping the machine immediately; forensic analysis of the memory is crucial to identify what secondary payloads were downloaded."
  ],
  "target_industries": [
    "Healthcare",
    "Critical Infrastructure",
    "Enterprise"
  ],
  "motivation": "Financial Extortion",
  "threat_actors": [
    "Unknown / Cybercriminal"
  ],
  "target_geographies": [
    "Global"
  ],
  "attack_stage": [
    "defense_evasion",
    "impact"
  ],
  "ecosystem": [
    "windows_pe"
  ],
  "is_emerging": false,
  "target_platforms": [
    "Windows 11",
    "Windows 10",
    "Windows Server 2022",
    "Windows Server 2019"
  ]
}