I found this website through someone mentioning Rig EK so decided to analyse it to look for any new changes. The website contains the PseudoDarkleech gate.
My setup did not deliver Cerber ransomware however the Cerber Check In UDP traffic was observed again. I decided this time to save the payload before it terminated itself. I then put it through an online sandbox to see what would happen and found the exact same result.
The payload also created a strange “.8H” file which was not readable. I have been unable to find an answer as to why Cerber creates the UDP traffic. It is possible the payload has other functionality such as commands to a bot net to perform DDoS or the Emerging Threat signature is a not a false positive and it is an action of the infamous Conficker.
- A few articles on Rig exploit kit and it’s evolution:
- Article on the PseudoDarkleech campaign and its history:
- zerorigek190117 -> Contains Pcap, payload and interesting files in password protected zip.
- 18.104.22.168 – lacaze-tarn[.]com – COMPROMISED WEBSITE
- 22.214.171.124 – 4wx[.]leecrismanradio[.]com – RIG-V
- 126.96.36.199/24 – UDP port 6892 – Cerber Check In IP Range
- 188.8.131.52/24 – UDP port 6892 – Cerber Check In IP Range
- 184.108.40.206 -> 220.127.116.11 – UDP port 6892 – Other UDP Traffic
- 18.104.22.168 -> 22.214.171.124 – UDP port 6892 – Other UDP Traffic
- Payload was rad92106.tmp.exe -> VirusTotal
- Conscious that I did not receive Cerber I also put it into HybridAnalysis which reported the exact same result.
- Also created a “.8H” file called “clearance“.
Details of infection chain:
- Compromised site redirects to Rig-V EK via PseudoDarkleech iframe.
- 4wx[.]leecrismanradio[.]com is Rig EK, from top to bottom -> Pre-Landing -> Landing Page -> Flash exploit -> Payload
- UDP traffic port 6892 to 126.96.36.199/24 all contained the data”0ca5ea83d2eb008c170000026“
- Dropped payload “rad4DE50.tmp.exe“
- Payload terminated itself and then deleted itself but also created a “.8H” file called “clearance“.
- Emerging Threat signatures for Cerber and Conficker
- I have not ruled out that this could be an action of Conficker but many other researchers have received Cerber following the UDP traffic observed. I have also seen the same in the past and received Cerber.