{
  "family": "hlux",
  "sample_count": 4,
  "category": "trojan",
  "description": "Trojan:Win32/Hlux (more commonly known to the security industry as the **Kelihos botnet**) was a highly sophisticated, notoriously resilient peer-to-peer (P2P) botnet. Operating for nearly a decade before its infrastructure was dismantled, Hlux/Kelihos was responsible for massive spam campaigns (billions of emails daily), stealing cryptocurrency wallets, harvesting credentials, and acting as a dropper for other malware families. Its decentralized architecture made it exceptionally difficult to take down.<br><br><b>Understanding Hlux (Kelihos) and P2P Botnets</b><br>To an end-user, a Hlux infection might go unnoticed, or result in slower internet speeds due to the background network activity. For a network administrator and law enforcement, Hlux represents a massive distributed threat. Unlike traditional botnets that rely on centralized Command and Control (C2) servers (which can be seized), Hlux nodes communicate with each other. Each infected machine acts as a router, passing encrypted instructions and spam templates between peers.<br><br><b>Execution and Decentralized Networking</b><br>Hlux was heavily distributed via drive-by downloads, exploit kits, and its own malspam campaigns (`T1566.001`). Upon execution, the payload establishes persistence (`T1547.001`) and injects its core routines into legitimate system processes (`T1055`). The critical phase is the network bootstrap: the malware uses a hardcoded list of IP addresses to contact the P2P network (`T1090`). Once connected, it downloads the latest list of active peers and receives encrypted tasks (`T1573`). These tasks included sniffing network traffic to steal FTP/email credentials (`T1040`), searching the hard drive for Bitcoin wallet files (`T1005`), and acting as an SMTP relay to blast out spam promoting pump-and-dump stock scams or pharmaceutical fraud (`T1098.002`).<br><br><b>Indicators of Compromise & Impact</b><br>The impact includes severe bandwidth consumption, IP blacklisting, and credential theft. Host-based IoCs include EDR alerts for injected processes creating massive amounts of outbound network connections to seemingly random IP addresses (other infected peers). Network IoCs are characterized by constant, encrypted UDP and TCP traffic on non-standard ports communicating with a wide variety of global IPs, rather than a single C2 domain.",
  "cta": "Published by the SystemHelpdesk team.",
  "aliases": [],
  "enrichment_level": "expert-seo",
  "faq": [
    {
      "@type": "Question",
      "name": "What is Hlux and what threat category does it belong to?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Hlux 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."
      }
    },
    {
      "@type": "Question",
      "name": "How does Hlux establish persistence and evade defensive controls?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Hlux 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 Hlux compromise?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Security teams responding to Hlux 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 secondary payloads and staging behaviors are commonly associated with Hlux?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Hlux 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."
      }
    },
    {
      "@type": "Question",
      "name": "How can security operations teams effectively detect and hunt for Hlux across enterprise endpoints?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Defenders should hunt for Hlux 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."
      }
    }
  ],
  "faq_count": 5,
  "mitre_attack": [
    "T1098.002",
    "T1573",
    "T1040",
    "T1090"
  ],
  "cisa_advisory": null,
  "last_updated": "2026-06-09",
  "mitre_attack_detail": [
    {
      "id": "T1090",
      "name": "Proxy: Peer-to-Peer Routing (P2P Botnet architecture)",
      "tactic": "Command and Control"
    },
    {
      "id": "T1098.002",
      "name": "Account Manipulation: Additional Email Delegate Permissions (Mass spamming)",
      "tactic": "Credential Access"
    },
    {
      "id": "T1040",
      "name": "Network Sniffing (Stealing credentials in transit)",
      "tactic": "Credential Access"
    },
    {
      "id": "T1573",
      "name": "Encrypted Channel (P2P communication)",
      "tactic": "Command and Control"
    }
  ],
  "containment_steps": [
    "Immediately isolate the infected endpoint from the network to stop it from participating in the P2P network and generating spam.",
    "Assume all web and FTP credentials stored on the machine have been harvested and force immediate resets.",
    "Analyze firewall logs to identify the P2P traffic patterns; block the heavily utilized non-standard ports used by the specific Kelihos variant.",
    "If cryptocurrency wallets were present on the machine, consider them compromised."
  ],
  "what_to_avoid": [
    "Do not rely solely on blocking domain names to stop Hlux; its P2P architecture relies on direct IP-to-IP communication, bypassing DNS.",
    "Avoid leaving the machine online for observation unless properly sandboxed, as it will actively contribute to global spam and DDoS campaigns."
  ],
  "target_industries": [
    "Global / Opportunistic"
  ],
  "motivation": "Opportunistic",
  "threat_actors": [
    "Unknown / Cybercriminal"
  ],
  "target_geographies": [
    "Global"
  ],
  "attack_stage": [
    "execution",
    "persistence"
  ],
  "ecosystem": [
    "windows_pe"
  ],
  "is_emerging": false,
  "target_platforms": [
    "Windows 11",
    "Windows 10",
    "Windows 7"
  ]
}