Gozi

Category: banking_trojan · Aliases: Gozi, ISFB, Ursnif, Trojan.Gozi, Win32/Gozi, Gozi-ISFB · Sample count (EMBER 2018): 113 · Enrichment: curated_sourced · Updated: 2026-10-14
Category: Banking_TrojanStatus: Automated SignaturePlatform: WINDOWS, X86, X64Stage: Initial-Access, Execution, Persistence, Credential-Access, Collection, ExfiltrationFirst seen: 2007Actor: Nikita KuzminActor: Deniss CalovskisActor: ISFB Operators ↗Industry: banking, financial_services, fintech, corporate_accountingMotivation: Financial Theft & Commercial Banking Wire Fraud🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows Server 2022
Executive Summary
Trojan:Win32/Gozi (also universally tracked as ISFB and the Ursnif family tree) is one of the most historically significant, resilient banking trojans in computer history.

Table of Contents

Overview

Trojan:Win32/Gozi (also universally tracked as ISFB and the Ursnif family tree) is one of the most historically significant, resilient banking trojans in computer history. First authored around 2007 by Russian national Nikita Kuzmin, Gozi was specifically designed to intercept online banking credentials, digital certificates, and wire transfer credentials from commercial banks. In 2010, Kuzmin was arrested in the United States and subsequently pleaded guilty in the Southern District of New York (SDNY), while co-conspirators Deniss Calovskis ('Miami') of Latvia and Mihail Sevrovs of Romania were arrested and extradited. Following Kuzmin's arrest, the complete Gozi source code leaked online around 2010, leading to a prolific ecosystem of independent criminal forks including ISFB v2/v3, Dreambot, IcedID, and GozNym. Gozi employs advanced API hooking in explorer.exe and browser processes (Internet Explorer, Firefox, Chrome), utilizing Tor-based or encrypted TLS C2 infrastructure with dynamic domain generation algorithms (DGA) to exfiltrate keystrokes, clipboard contents, and intercepted banking session cookies.

Known aliases

Threat reports may refer to this family under multiple names:

Threat Actor Attribution

Attribution is probabilistic, not a science. Each link below states its confidence level and the evidence behind it.

→ Explore all Threat Actor & APT Campaign Profiles

Family Pedigree & Lineage

Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:

Known Derivatives & Downstream Variants: Gozi V1 (2007) · Isfb V2.X (Leaked Code) · Dreambot · Goznym (Hybrid) · Icedid (Lineage)

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:

→ Explore the complete 226-Technique ATT&CK Threat Matrix

Tactical Mitigations

Based on the techniques used by this family, consider the following defensive strategies:

MITRE D3FEND™ Defensive Countermeasures

Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):

D3FEND IDCountermeasure NameTacticCountered ATT&CKDefensive Guidance
D3-DIADLL Injection AnalysisDetectT1055.001Monitor remote thread creation (CreateRemoteThread) and unauthorized DLL loading into core Windows processes (svchost.exe, explorer.exe).
D3-MFAMulti-factor AuthenticationHardenT1056.001Enforce FIDO2 / WebAuthn physical tokens to render keystroke-intercepted passwords useless.
D3-WAFWeb Content Filtering & InspectionFilterT1071.001Block newly registered domains (NRDs) and inspect HTTP Host and URI headers for known C2 profiles.
D3-MitBAMan-in-the-Browser AnalysisDetectT1185Deploy browser extension whitelisting and hardware-backed session binding to prevent rogue DOM and socket injection.
D3-CVHCredential Vault HardeningHardenT1555.003Enable DPAPI master key audit logging and isolate browser SQLite database files within virtualization-based security containers.
D3-FSFile Sandboxing (Attachment Detonation)IsolateT1566.001Detonate macro-enabled documents, ISOs, and password-protected archives inside an isolated hypervisor.

Exploited Vulnerabilities (CVEs)

This malware family is documented weaponizing the following common vulnerabilities and exposures:

Command & Control (C2) and Network Profile

How this family talks to its operators. C2 traffic can often identify a family even when its code and configuration are hard to analyse. Ports and patterns are historical and change between campaigns, so use them as hunting leads rather than block-only rules.

