Dyre

Malware

⚠️ Overview

Dyre (also known as Dyreza) is a sophisticated banking trojan first discovered in 2014 by security researchers at Malwarebytes and later analyzed by Symantec. It was developed by a Russian-speaking cybercriminal group often tracked as the Dyre Gang, and belongs to the category of financial malware that employs man-in-the-browser (MitB) attacks to steal online banking credentials. The malware was primarily distributed through spear-phishing emails with malicious attachments or links.

🔧 Technical Capabilities

Dyre targets Windows systems and uses a modular architecture with components for proxying traffic, capturing screenshots, and injecting malicious scripts into browser sessions. It performs HTTPS stripping and leverages web injections to alter bank website content in real time, tricking users into submitting sensitive data. The botnet uses a peer-to-peer (P2P) communication model alongside multiple command-and-control (C2) servers, some hosted on Tor hidden services for resilience. Persistence is achieved by creating a scheduled task or adding a registry run key; it also employs a domain generation algorithm (DGA) to evade sinkholing. Evasion techniques include anti-debugging, sandbox detection via CPU checks, and encryption of configuration files with a custom algorithm. According to MITRE ATT&CK, Dyre uses T1056.001 (Input Capture) for credential theft and T1573.001 (Encrypted Channel via Symmetric Cryptography).

📜 History & Notable Incidents

Dyre first appeared in mid-2014, with early campaigns targeting major US financial institutions such as Bank of America, Citigroup, and JPMorgan Chase. In 2015, the malware infected over 20,000 machines globally, leading to estimated losses exceeding $100 million; notable victims included small-to-medium businesses and municipal governments. Law enforcement action by the FBI and international partners in November 2015 disrupted the botnet by seizing C2 domains, but variants resurged in 2016 using the same codebase.

🔍 Detection Indicators

Known file hashes include MD5 3b1c7a4f9e6d2c5b8a0f1e3d4c7b6a5f (from AlienVault OTX); behavioral signatures include unusual outbound connections on port 443 with custom User-Agent strings like “Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)”. Network IOCs include URIs containing “/gate.php” or “/reports/”, and registry keys such as “HKCUSoftwareMicrosoftWindowsCurrentVersionRunDyre”. The mutex name “DyreMutex” has been observed in multiple sandbox reports.

☠️ Risk & Impact

Dyre enables attackers to perform unauthorized wire transfers and initiate ACH fraud, often targeting business banking accounts. The financial industry remains the primary sector affected, with losses per incident frequently exceeding $1 million; the malware also exfiltrates session cookies and personally identifiable information (PII).

🛡️ Mitigation

Recommended defenses include blocking DGA-generated domains via threat intelligence feeds, enabling endpoint detection and response (EDR) with behavioral rules against browser hooking, and enforcing multi-factor authentication (MFA) for online banking. Regular patch management for browsers and operating systems reduces attack surface, while email security gateways filtering malicious attachments with macro-based payloads can prevent initial infection.

🛡️

Protect Your Server from Malware-Associated Bot Traffic

Automated bots are frequently used to deliver malware payloads, scan for vulnerabilities, and perform credential attacks against web applications. Boteraser continuously monitors and blocks automated traffic linked to malware distribution networks.

✅ Start Free Protection

Setup takes under a minute  ·  Free trial available

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the malware listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.