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

Executive Summary

\nRedaman is a highly sophisticated Banking Trojan that primarily targets financial institutions, payment processors, and corporate banking portals, historically focusing heavily on the Russian and Eastern European financial sectors. Evolving from earlier banking trojans (and sharing code similarities with the RTM banking trojan), Redaman is engineered for massive financial theft, utilizing advanced evasion techniques and localized man-in-the-browser (MitB) attacks.\n\n

Infection Vector and Technical Capabilities

\nRedaman is predominantly distributed via highly targeted, localized spear-phishing campaigns. These emails often contain weaponized attachments (such as malicious PDF files or Word documents with macro exploits) or deceptive links disguised as urgent financial invoices or tax documents.\n\nOnce executed, Redaman deploys a multi-stage infection process:\n\n\n

Threat Assessment

\nA Redaman infection is a critical, high-impact security incident. It represents a direct, immediate threat of massive financial loss, corporate account takeover, and severe regulatory compliance breaches for the affected organization.\n\n

Remediation and Eradication

\n", "cta": "Published by the SystemHelpdesk team.", "aliases": [ "Trojan-Banker.Win32.Redaman", "Banker.RTM", "Win32/Redaman" ], "enrichment_level": "expert-seo", "faq": [ { "@type": "Question", "name": "What is Redaman and what threat category does it belong to?", "acceptedAnswer": { "@type": "Answer", "text": "Redaman 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 Redaman establish persistence and evade defensive controls?", "acceptedAnswer": { "@type": "Answer", "text": "Redaman 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 Redaman compromise?", "acceptedAnswer": { "@type": "Answer", "text": "Security teams responding to Redaman 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-Banker.Win32.Redaman?", "acceptedAnswer": { "@type": "Answer", "text": "Trojan-Banker.Win32.Redaman 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-Banker.Win32.Redaman across enterprise endpoints?", "acceptedAnswer": { "@type": "Answer", "text": "Defenders should hunt for Trojan-Banker.Win32.Redaman 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.001", "T1185", "T1114", "T1056.004" ], "cisa_advisory": null, "last_updated": "2026-10-15", "type": "Banking Trojan", "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.001", "name": "Keylogging", "tactic": "Credential Access" }, { "id": "T1185", "name": "Browser Session Hijacking (Ad injection and tracking)", "tactic": "Collection" }, { "id": "T1114", "name": "Email Collection (Harvesting addresses for spamming)", "tactic": "Collection" }, { "id": "T1056.004", "name": "Input Capture: Credential API Hooking", "tactic": "Credential Access" } ], "containment_steps": [ "Sever network connectivity for the flagged endpoint to terminate persistent command-and-control (C2) communication channels and stop Redaman from retrieving secondary stage payloads.", "Capture process memory triage to detect and terminate malicious threads injected by Redaman 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 Redaman 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 Redaman execution timeframe." ], "what_to_avoid": [ "Do not assume the incident is resolved simply because an antivirus tool removed the initial Redaman 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 Redaman 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" ] }