{
  "family": "collector",
  "sample_count": 8,
  "category": "trojan",
  "description": "Spyware:Win32/Collector is a specialized Information Stealer (Infostealer) trojan designed to silently harvest and exfiltrate highly specific sets of data from infected endpoints. Unlike broad keyloggers, Collector often targets specific configuration files, proprietary databases, saved web browser credentials, and cryptocurrency wallet `.dat` files, packaging the stolen data for exfiltration.<br><br><b>Understanding the Collector Spyware</b><br>To an end-user, a Collector infection is entirely invisible. The system continues to function normally. For a security analyst, a Collector detection is a critical data breach event. The malware is designed for rapid execution; it 'smash and grabs' the targeted files and immediately exfiltrates them, often completing its objective within seconds of execution.<br><br><b>Execution and Data Harvesting Mechanics</b><br>Collector is typically distributed via weaponized phishing attachments (`T1566.001`) or as a secondary payload dropped by an Initial Access Broker. Upon execution (`T1204.002`), it attempts to evade detection by disabling local antivirus (`T1562.001`). It systematically searches the hard drive for specific file extensions (`T1083`) or queries the SQLite databases used by Chromium and Firefox browsers to store saved passwords and cookies (`T1555.003`). It specifically targets directories known to house cryptocurrency wallets (e.g., `%AppData%\\Bitcoin`). The harvested data is compressed into an archive and exfiltrated via HTTP POST requests to a Command and Control (C2) server or a Telegram bot channel (`T1048.003`).<br><br><b>Indicators of Compromise & Impact</b><br>The primary impact is the catastrophic loss of user credentials, sensitive proprietary data, and potentially financial theft (if crypto wallets are stolen). EDR logs will flag an anomalous process accessing multiple database files (`Login Data`, `Cookies`, `wallet.dat`) in rapid succession. Network IoCs include a brief burst of outbound HTTP/HTTPS traffic containing an encrypted archive immediately following the execution of an unknown binary.",
  "cta": "Published by the SystemHelpdesk team.",
  "aliases": [],
  "enrichment_level": "expert-seo",
  "faq": [
    {
      "@type": "Question",
      "name": "What is Collector and what threat category does it belong to?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Collector 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 Collector establish persistence and evade defensive controls?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Collector 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 Collector compromise?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Security teams responding to Collector 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 Collector?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Collector 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 Collector across enterprise endpoints?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Defenders should hunt for Collector 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": [
    "T1562.001",
    "T1083",
    "T1048.003",
    "T1555.003"
  ],
  "cisa_advisory": null,
  "last_updated": "2026-06-09",
  "mitre_attack_detail": [
    {
      "id": "T1555.003",
      "name": "Credentials from Password Stores: Credentials from Web Browsers",
      "tactic": "Credential Access"
    },
    {
      "id": "T1083",
      "name": "File and Directory Discovery (Searching for targeted files)",
      "tactic": "Discovery"
    },
    {
      "id": "T1048.003",
      "name": "Exfiltration Over Alternative Protocol (Telegram API / HTTP POST)",
      "tactic": "Exfiltration"
    },
    {
      "id": "T1562.001",
      "name": "Impair Defenses: Disable or Modify Tools",
      "tactic": "Defense Evasion"
    }
  ],
  "containment_steps": [
    "Instantly isolate the endpoint, though the exfiltration of credentials has likely already occurred within seconds of execution.",
    "Enforce a mandatory, immediate password reset for *every* account the user has saved in their browser.",
    "Revoke all active web session cookies for the user to prevent attackers from bypassing Multi-Factor Authentication (MFA) using stolen cookies.",
    "If cryptocurrency wallets were present on the machine, assume they are compromised and move funds to a secure wallet immediately."
  ],
  "what_to_avoid": [
    "Do not assume MFA will protect the compromised accounts; infostealers specifically target session cookies to perform 'Pass-the-Cookie' attacks.",
    "Avoid focusing solely on malware removal; the primary incident response must focus on credential revocation and monitoring for anomalous logins."
  ],
  "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"
  ]
}