Last Updated: 2016-01-28 18:54:46 UTC
by Brad Duncan (Version: 1)
Some of these blocked emails have malicious Microsoft Office documents (Word, Excel, etc.) as file attachments.
Most of these Office documents have macros that, if enabled, will download and install malware on an unprotected Windows host. Payloads vary with this type of malspam. We've seen CryptoWall  and Pony or other downloaders pushing further payloads [2, 3, 4].
However, Dridex is by far the most common malsapm we see using malicious Office documents. Several sources routinely report waves of Dridex malspam [for example: 5, 6, 7]. I've already posted some diaries about Dridex here for the Internet Storm Center (ISC) [8, 9, 10].
I haven't posted any technical details on Dridex in the past few months, so I figure we're overdue for a review.
What is Dridex?
Dridex is credential-stealing malware that targets Windows clients like desktops and laptops. Dridex is designed to steal credentials and obtain money from victims' bank accounts. The malware is generally distributed through email . Dridex-related email has often been labeled as phishing; however, it is more accurately described as malspam. The criminal organizations behind this malware rely on Microsoft office documents containing malicious macros to download Dridex onto an unsuspecting user's Windows computer .
First spotted around November 2014, Dridex is considered the direct successor of Cridex banking malware . Dridex malspam has been fairly consistent since then, usually appearing on a near-daily basis. Dridex disappeared about a month in September 2015 after the arrest of an administrator for a botnet delivering the malware. By October 2015, Dridex malspam was back , and it's been appearing on a near-daily basis up through the present day.
According to IBM security intelligence, Dridex released a new malware build earlier this month on 2016-01-06. This new build was followed by a malspam campaign using the Andromeda botnet to deliver malware to would-be victims. Campaigns have mainly focused on users in the UK .
Dridex malspam from Monday 2016-01-25
On Monday 2016-01-25, we saw a wave of 558 Dridex malspam messages. These 558 messages were sent to 398 different UK-based email addresses, which matches the geographic targeting stated in the IBM security intelligence report .
Let's take a closer look at one of these emails.
The sender, subject lines, message text, and attachment names are different for each email sent by the botnet. After opening the attached Word document on a Windows host, then enabling the macros, we saw the following traffic:
Enabling the macros caused an HTTP GET request for Dridex malware. It was sent in the clear over TCP port 80.
The remaining traffic includes SSL over TCP ports 4143 and 443. The infected host contacted other IP addresses that didn't respond, and we saw some encrypted traffic for two other IP addresses over TCP port 444. The SSL traffic used certificates similar to Dridex examples we've seen before.
Overall, this was a fairly straight-forward example of recent Dridex activity. There were no tricks to obfuscate or hide the initial malware downloaded by the document macros. Too bad I didn't get an example from some of the trickier methods Dridex uses to disguise this initial download [15, 16]. Dridex malspam is sent by different botnets. The associated malware will have different characteristics depending on the wave of malspam sent by a particular botnet . Today's diary only provides one such example.
Traffic and malware used for this diary can be found here.
If you have a properly-configured Windows host in a well-administered environment, your risk of infection is low. Unfortunately, humans are the weakest link in this infection chain. I still hear an occasional story about someone who was infected with Dridex. These waves of malspam must be profitable for the criminals behind Dridex, or we wouldn't continue seeing them.
Have you seen Dridex this year? Has anyone had to respond to a Dridex infection? If so, please share your story by leaving a comment below.