{ "family": "goldun", "sample_count": 1, "category": "trojan", "description": "

Executive Summary

\nGoldun 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.\n\n

Infection Vector and Technical Capabilities

\nGoldun 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.\n\nOnce active, Goldun employs precise, financially-motivated data harvesting techniques:\n\n\n

Threat Assessment

\nA 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.\n\n

Incident Response and Remediation

\n", "cta": "Published by the SystemHelpdesk team.", "aliases": [ "Trojan.Goldun", "Banker.Goldun", "Win32/Spy.Goldun" ], "enrichment_level": "expert-seo", "faq": [ { "@type": "Question", "name": "What is Goldun and what threat category does it belong to?", "acceptedAnswer": { "@type": "Answer", "text": "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." } }, { "@type": "Question", "name": "How does Goldun establish persistence and evade defensive controls?", "acceptedAnswer": { "@type": "Answer", "text": "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." } }, { "@type": "Question", "name": "What are the essential incident response steps for mitigating a Goldun compromise?", "acceptedAnswer": { "@type": "Answer", "text": "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." } }, { "@type": "Question", "name": "What secondary payloads and staging behaviors are commonly associated with Trojan.Goldun?", "acceptedAnswer": { "@type": "Answer", "text": "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." } }, { "@type": "Question", "name": "How can security operations teams effectively detect and hunt for Trojan.Goldun across enterprise endpoints?", "acceptedAnswer": { "@type": "Answer", "text": "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." } } ], "faq_count": 5, "mitre_attack": [ "T1056.004", "T1552.001", "T1114" ], "cisa_advisory": null, "last_updated": "2026-10-15", "type": "Banking Trojan / Info Stealer", "target_industries": [ "Global / Opportunistic" ], "motivation": "Opportunistic", "threat_actors": [ "Unknown / Cybercriminal" ], "target_geographies": [ "Global" ], "attack_stage": [ "execution", "persistence" ], "ecosystem": [ "windows_pe" ], "is_emerging": false, "mitre_attack_detail": [ { "id": "T1056.004", "name": "Input Capture: Credential API Hooking", "tactic": "Credential Access" }, { "id": "T1552.001", "name": "Credentials In Files (Harvesting passwords and wallets from local storage)", "tactic": "Credential Access" }, { "id": "T1114", "name": "Email Collection (Harvesting addresses for spamming)", "tactic": "Collection" } ], "containment_steps": [ "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": [ "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." ], "target_platforms": [ "Windows 11", "Windows 10", "Windows 7" ] }