Gozi
Overview
Trojan:Win32/Gozi (also known as Ursnif or ISFB) is one of the most sophisticated, enduring, and financially devastating banking trojans in cybersecurity history.
Understanding Gozi (Ursnif)
For the general public, a Gozi infection results in emptied bank accounts and stolen identities. For cybersecurity experts, Gozi represents a masterclass in malware engineering. Its leaked source code in 2010 spawned numerous variants, making it a cornerstone of modern financial cybercrime. It is specifically designed to steal banking credentials, intercept two-factor authentication (2FA) codes, and execute fraudulent transactions via web injects.
Execution and Evasion Strategies
Gozi is typically distributed via highly targeted spearphishing campaigns containing weaponized Office documents (macros) or through exploit kits like RIG or Angler. Once executed, Gozi uses advanced evasion techniques; it often stores its configurations and payloads encrypted within the Windows Registry rather than the file system (fileless malware techniques). It achieves persistence by modifying the AppInit_DLLs registry key or utilizing COM hijacking.
Indicators of Compromise & Impact
Once active, Gozi injects its core modules into web browsers (IE, Chrome, Firefox). When a victim navigates to a targeted banking portal, Gozi uses 'web injects' to alter the HTML of the banking site on-the-fly, prompting the user for additional sensitive information (like PINs or secure tokens). Incident responders tracking Gozi should analyze memory for injected browser DLLs, hunt for anomalous outbound traffic to Fast Flux C2 networks, and monitor for hidden registry keys containing large blobs of encrypted data.
MITRE ATT&CK Techniques
Observed techniques used by this family, mapped to the MITRE ATT&CK framework:
| Technique | Name | Tactic |
|---|---|---|
T1055.001 | Process Injection: Dynamic-link Library Injection | Defense Evasion |
T1185 | Browser Session Hijacking | Collection |
T1546.015 | Event Triggered Execution: Component Object Model Hijacking | Privilege Escalation |
T1111 | Two-Factor Authentication Interception | Credential Access |
T1566.001 | Phishing: Spearphishing Attachment | Initial Access |
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- T1185: Enforce strong MFA and use browser isolation or hardened browsers for sensitive financial or administrative portals to defeat session hijacking.
- T1566.001: Scan email attachments for malicious macros, scripts, or suspicious archive files.
Generated Detections (Boilerplate)
These YARA and Sigma rules are auto-generated based on the family name and aliases. They must be heavily tuned before deployment in a production environment.
YARA Rule
rule MALWARE_WIN_GOZI {
meta:
description = "Detects Gozi (banking_trojan)"
author = "SystemHelpdesk Boilerplate Generator"
date = "2026-07-06"
strings:
$s1 = "gozi" ascii wide nocase
condition:
uint16(0) == 0x5a4d and any of them
}Sigma Rule
title: Suspicious Gozi Activity
id: 9e66b7fb7b1c14462ac41a2bd4799098
status: experimental
description: Detects generic indicators of the gozi malware family.
logsource:
category: process_creation
product: windows
detection:
selection:
Image|endswith:
- '\cmd.exe'
- '\powershell.exe'
CommandLine|contains:
- "*gozi*"
condition: selection
level: mediumContainment & Response Steps
Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.
- Immediately sever the endpoint's network connection to halt active financial theft and data exfiltration.
- Force a mandatory password reset for all financial, corporate, and personal accounts accessed from the infected host.
- Capture a forensic image of the system's RAM; memory analysis is often the only way to extract Gozi's decrypted web injects and C2 configuration.
- Perform a clean installation (reimage) of the operating system, as Gozi's deep system hooks and fileless registry persistence are extremely difficult to eradicate manually.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not attempt to remediate a Gozi infection using standard AV tools; its advanced rootkit capabilities often hide its true presence.
- Do not log into any accounts on the infected machine, as the web injects and keyloggers are highly effective at capturing real-time credentials.
References & External Analysis
- Search "gozi" on VirusTotal (External Analysis)
Frequently Asked Questions
How do I remove the Gozi Banking_Trojan from Windows?
Manual removal of Gozi 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.
Is Gozi a virus or a Banking_Trojan?
Gozi is classified as a Banking_Trojan. Unlike traditional viruses that infect files, modern malware like Gozi typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Gozi infection?
Symptoms of Gozi 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.
Related Families (Category: banking_trojan)
Explore other malware families in the same category:
Protect Your Network Against Banking_Trojans
Want to prevent Gozi and similar threats from compromising your organization? Read our comprehensive defensive guide: Banking Trojan Protection.
Machine-readable
Get this profile as JSON: https://jordan123234-malware-families-explorer.static.hf.space/api/gozi.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.