Finfish
Table of Contents
Overview
Spyware:Win32/Finfish (also known as FinFisher or FinSpy) is an incredibly sophisticated, commercial-grade spyware suite. Developed by the German company Gamma International (and its UK affiliate Gamma Group), FinFisher is marketed and sold exclusively as 'lawful interception' software to law enforcement and intelligence agencies worldwide. However, it has been widely documented by human rights organizations (like Citizen Lab) being deployed by oppressive regimes against journalists, political dissidents, and activists.
Understanding Finfish (Commercial Spyware)
To a victim, a FinFisher infection is entirely invisible. The spyware is designed for absolute stealth and total device compromise. For a security analyst, FinFisher is the apex predator of endpoint surveillance. It grants the operator complete, undetectable control over the infected machine, allowing for real-time monitoring of all communications, even those utilizing end-to-end encryption, by capturing the data *before* it is encrypted on the device.
Execution and Surveillance Capabilities
FinFisher is deployed through highly targeted means, including spear-phishing with zero-day exploits (`T1190`), physical access (USB drops - `T1091`), or even ISP-level MitM attacks (FinFly ISP). Once executed, it employs aggressive anti-analysis and rootkit techniques (`T1014`) to hide its processes, files, and network connections. Its surveillance modules are vast: it can silently activate the webcam and microphone (`T1125`), log all keystrokes (`T1056.001`), exfiltrate files (`T1041`), and hook into VoIP applications (like Skype or WhatsApp) to record live conversations (`T1056.002`). It communicates with its C2 servers using custom, heavily obfuscated protocols designed to blend in with normal web traffic.
Indicators of Compromise & Impact
The impact is total loss of privacy and severe compromise of sensitive data. Because FinFisher is designed to evade top-tier AV and EDR solutions, host-based IoCs are extremely difficult to find. Advanced memory forensics (`T1055`) and deep packet inspection of network traffic are usually required. Historically, researchers have identified specific strings, mutexes, and highly obfuscated virtualized code blocks (like those produced by the 'VMProtect' packer) associated with FinFisher droppers.
MITRE ATT&CK Techniques
Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- T1056.001: Implement Endpoint Detection and Response (EDR) to monitor for suspicious API calls related to keystroke interception. Enforce Multi-Factor Authentication (MFA) to render stolen passwords useless.
- T1056.002: Monitor for unauthorized keylogging, screen capturing, or web browser API hooking. Deploy EDR to detect API hooking.
- T1125: Restrict access to local camera or microphone APIs. Utilize endpoint protection that monitors hardware access.
MITRE D3FEND™ Defensive Countermeasures
Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):
| D3FEND ID | Countermeasure Name | Tactic | Countered ATT&CK | Defensive Guidance |
|---|---|---|---|---|
D3-KMC | Kernel Memory Integrity Checking | Harden | T1014 | Enable Hypervisor-Protected Code Integrity (HVCI) and UEFI Secure Boot to prevent unsigned kernel driver execution. |
D3-MFA | Multi-factor Authentication | Harden | T1056.001 | Enforce FIDO2 / WebAuthn physical tokens to render keystroke-intercepted passwords useless. |
D3-AHC | API Hook Detection | Detect | T1056.002 | Deploy kernel and userland EDR drivers to monitor SetWindowsHookEx and low-level keyboard hooks. |
D3-HAC | Hardware Device Access Control | Isolate | T1125 | Enforce Group Policy hardware access restrictions on integrated webcams and microphones. |
Tiered Detection Rules (Cisco CAIRN Model)
Modern threat detection requires multi-layered rule engineering. We classify detections into three operational tiers based on signal fidelity:
Tier 1 Primitive Artifact Rule (Fast Triage)
Matches raw strings and file markers. Vulnerable to binary repacking and simple obfuscation.
rule MALWARE_WIN_FINFISH_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Finfish"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "finfish" ascii wide nocase
condition:
uint16(0) == 0x5a4d and any of them
}
Tier 2 Behavioral Context Rule (Process Chains & Sigma)
Tracks parent-child process anomalies and suspicious scripting telemetry. Resilient against file renames.
title: SystemHelpDesk Detection - Finfish (Advanced Threat) Execution & Triage
id: a76bc848-6861-535d-9fef-5fcfcef6c748
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Finfish malware family. Detects proxy execution, reflective DLL loading,
and remote command injection associated with modular enterprise backdoors.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/finfish
- https://malware-families-catalog.systemhelpdesk.com/defensive/backdoor-rat-protection
- https://malware-families-catalog.systemhelpdesk.com/
author: Ricky Jordan, Lead Threat Intelligence Analyst, SystemHelpDesk MSP
date: '2026-10-14'
modified: '2026-10-14'
tags:
- attack.advanced-threat
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1014
- attack.t1125
- attack.t1056_002
- attack.t1056_001
logsource:
category: process_creation
product: windows
detection:
selection_process:
Image|endswith:
- \powershell.exe
- \cmd.exe
- \rundll32.exe
- \regsvr32.exe
CommandLine|contains:
- DownloadString
- IEX(
- '/s /n /u /i:'
- sc create
- start-process
condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: high
Tier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_FINFISH_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Finfish tradecraft"
tier = "T3 - Attribution Fingerprint"
confidence = "High (Confirmed Family Signature)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
// Core family identifier & heuristic payload signatures
$attrib_str = "finfish" ascii wide nocase
$pe_magic = "MZ" ascii
$net_marker = "http" ascii nocase
condition:
uint16(0) == 0x5a4d and ($attrib_str and $net_marker) and filesize < 15MB
}
Containment & Response Steps
Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.
- If state-sponsored spyware is suspected, immediately isolate the device but DO NOT power it off, as volatile memory forensics are critical.
- Engage a specialized incident response firm with experience in analyzing APT (Advanced Persistent Threat) and commercial spyware toolsets.
- Perform a full forensic image of the RAM and the hard drive for offline analysis.
- Consider the compromised device completely untrustworthy; standard reimaging may not be sufficient if firmware-level persistence was achieved.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not alert the user of the suspected infection via the compromised device (e.g., via email or chat), as the attacker is actively monitoring all communications.
- Avoid relying on standard endpoint antivirus to detect or remove FinFisher, as it is explicitly engineered to bypass these protections.
References & External Analysis
- Search "finfish" on VirusTotal (External Analysis)
- Search "finfish" on Any.Run (Sandbox Sandbox)
- Search "finfish" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Finfish and what threat category does it belong to?
Finfish is classified as a Advanced Threat. 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.
How does Finfish establish persistence and evade defensive controls?
Finfish 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.
What are the essential incident response steps for mitigating a Finfish compromise?
Security teams responding to Finfish 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.
What lateral movement and credential access tactics does Finfish leverage in enterprise intrusions?
Finfish frequently utilizes privileged account harvesting techniques such as LSASS memory dumping, Kerberoasting, and token impersonation to escalate privileges. Once administrative credentials are acquired, it pivots across the victim network utilizing living-off-the-land binaries (LOLBins) such as WMI, PowerShell remoting, and PsExec, or abuses remote desktop protocols (RDP) to reach critical internal repositories and domain controllers.
How does Finfish maintain covert communications and evade perimeter network monitoring?
Finfish often relies on multi-stage command and control (C2) architectures utilizing encrypted protocols over standard web ports (HTTPS/443 or DNS tunneling) to blend in with legitimate enterprise network traffic. Many variants incorporate proxy networks, domain fronting, or cloud services (such as Microsoft Graph API, Google Drive, or Telegram) to masquerade C2 channels, bypassing traditional signature-based egress filtering.
How do I remove Finfish from Windows?
Manual removal of Finfish is highly discouraged as it may leave persistence mechanisms intact. We recommend disconnecting the device from the internet and utilizing a professional incident response service or enterprise-grade EDR software to conduct a full forensic sweep.
What are the main symptoms of a Finfish infection?
Symptoms of Finfish can include unexpected system slowness, unauthorized outbound network traffic to unknown IP addresses, disabled security software, and suspicious background processes running from AppData or Temp directories.
Protect Your Network Against Advanced_Threats
Want to prevent Finfish and similar threats from compromising your organization? Read our comprehensive defensive guide: Think You've Been Hacked? What To Do First.
📣 Threat Intel Correction or Update?
Notice an outdated IOC, unlisted alias, or disputed attribution? Threat researchers are invited to propose an update on GitHub or contact the SystemHelpDesk research desk. All community revisions are credited in our public CHANGELOG.
Machine-readable
Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/finfish.json
Ecosystem & Interactive Environments
This profile is part of the Malware Families Catalog, a public dataset of 2,899 malware families. The catalog is also published across our ecosystem: Hugging Face, Kaggle, Zenodo, Replit, StackBlitz, CodeSandbox, and CodePen.