{
  "family": "firehooker",
  "sample_count": 1,
  "category": "trojan",
  "description": "<h3>Executive Summary</h3>\nFirehooker is a highly specialized Information Stealer (Info-Stealer) designed specifically to target web browsers, with a historical focus on Mozilla Firefox (hence the name). Its primary objective is to execute a \"man-in-the-browser\" (MitB) attack by hooking into the browser's core API functions, allowing threat actors to intercept, record, and steal sensitive credentials, session tokens, and financial data in real-time as the user types them.\n\n<h3>Infection Vector and Technical Capabilities</h3>\nFirehooker is typically distributed as a secondary payload, dropped onto a system by an initial access broker, a downloader trojan, or via an exploit kit originating from a compromised website.\n\nUpon execution, Firehooker performs advanced, targeted espionage:\n<ul>\n<li><strong>Advanced API Hooking (MitB):</strong> Instead of relying on a simple, noisy global keylogger, Firehooker injects malicious DLLs directly into the active browser process (e.g., `firefox.exe`, `chrome.exe`). It hooks specific cryptographic and network APIs (like `PR_Write` or `HttpSendRequest`). This allows the malware to capture passwords and credit card numbers *before* they are encrypted via HTTPS/SSL.</li>\n<li><strong>Form Grabbing and Web Injects:</strong> Because it sits inside the browser, Firehooker can perform \"form grabbing\"—stealing data submitted in HTML forms. Advanced variants can dynamically inject malicious HTML fields into legitimate banking websites (e.g., asking for an ATM PIN) to steal additional 2FA data.</li>\n<li><strong>Data Exfiltration:</strong> All intercepted data is compiled, encrypted, and exfiltrated via HTTP POST requests to an attacker-controlled command-and-control (C2) server.</li>\n</ul>\n\n<h3>Threat Assessment</h3>\nA Firehooker infection is a critical security incident. Because it operates via API hooking within the browser, the data theft is invisible to the user; the padlock icon still shows a secure HTTPS connection. The stolen session tokens and credentials can be immediately used to execute fraudulent financial transactions or access secure corporate portals.\n\n<h3>Incident Response and Remediation</h3>\n<ul>\n<li><strong>Global Credential Reset:</strong> ALL credentials entered on the compromised machine while infected—especially banking passwords, corporate VPN logins, and webmail access—must be considered compromised and reset immediately from a *different, clean device*.</li>\n<li><strong>MFA Token Revocation:</strong> Assume session cookies were stolen. Force an immediate sign-out of all active sessions for critical web applications to invalidate the stolen tokens.</li>\n<li><strong>Endpoint Eradication:</strong> The sophisticated process injection techniques used by Firehooker necessitate a full forensic review. Re-imaging the machine from a trusted baseline is required to ensure complete eradication and that no hidden hooks remain in the system.</li>\n</ul>",
  "cta": "Published by the SystemHelpdesk team.",
  "aliases": [
    "Trojan.Firehooker",
    "PWS.Firehooker",
    "Banker.Hooker"
  ],
  "enrichment_level": "insufficient_information",
  "faq": [],
  "faq_count": 0,
  "mitre_attack": [
    "T1185",
    "T1056.001",
    "T1189",
    "T1555.003"
  ],
  "cisa_advisory": null,
  "last_updated": "2026-07-02T06:46:38Z",
  "type": "Information Stealer / Banker",
  "target_industries": [
    "Global / Opportunistic"
  ],
  "motivation": "Opportunistic",
  "threat_actors": [
    "Unknown / Cybercriminal"
  ],
  "target_geographies": [
    "Global"
  ]
}