|
Introduction Shade ransomware was spotted in the wild as early as 2014, and it was first called Troldesh. I previously wrote an ISC diary on malicious spam (malspam) pushing Troldesh ransomware two years ago in November 2016, and I also documented a later example in March 2017. However, Shade/Troldesh ransomware has been spotted in the wild since then. I searched Twitter and found a handful of sightings in the past few weeks. Today's diary reviews recent examples from a campaign using Russian-language malspam to push Shade/Troldesh, and it also examines an infection from Wednesday 2018-11-28.
Recent campaign since October 2018 This investigation started after I ran across a Russian language email with an attachment that caused a Shade/Troldesh ransomware infection after I checked it in my lab environment. I hadn't paid much attention to this ransomware family in a while, so I decided to look into it. My first step in the investigation was checking URLhaus. There I found approximately 50 URLs reported as an executable and tagged either Shade or Troldesh (or both) since October 2018. Many of these URLs ended with sserv.jpg, and a search on that revealed 71 URLs reported since 2018-11-01. I added more URLs after my investigation. Not all of these URLs reported to URLhaus were tagged Shade or Troldesh, but they fit the same general pattern that I'd seen from my infection traffic. Searching through VirusTotal Intelligence, I found Russian language malspam with attached zip archives pushing Shade/Troldesh ransomware since at least 2018-10-30. I collected 12 examples to investigate for this diary.
The malspam The emails are in Russian, and they claim an order or a request from a bank.
An infected Windows host Potential victims would need to be on a vulnerable Windows host with poor security measures. Victims would open the attached zip archive, then they would need to double-click the JavaScript (.js) file contained in the archive. This causes their Windows computer to retrieve Shade/Troldesh ransomware and become infected. The ransomware infection quickly becomes obvious.
Infection traffic Almost immediately after the initial Shade/Troldesh malware binary is retrieved, the infected host generated Tor traffic. Then the infected host checked it's IP address and generated encrypted SMTP traffic to smtp.mail.ru.
After four cycles of IP address checks and SMTP traffic, the infected Windows host generated a great deal of web traffic. This reminded me of click-fraud traffic.
Indicators The following are indicators from this malspam campaign and the associated infections:
Attachment names noted so far:
Some SHA256 hashes for attached zip archives:
Some SHA256 hashes for extracted JS files:
URLs generated by the above extracted JS files:
SHA256 hashes of Shade/Troldesh ransomware retrieved from any of the above URLs on still active on 2018-11-28:
Malware from an infected Windows host: SHA256 hash: 5f50dcf06dd5fb51b26f815fd8ff6d4a5afa7301e9c7923ea8f75b2b1e224f82
SHA256 hash: e51f36811056d71c970791223da17c3f5b4d84394063a42eb8f2c432e97dba7a
SHA256 hash: d5fe31471af8abcd884108fbbfe776c3df6c988a865e401fc83ccbdfe030ed4e
SHA256 hash: 2824a8ce0e65bb185a88ff1fe5f1df202405c42b6705a420dbc07c565a44b240
Tor domains from the decryption instructions:
Email address from the decryption instructions:
Final words 12 email examples, a pcap of network traffic traffic from an infection, and the associated malware/artifacts are available here. I checked the 28 URLs I found ending in .jpg for delivering the initial Shade/Troldesh malware binary. 17 of them still returned the ransomware executable. All URLs have been submitted to URLhaus, so hopefully they'll all get taken off-line soon. These URLs will not work if you copy/paste them into a browser, because the servers hosting this malware are looking for the right User-Agent string. You'd have to use a tool like curl to spoof the correct User-Agent string and get the malware.
Russian language malspam pushing Shade/Troldesh ransomware is not anything new. As mentioned earlier, I posted a diary about it back in 2016 and I doubt it ever really disappeared for long. Nor is this malspam limited to Russian malspam. The example I documented in 2017 was from English language malspam. This diary is yet another reminder that the criminals behind this malware remain active and are still trying to infect vulnerable Windows hosts. --- |
Brad 346 Posts ISC Handler |
| Subscribe |
Nov 29th 2018 11 months ago |
|
malspam?? It's a new word! Congrats.
Maybe now people will stop calling every malicious email "phishing". |
Anonymous |
| Quote |
Nov 29th 2018 11 months ago |
Sign Up for Free or Log In to start participating in the conversation!
