Bank

Overview

Trojan:Win32/Bank (or generic 'Banker' detections) is a broad classification for highly sophisticated malware designed specifically to steal financial credentials, intercept two-factor authentication (2FA), and facilitate fraudulent wire transfers. This category includes notorious families like Zeus, Trickbot, Dridex, and IcedID. Beyond credential theft, these trojans serve as premium Initial Access Brokers (IABs), frequently selling their access to enterprise networks directly to ransomware cartels (`T1111`).

Understanding Bank Trojans
To an end-user, the infection is designed to be invisible. They may log into their bank normally, unaware that the Trojan is manipulating the web page in real-time. For a SOC, a Banking Trojan infection is a critical, Tier-1 incident. If a Banking Trojan is present on a corporate network, a major ransomware deployment is often imminent.

Execution and Fraud Mechanics
Distribution relies heavily on massive spear-phishing campaigns (`T1566.001`) using weaponized macros or ISO files. Once executing, the Trojan establishes deep persistence and injects its core modules into web browser processes (`T1055`). It uses 'Man-in-the-Browser' (MitB) techniques (`T1111`): when the user navigates to a targeted banking site, the trojan intercepts the traffic and injects fake HTML forms (asking for OTPs or credit card numbers) into the legitimate banking page. Advanced variants utilize hidden VNC modules (`T1071.001`), allowing the attacker to initiate fraudulent transfers directly from the victim's machine, bypassing geographic and device-fingerprinting fraud controls.

Indicators of Compromise & Impact
The impact is direct financial theft and extreme risk of follow-on ransomware. Host-based IoCs include EDR alerts for process hollowing (especially targeting `explorer.exe` or `svchost.exe`), unauthorized API hooking in browser processes (Chrome, Edge, Firefox), and the presence of encrypted configuration files in `%AppData%`. Network IoCs include encrypted beaconing to C2 infrastructure and the download of dynamic web-inject configuration files.

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to the 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.
• 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_BANK {
    meta:
        description = "Detects Bank (ransomware)"
        author = "SystemHelpdesk Boilerplate Generator"
        date = "2026-07-06"
    strings:
        $s1 = "bank" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

Sigma Rule

title: Suspicious Bank Activity
id: bd5af1f610a12434c9128e4a399cef8a
status: experimental
description: Detects generic indicators of the bank malware family.
logsource:
    category: process_creation
    product: windows
detection:
    selection:
        Image|endswith:
            - '\cmd.exe'
            - '\powershell.exe'
        CommandLine|contains:
            - "*bank*"
    condition: selection
level: medium

Containment & Response Steps

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

1. Isolate the infected endpoint IMMEDIATELY. Banking trojans are a primary precursor to enterprise ransomware deployment.
2. Initiate a forced password reset for ALL accounts accessed from the infected machine, especially corporate banking and VPN credentials.
3. Capture a live memory image (RAM dump) to extract the decrypted banking trojan modules, C2 lists, and targeted bank inject configurations.
4. Notify the organization's financial institution to place holds or monitoring on accounts that may have been compromised.

What to Avoid

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

1. Do not allow the user to log into ANY accounts while the machine is connected to the network, as the Man-in-the-Browser capability is active.
2. Avoid treating this as a minor malware infection; the presence of a banking trojan indicates a severe, high-tier compromise.

References & External Analysis

• Search "bank" on VirusTotal (External Analysis)

Frequently Asked Questions

Related Families (Category: ransomware)

Explore other malware families in the same category:

• Xxybsq
• Clearsearch
• Boxter
• Genericrxbw
• Refpron

Machine-readable

Get this profile as JSON: https://jordan123234-malware-families-explorer.static.hf.space/api/bank.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.