ProtocolsHTTPS, HTTP, Tor
Observed ports443, 80, 9050
Identifiable from traffic aloneMedium

Indicators of Compromise

Public indicators drawn from CISA advisories and vendor reporting. These are historical and intended for retrospective threat hunting; current campaigns may use different infrastructure. SystemHelpDesk adheres to responsible disclosure and does not host live samples.

File hashes (SHA-256, sample)

Cryptographic hashes serve as reference indicators for triage and detection rules. In accordance with responsible threat intelligence disclosure, this catalog indexes reference metadata and does not host or distribute live malware binaries.

Delivery vectors

Persistence mechanisms

SIEM / EDR Ingestion: Need these reference indicators for threat hunting?

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_GOZI_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Gozi"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "gozi" ascii wide nocase
        $s2 = "gozi" ascii wide nocase
        $s3 = "isfb" ascii wide nocase
        $s4 = "ursnif" ascii wide nocase
        $s5 = "trojan.gozi" ascii wide nocase
        $s6 = "win32/gozi" ascii wide nocase
        $s7 = "gozi-isfb" 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 - Gozi (Banking Trojan) Execution & Triage
id: 799ccdff-4802-5f81-b978-8d45641b7b30
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Gozi malware family. Detects recon staging, certutil file payload staging,
  and web-inject process proxying characteristic of banking trojan initial loaders.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/gozi
- https://malware-families-catalog.systemhelpdesk.com/defensive/banking-trojan-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.banking-trojan
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1185
- attack.t1055_001
- attack.t1555_003
- attack.t1071_001
- attack.t1566_001
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \svchost.exe
    - \explorer.exe
    - \msiexec.exe
    - \certutil.exe
    CommandLine|contains:
    - -urlcache
    - -split -f
    - ipconfig /all
    - route print
    - netstat -ano
  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_GOZI_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Gozi 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 = "gozi" 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
}
SOC & SIEM Rule Downloads: ⬇ Download YARA Rule (.yar) ⬇ Download Sigma Rule (YAML) ⬇ Download Sigma Rule (JSON) ⚙ Threat Profile API (JSON)

Containment & Response Steps

Home Users: If you suspect a malware infection on your personal device, disconnect from the internet immediately and run a full system scan with your antivirus software (see our TotalAV Antivirus & Security Support Guide). The steps below are intended for IT professionals responding to enterprise incidents.

Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.

  1. Terminate suspicious browser injection threads and isolate affected accounting endpoints.
  2. Revoke compromised digital certificates, banking cookies, and web session tokens.
  3. Deploy endpoint detection agents capable of identifying API hooks in wininet.dll and ws2_32.dll.
  4. Apply security updates for Microsoft Office equation editor vulnerability CVE-2017-11882.

What to Avoid

Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.

  1. Do not input corporate banking credentials on workstations showing unauthorized browser extensions or strange certificate warnings.
  2. Avoid opening macro-enabled Office files received from unknown or unverified vendors.
  3. Never store digital banking private keys without hardware-token protection.

References & External Analysis

Frequently Asked Questions

What is the Gozi (ISFB) banking trojan?

Gozi is a foundational banking trojan created in 2007 that steals financial credentials and digital certificates via browser API hooking.

Who created Gozi and how was he prosecuted?

Gozi was created by Russian national Nikita Kuzmin, who was arrested in 2010, pleaded guilty in US federal court (SDNY), and was ordered to pay millions in restitution.

What happened when the Gozi source code leaked?

The public leak of Gozi's source code spawned numerous independent crimeware syndicates, directly giving rise to Dreambot, IcedID, and GozNym.

How does Gozi intercept banking sessions?

Gozi hooks wininet.dll, ws2_32.dll, and browser DLLs to manipulate web pages in real time and harvest credentials before encryption.

What vulnerabilities were used to deploy Gozi?

Gozi was delivered via malicious documents exploiting CVE-2012-0158, CVE-2017-0199, and CVE-2017-11882 in Microsoft Office.

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.

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 for Businesses.

📣 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.

Need help with an active incident? Published by the SystemHelpdesk team.

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/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.