Dyre, also known as Dyreza and Dyzap, is a banking trojan focused on compromising Windows systems. The provided content describes it as using HTTPS for command-and-control communications and, in some variants, using STUN to determine the infected host’s public IP address behind NAT, with icanhazip.com used as a fallback if STUN failed. Dyre can identify users on a compromised host, identify running services, identify installed programs, and identify network settings. It can create files in a TEMP folder to act as a local database for staged information, then send staged information externally to command-and-control infrastructure. For execution and credential theft-related activity, Dyre can directly inject its code into web browser processes. For persistence, it registers itself as a service by adding Registry keys and can also create a scheduled task configured to run every minute. The content also notes a Dyre banking trojan variant observed by FireEye that attempted to exploit CVE-2013-3660 and CVE-2015-0057 to obtain system privileges. A network detection artifact explicitly associated with the Dyre malware family is the JA3 TLS fingerprint b386946a5a44d1ddcc843bc75336dfce.
Mallory pivots from this family to the IOCs, detections, and named campaigns that touch your stack, and pages you when something new lands.
2 CVEs Mallory has correlated with this family across public research and vendor advisories. Each row links to the full Mallory page for that vulnerability.
Four months later, on the 17th of June, a new variant of the Dyre Banking Trojan was detected by FireEye. This variant of Dyre attempts to exploit CVE-2013-3660 and CVE-2015-0057 in order to obtain system privileges.
Four months later, on the 17th of June, a new variant of the Dyre Banking Trojan was detected by FireEye. This variant of Dyre attempts to exploit CVE-2013-3660 and CVE-2015-0057 in order to obtain system privileges.
1 distinct threat actor attributed by public researchers. Open in Mallory to see the full evidence chain and overlapping campaigns.
20 distinct techniques documented for this family, organized by ATT&CK tactic.
“Sandworm Team leveraged Scheduled Tasks through a Group Policy Object (GPO) to execute CaddyWiper at a predetermined time.” / “APT29 used scheduler and schtasks to create new tasks on remote host as part of their lateral movement… updating an existing legitimate task to execute their tools and then returned the scheduled task to its original configuration.”
“Sandworm Team leveraged Scheduled Tasks through a Group Policy Object (GPO) to execute CaddyWiper at a predetermined time.” / “APT29 used scheduler and schtasks to create new tasks on remote host as part of their lateral movement… updating an existing legitimate task to execute their tools and then returned the scheduled task to its original configuration.”
“Sandworm Team leveraged Scheduled Tasks through a Group Policy Object (GPO) to execute CaddyWiper at a predetermined time.” / “APT29 used scheduler and schtasks to create new tasks on remote host as part of their lateral movement… updating an existing legitimate task to execute their tools and then returned the scheduled task to its original configuration.”
During the 2022 Ukraine Electric Power Attack, Sandworm Team leveraged Scheduled Tasks through a Group Policy Object (GPO) to execute CaddyWiper at a predetermined time.
"Sandworm Team used UPX to pack a copy of Mimikatz"; "APT38 has used several code packing methods such as Themida, Enigma, VMProtect, and Obsidium"; "Lazarus Group packed malicious .db files with Themida to evade detection."
The content repeatedly describes adversaries and malware injecting code, shellcode, DLLs, or payloads into legitimate processes such as svchost.exe, explorer.exe, iexplore.exe, wuauclt.exe, lsass.exe, and browser processes.
The content repeatedly describes malware and threat actors decoding, decrypting, deobfuscating, or unpacking payloads, strings, configuration data, commands, and C2 responses prior to execution or use.
Environmental awareness allows malware samples to detect the underlying runtime environment of the system it is trying to infect... search for differences between a virtualized and bare metal environment... about one in five (17%) samples of the Carbanak malware samples analyzed by Lastline tried to detect a virtual sandbox before executing.
"actors used the following command ... to obtain information about services: net start"; "APT1 used the commands net start and tasklist to get a listing of the services on the system"; "OilRig has used sc query on a victim to gather information about services"; "Indrik Spider has used the win32_service WMI class to retrieve a list of services"
The content repeatedly describes malware and threat actors using commands and APIs such as ipconfig /all, ifconfig, arp -a, route print, nbtstat, netsh, GetAdaptersInfo, and GetIpNetTable to gather IP addresses, MAC addresses, DNS, DHCP, gateways, routing tables, ARP cache, proxy settings, domains, and network adapter/interface details.
The content repeatedly describes malware and threat actors collecting usernames, identifying logged-in users, running whoami/query user/quser, checking whether the current user is an administrator, enumerating user sessions, and gathering account details from compromised hosts.
The content is a long ATT&CK-style listing of malware and threat actors that collect host details such as OS version, hostname, architecture, CPU, memory, BIOS, language, and other basic system characteristics; examples include use of commands like systeminfo, ver, uname, sw_vers, and WMI queries.
Environmental awareness allows malware samples to detect the underlying runtime environment of the system it is trying to infect... search for differences between a virtualized and bare metal environment... about one in five (17%) samples of the Carbanak malware samples analyzed by Lastline tried to detect a virtual sandbox before executing.
the banking trojan employed STUN to determine an infected host’s public IP behind a NAT. While the variant analyzed included a fallback mechanism of reaching out to icanhazip.com in the event STUN didn’t work
"Bazar can query the Registry for installed applications." / "BRONZE BUTLER has used tools to enumerate software installed on an infected host." / "LightSpy ... enumerate the Applications folder to collect the bundle name, bundle identifier, and version information..." / "Volt Typhoon has queried the Registry on compromised systems for information on installed software."
While the variant analyzed included a fallback mechanism of reaching out to icanhazip.com in the event STUN didn’t work
Since JA3 detects the client application, it doesn’t matter if malware uses DGA (Domain Generation Algorithms), or different IPs for each C2 host, or even if the malware uses Twitter for C2, JA3 can detect the malware itself based on how it communicates rather than what it communicates to. | JA3 allows us to detect these applications, malware families, and pen testing tools, regardless of their destination, Command and Control (C2) IPs, or SSL certificates.
The content repeatedly describes threat actors and malware using HTTP and HTTPS for command and control, such as: "Sandworm Team used BlackEnergy to communicate between compromised hosts and their command-and-control servers via HTTP post requests."
In an attempt to evade malware blacklists, the creators of Dyre have since begun changing the malware’s domain on a daily basis. To adapt to this constant change, newer versions of Dyre now employ a domain generation algorithm (DGA), which computes where the C&C servers will be at any given time.
this post focuses on the misuse of STUN by malware... It is our belief that this trending of STUN capabilities in malware supports two goals for attackers... Hide in plain sight : Given a popular service and/or protocol, there is a higher likelihood that malware that utilizes similar communications can achieve equivalent success in its misuse, as it is allowed through the same security controls.
ADVSTORESHELL exfiltrates data over the same channel used for C2... Agrius exfiltrated staged data using tools such as Putty and WinSCP, communicating with command and control servers... numerous malware and groups sent victim data, files, credentials, or host information over existing C2 channels.
36 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Full values are available in Mallory.
IPs, domains, and DNS infrastructure linked to this family.
41 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Banking trojan referenced as previously using the STUN protocol to determine the public IP address of infected systems, with icanhazip.com as a fallback.
Dyre (Dyreza) is a banking trojan that targets online banking credentials and financial information.
Banking trojan that injects code directly into browser processes.
Earlier banking-focused botnet believed to be a predecessor to TrickBot.
Match every observed IP, domain, and hash against your live telemetry.
Named campaigns wielding this family, with evidence pinned to each claim.
CVEs this family uses for access and lateral movement.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Every documented technique, ranked by evidence weight.
Reddit, Mastodon, and CTI community discussion around this family.