{
  "family": "lolbot",
  "sample_count": 374,
  "category": "rat",
  "description": "Trojan:Win32/Lolbot is a specialized trojan family frequently associated with instant messaging disruption, banking fraud, and credential theft.<br><br><b>Understanding Lolbot</b><br>While early variants of Lolbot were known for hijacking popular instant messaging applications (like Yahoo Messenger or Skype) to spread malicious links to a victim's contact list, modern iterations are highly focused on intercepting financial transactions. For security analysts, Lolbot is a dangerous information stealer that relies on Man-in-the-Browser (MitB) or keylogging techniques to harvest sensitive data.<br><br><b>Execution and Evasion Strategies</b><br>Lolbot typically gains initial access through spearphishing campaigns containing weaponized macro documents or malicious ZIP archives. Once executed, it injects its malicious DLLs into web browser processes (such as <code>chrome.exe</code> or <code>iexplore.exe</code>) and messaging applications. This allows the malware to hook API calls, thereby intercepting credentials before they are encrypted and sent over the network. To evade Endpoint Detection and Response (EDR) solutions, Lolbot employs heavy obfuscation and often checks for the presence of virtual machines (anti-analysis techniques).<br><br><b>Indicators of Compromise (IoCs)</b><br>Incident responders investigating Lolbot should search for unauthorized DLL injections in browser memory spaces, unexpected modifications to local proxy settings, and anomalous outbound HTTPS traffic to unknown command-and-control (C2) domains. The presence of dropped `.dat` or `.log` files in the user's `AppData` directory often indicates active keylogging.",
  "cta": "Published by the SystemHelpdesk team.",
  "aliases": [],
  "enrichment_level": "expert-seo",
  "faq": [],
  "faq_count": 0,
  "mitre_attack": [
    "T1566.001",
    "T1056.001",
    "T1185",
    "T1497.001",
    "T1055.001"
  ],
  "cisa_advisory": null,
  "last_updated": "2026-06-09",
  "mitre_attack_detail": [
    {
      "id": "T1566.001",
      "name": "Phishing: Spearphishing Attachment",
      "tactic": "Initial Access"
    },
    {
      "id": "T1055.001",
      "name": "Process Injection: Dynamic-link Library Injection",
      "tactic": "Defense Evasion"
    },
    {
      "id": "T1056.001",
      "name": "Input Capture: Keylogging",
      "tactic": "Collection"
    },
    {
      "id": "T1185",
      "name": "Browser Session Hijacking",
      "tactic": "Collection"
    },
    {
      "id": "T1497.001",
      "name": "Virtualization/Sandbox Evasion: System Checks",
      "tactic": "Defense Evasion"
    }
  ],
  "containment_steps": [
    "Immediately disconnect the compromised asset from the network to halt the exfiltration of stolen credentials.",
    "Force a global password reset for all user accounts that were accessed from the infected endpoint, prioritizing financial and corporate accounts.",
    "Utilize memory forensics tools (like Volatility) to identify and dump the injected malicious DLLs from browser processes.",
    "Audit the system's local proxy and DNS settings, ensuring they have not been modified to intercept secure web traffic."
  ],
  "what_to_avoid": [
    "Do not log into any administrative portals or sensitive accounts from the infected machine, as the keylogger will capture these new credentials.",
    "Do not blindly trust basic AV scans, as Lolbot's process injection often allows it to bypass static signature checks."
  ],
  "target_industries": [
    "Global / Opportunistic"
  ],
  "motivation": "Opportunistic",
  "threat_actors": [
    "Unknown / Cybercriminal"
  ],
  "target_geographies": [
    "Global"
  ]
}