Dridex is modular Windows malware best known as a banking Trojan. It has been used to steal passwords, personal information, and online-banking details for fraudulent transactions. Dridex has also served as an access and payload-delivery platform, so an infection can lead to more than bank-account theft.
The UK National Cyber Security Centre reports that Dridex has affected victims since at least 2014 and commonly arrives through malicious phishing attachments or is dropped by existing malware such as Emotet. Delivery methods and modules change, so responders should analyze the observed campaign rather than depend on one historical filename or document format.
What Dridex does
Capabilities vary by version and operator configuration. Documented activity includes:
- Collecting system and user information.
- Stealing browser, form, password, and financial data.
- Capturing input through keylogging or browser interception.
- Connecting to distributed command infrastructure.
- Downloading modules and additional malware.
- Providing a foothold used in broader criminal intrusion and ransomware chains.
TLS between the browser and bank does not protect a session from malware already running on the endpoint. A banking Trojan can read data before it is encrypted or after the browser decrypts it.
A typical Dridex infection chain
- Delivery: a user receives a convincing invoice, payroll document, archive, link, or other phishing lure.
- Execution: a document macro, script, shortcut, loader, or exploit launches the next stage.
- Installation: Dridex establishes execution and communicates with attacker infrastructure.
- Collection: modules monitor browsers, credentials, forms, or financial sessions.
- Follow-on activity: stolen access is used for fraud, or other malware is deployed into the environment.
A detection for the loader may occur after the attachment has already launched another component. Conversely, a blocked attachment that never executed does not automatically mean the endpoint was infected. Process and network telemetry determine the outcome.
Possible warning signs
- A security alert naming Dridex, Bugat, or a related campaign component.
- Office software or an archive utility starting scripts, command shells, or unexpected system tools.
- New persistence, packed DLLs, or unfamiliar processes in user-writable folders.
- Connections to unusual or newly observed destinations from a workstation.
- Unrecognized financial transactions, payees, logins, mailbox rules, or account-recovery changes.
- Additional detections for loaders, credential theft, remote access, or ransomware.
What to do after a detection
- Isolate the endpoint and stop using it for email, banking, administration, or password changes.
- Preserve evidence: message, attachment, URLs, hashes, process tree, persistence, DNS and proxy records, and detection times.
- Contact affected financial institutions through verified channels if banking data or payments may be exposed. Review transactions and newly added payees.
- Protect accounts from a clean system. Revoke sessions, reset passwords and recovery information, and enable strong MFA.
- Search other mailboxes and endpoints for the same campaign indicators and execution pattern.
- Scan or rebuild. Remove every stage and reimage high-value systems when follow-on access cannot be ruled out.
- Monitor after recovery for renewed authentication, payment, email, and command-and-control activity.
Prevention
Block risky attachment types and unnecessary macros or script interpreters, patch browsers and document software, and give users only the privileges they require. Use email authentication and filtering, endpoint behavior monitoring, network segmentation, and controls for unusual child processes. Financial workflows should require independent approval for new payees and high-risk transactions so one compromised workstation cannot authorize payment alone. Regularly test payment-fraud escalation contacts so employees know how to stop a suspicious transfer quickly.
Frequently asked questions
Is Dridex ransomware?
Dridex is primarily classified as banking and access malware. It has been associated with chains that deliver ransomware, but the Dridex component itself should not be equated with the later encryptor.
Does removing Dridex make stolen credentials safe again?
No. Reset exposed credentials and revoke sessions from a clean device after containment, then review accounts for abuse.