{
  "family": "httpbot",
  "sample_count": 1,
  "category": "ransomware",
  "description": "Backdoor:Win32/Httpbot (or HTTP Bot) is a broad classification for botnet agents and Remote Access Trojans (RATs) that specifically utilize standard web protocols (HTTP and HTTPS) to communicate with their Command and Control (C2) servers (`T1071.001`). By disguising their malicious traffic as normal web browsing, Httpbot variants successfully bypass many traditional firewalls and basic network intrusion detection systems.<br><br><b>Understanding Httpbot (Web-Based C2)</b><br>To an end-user, the infection is entirely invisible; there are no pop-ups or signs of sluggishness. For a security team, an Httpbot detection indicates an endpoint is actively compromised and receiving instructions from an external attacker. This is a severe incident, as the bot can be instructed to download ransomware, steal data, or participate in Distributed Denial of Service (DDoS) attacks.<br><br><b>Execution and Evasion Mechanics</b><br>Httpbot typically arrives as a secondary payload dropped by a loader (like an Office macro or a drive-by download). It establishes persistence via Registry Run keys (`T1547.001`). Once active, it begins 'beaconing'—sending regular HTTP GET or POST requests to the C2 server. Attackers often format the C2 traffic to mimic legitimate APIs (e.g., sending JSON payloads, or hiding commands in base64-encoded strings within HTTP headers) (`T1027`). Modern variants almost exclusively use HTTPS, encrypting the traffic and forcing defenders to rely on SSL inspection or host-based logging to read the payload.<br><br><b>Indicators of Compromise & Impact</b><br>The impact is total loss of endpoint control. Host-based IoCs include unexpected executables running from `%AppData%` and maintaining long-running, periodic network connections. Network IoCs are critical: look for highly regular, repetitive HTTPS connections (beacons) originating from `svchost.exe` (if injected) or unknown binaries, especially to newly registered domains or IP addresses lacking a legitimate reputation.",
  "cta": "Published by the SystemHelpdesk team.",
  "aliases": [],
  "enrichment_level": "expert-seo",
  "faq": [],
  "faq_count": 0,
  "mitre_attack": [
    "T1547.001",
    "T1055",
    "T1071.001"
  ],
  "cisa_advisory": null,
  "last_updated": "2026-06-09",
  "mitre_attack_detail": [
    {
      "id": "T1071.001",
      "name": "Application Layer Protocol: Web Protocols (Using HTTP/HTTPS for Command and Control)",
      "tactic": "Command and Control"
    },
    {
      "id": "T1547.001",
      "name": "Boot or Logon Autostart Execution: Registry Run Keys (Persistence mechanism)",
      "tactic": "Persistence"
    },
    {
      "id": "T1055",
      "name": "Process Injection (Often injecting into legitimate browser processes to further mask traffic)",
      "tactic": "Defense Evasion"
    }
  ],
  "containment_steps": [
    "Isolate the endpoint immediately to cut off the attacker's control and prevent the deployment of secondary payloads.",
    "Analyze network proxy or firewall logs to identify the specific C2 domain or IP address the bot was communicating with.",
    "Block the identified C2 infrastructure enterprise-wide.",
    "Perform a full forensic review of the endpoint to determine what commands were executed while the bot was active (e.g., data exfiltration)."
  ],
  "what_to_avoid": [
    "Do not assume the network is safe just because traffic is flowing over port 443 (HTTPS); attackers leverage encryption to hide their C2 channels.",
    "Avoid leaving the machine on the network to 'monitor' the bot; the attacker could pivot laterally at any moment."
  ],
  "target_industries": [
    "Global / Opportunistic"
  ],
  "motivation": "Opportunistic",
  "threat_actors": [
    "Unknown / Cybercriminal"
  ],
  "target_geographies": [
    "Global"
  ]
}