Goldun
Table of Contents
Overview
Executive Summary
Goldun is a specialized banking trojan and information stealer designed to compromise user accounts across various financial institutions, e-currency platforms, and cryptocurrency exchanges. Operating primarily as a highly stealthy credential harvester, Goldun prioritizes the theft of login data, two-factor authentication (2FA) tokens, and session cookies to facilitate immediate and unauthorized financial transactions.Infection Vector and Technical Capabilities
Goldun is typically distributed through targeted spear-phishing campaigns masquerading as financial alerts, or deployed silently by exploit kits hosted on compromised websites. It is also frequently dropped as a secondary payload by other prevalent trojans. Once active, Goldun employs precise, financially-motivated data harvesting techniques:- Man-in-the-Browser (MitB): Advanced variants of Goldun inject malicious code directly into web browsers (API hooking) to intercept data before it is encrypted via HTTPS. This allows the attacker to capture banking passwords and PINs in plaintext.
- Web Injects: It can dynamically alter the HTML of legitimate banking websites displayed to the victim, prompting them to enter additional sensitive information (like ATM PINs, Social Security numbers, or answers to security questions) which is then exfiltrated.
- Credential Store Extraction: The trojan systematically extracts saved passwords, cookies, and session tokens directly from the local credential stores of popular web browsers.
Threat Assessment
A Goldun infection is a critical security incident prioritizing immediate financial fraud. The theft of session cookies and 2FA tokens can allow attackers to bypass standard security measures and drain corporate or personal bank accounts directly.Incident Response and Remediation
- Immediate Network Isolation: The highest priority is to isolate the endpoint to halt the active exfiltration of captured credentials and network traffic logs.
- Immediate Financial Notification: Contact associated financial institutions immediately to freeze accounts and monitor for unauthorized transactions.
- Global Credential Reset: A mandatory, global reset of all associated credentials (including MFA tokens) is absolutely required.
- Complete Re-imaging: Due to the deep system hooking required for Man-in-the-Browser attacks, the endpoint must undergo a complete bare-metal wipe and re-image from a trusted baseline.
Known aliases
Threat reports may refer to this family under multiple names:
MITRE ATT&CK Techniques
Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:
| Technique | Name | Tactic | Official Spec |
|---|---|---|---|
T1056.004 | Input Capture: Credential API Hooking | Credential Access | ATT&CK ↗ |
T1552.001 | Credentials In Files (Harvesting passwords and wallets from local storage) | Credential Access | ATT&CK ↗ |
T1114 | Email Collection (Harvesting addresses for spamming) | Collection | ATT&CK ↗ |
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- T1056.004: Monitor for unauthorized keylogging, screen capturing, or web browser API hooking. Deploy EDR to detect API hooking.
MITRE D3FEND™ Defensive Countermeasures
Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):
| D3FEND ID | Countermeasure Name | Tactic | Countered ATT&CK | Defensive Guidance |
|---|---|---|---|---|
D3-AHC | API Hook Detection | Detect | T1056.004 | Deploy kernel and userland EDR drivers to monitor SetWindowsHookEx and low-level keyboard hooks. |
D3-EAM | Email Access Monitoring | Detect | T1114 | Monitor Graph API and MAPI email harvesting routines and alert on bulk email downloads originating from unusual IP addresses. |
D3-FPA | File Permission Auditing | Harden | T1552.001 | Scan filesystem repositories for plaintext configuration files and restrict access via Least Privilege RBAC controls. |
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_GOLDUN_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Goldun"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "goldun" ascii wide nocase
$s2 = "trojan.goldun" ascii wide nocase
$s3 = "banker.goldun" ascii wide nocase
$s4 = "win32/spy.goldun" 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 - Goldun (Trojan) Execution & Triage
id: e5387f4a-7e25-5ad1-950a-ca7fbacaa278
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Goldun malware family. Detects suspicious execution from temporary user
directories with hidden window flags and background transfer utilities.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/goldun
- https://malware-families-catalog.systemhelpdesk.com/defensive/downloader-dropper-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.trojan
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1056_004
- attack.t1552_001
- attack.t1114
logsource:
category: process_creation
product: windows
detection:
selection_process:
Image|endswith:
- \cmd.exe
- \powershell.exe
- \cscript.exe
- \wscript.exe
CommandLine|contains:
- AppData\Local\Temp
- -WindowStyle Hidden
- /e:jscript
- bitsadmin /transfer
condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: mediumTier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_GOLDUN_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Goldun 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 = "goldun" 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
}Containment & Response Steps
Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.
- Sever network connectivity for the flagged endpoint to terminate persistent command-and-control (C2) communication channels and stop Goldun from retrieving secondary stage payloads.
- Capture process memory triage to detect and terminate malicious threads injected by Goldun into legitimate system processes such as explorer.exe or svchost.exe.
- Audit Windows Registry Run keys (HKCU\Software\Microsoft\Windows\CurrentVersion\Run) and Task Scheduler entries to locate and purge Goldun persistence hooks.
- Deploy updated enterprise EDR detection signatures and conduct an out-of-band endpoint scan to isolate dropped binaries and staged payloads.
- Rotate all credentials, domain user passwords, and session cookies active on the system during the Goldun execution timeframe.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not assume the incident is resolved simply because an antivirus tool removed the initial Goldun dropper; always verify that secondary payloads and persistence hooks have been eradicated.
- Avoid logging in with Domain Admin or privileged credentials on a machine suspected of running Goldun until memory triage is complete.
- Do not delay host isolation; automated lateral movement and credential dumping can occur within minutes of initial execution.
References & External Analysis
- Search "goldun" on VirusTotal (External Analysis)
- Search "goldun" on Any.Run (Sandbox Sandbox)
- Search "goldun" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Goldun and what threat category does it belong to?
Goldun is classified as a Trojan. Documented across security telemetry, it is engineered to execute unauthorized operations, establish persistent footholds on target endpoints, and facilitate malicious campaigns targeting enterprise and individual environments.
How does Goldun establish persistence and evade defensive controls?
Goldun typically establishes persistence through registry run keys, scheduled tasks, or service installations, while evading signature-based antivirus solutions through code obfuscation, memory injection, or anti-analysis sandbox checks.
What are the essential incident response steps for mitigating a Goldun compromise?
Security teams responding to Goldun should immediately isolate affected endpoints from the network, perform memory triage to capture volatile forensic artifacts, audit registry and startup persistence mechanisms, revoke exposed user credentials, and restore systems from verified, clean backups.
What secondary payloads and staging behaviors are commonly associated with Trojan.Goldun?
Trojan.Goldun frequently operates as a loader or dropper designed to establish a foothold before downloading and executing secondary high-impact malware payloads. Depending on the threat actor's objectives, these dropped modules can range from ransomware and banking injects to modular infostealers and remote management backdoors.
How can security operations teams effectively detect and hunt for Trojan.Goldun across enterprise endpoints?
Defenders should hunt for Trojan.Goldun by deploying behavioral endpoint detection and response (EDR) rules that monitor suspicious process spawning (such as cmd.exe or powershell.exe spawned from office documents or temporary directories), anomalous outbound network connections from non-browser binaries, and unauthorized modifications to Windows Run keys and scheduled task registries.
How do I remove the Goldun Trojan from Windows?
Manual removal of Goldun 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 Goldun a virus or a Trojan?
Goldun is classified as a Trojan. Unlike traditional viruses that infect files, modern malware like Goldun typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Goldun infection?
Symptoms of Goldun 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 Trojans
Want to prevent Goldun 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.
Machine-readable
Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/goldun.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.