|
2017-03-22 Update: This diary was posted earlier, but we had some technical issues, and the previous diary disappeared. I had to re-post this as a new diary with a new story ID and URL. Introduction Cerber ransomware has been a constant presence since it was first discovered in February 2016. Since then, I've seen it consistently pushed by exploit kits (like Rig and Magnitude) from the pseudoDarkleech and other campaigns. I've also been tracking Cerber on a daily basis from malicious spam (malspam). Some malspam pushing Cerber is part of the "Blank Slate" campaign. Why call it Blank Slate? Because the emails have no message text, and there's nothing to indicate what, exactly, the attachments are. Subject lines and attachment names are vague and usually consist of random numbers. An interesting aspect of this campaign is that the file attachments are double-zipped. There's a zip archive within the zip archive. Within that second zip archive, you'll find a malicious JavaScript (.js) file or a Microsoft Word document. These files are designed to infect a computer with ransomware. Blank Slate has pushed different types of ransomware. However, the vast majority of ransomware from this campaign has been Cerber. I wrote an in-depth article about Blank Slate earlier this month, and it's changed very little since then.
Let's look at some examples from Monday and Tuesday of this week (2017-03-20 and 2017-03-21). The emails Like other malspam campaigns, Blank Slate emails come from numerous hosts across the globe. I always think of this as botnet-based malspam, but I don't have any visibility on the sending side.
Sending email addresses are always spoofed. The only reliable source data consists of IP addresses for sending mail servers, specifically the one that directly contacted the recipient's mail server, as noted in the email headers. Everything else in an email can probably be spoofed. What does one of these emails look like? Below is a screen shot with the recipient's information redacted.
What's in the zip file attachment? Another zip file!
What's in that zip within the zip? It's either a Microsoft Word document, or it's a .js file. In this case it's a .js file. I've seen many more .js files than Word documents in recent weeks from this campaign.
The .js file contains obfuscated script. If you double-click the file on a default-configured Windows host, Microsoft Windows Script (WScript) Host will execute the code and try to infect the computer.
The traffic On Monday 2017-03-20, I ran one of the extracted .js files on a vulnerable Windows host. After an initial HTTP GET request for the ransomware binary, post-infection traffic was similar to several other recent examples of Cerber. You'll see UDP traffic from the infected host over port 6892. That's followed by HTTP traffic to a domain starting with p27dokhpz2n7nvgr and ending with .top. IP addresses for the UDP traffic changes every week or two (or longer). Post-infection HTTP domains change more frequently.
The infected Windows host acted similar to other hosts I've infected in previous months. Along with the desktop background, decryption instructions were dropped to the desktop in three different files. File names began with _READ_THIS_FILE_ and consisted of a text file, an image file, and an HTA file.
The decryption process hasn't changed in recent months. Recently, whenever I've checked Cerber decryption instructions, the ransom was consistently $500 US dollars. The bitcoin amount had always reflected that $500 dollar value. But this week's example was different. This week, the ransom was 1 bitcoin.
Indicators of Compromise (IoC) The following IP is traffic generated by the extracted .js files that downloaded Cerber:
Post-infection Cerber traffic:
Cerber samples collected using this batch of emails: SHA256 hash: 92135e39f2e0db1aaf6605446e24fc9aedc36eb4bed9e7cdad1e92e4d387ed04
SHA256 hash: 035d137592a7f6ce707739ceecb09db517587bcb0100254c3dd8ee4a262603af
SHA256 hash: ee6b4e29aac7ca55a19265728d484221956b1b11c4961b60dd70137316bde245
SHA256 hash: 0456237db4444582d94f4231824bdc09475d844820f14fcd2172ccdc13bddbf3
SHA256 hash: d3a6ab8e8f6eb49cba032208d04d7105ac764982ca56fcaf1a421396e1adadfa
Final words I always wonder how effective campaigns like this are. Potential victims must open an attachment from a blank email, go through two zip archives, then double-click the final file. If the final file is a Word document, the victim must also enable macros. And that works on default Windows configurations. But properly-administered Windows hosts and decent email filtering are enough, I think, to keep most people from worring about it. I'm far more interested in the cycle of abuse targeting hosting providers. Without web servers to host ransomware binaries, Blank Slate cannot continue its current method of operations. For more details on Blank Slate, see my previous writeup about it. Pcap and malware samples for this ISC diary can be found here. --- |
Brad 345 Posts ISC Handler |
| Subscribe |
Mar 22nd 2017 2 years ago |
|
I've seen something exactly like this in the past weeks. I dubbed the attachments as "Matryoshka style". See description and IOCs on
https://truica-victor.com/email-scams-sloppy-cerber-dropper/ Whats interesting is that the spam filter is very bad at identifying it though. All of this is getting in my inbox. Over a 10 months period i’ve receiving the same kind of things from the same email address (different IPs though). I've also noticed the "Matryoshka style" attachments in another set of spam emails - https://truica-victor.com/email-scams-various-ups-delivery-notifications-failures/ |
vatruica 1 Posts |
| Quote |
Mar 22nd 2017 2 years ago |
Quoting vatruica:I've seen something exactly like this in the past weeks. That first example is definitely the same Blank Slate campaign. I think your second example with the fake delivery notifications is a different campaign that's been pushing Kovter and Locky or some other ransomware lately. Thanks for the info! |
Brad 345 Posts ISC Handler |
| Quote |
Mar 22nd 2017 2 years ago |
Sign Up for Free or Log In to start participating in the conversation!
