Information Security News
Rig exploit kit (EK) is one of a handful of EKs still active as reported in May 2019 by Malwarebytes. Even though EKs are far less active than in previous years, EK traffic is still sometimes noted in the wild. Twitter accounts like @nao_sec, @david_jursa, @jeromesegura, and @tkanalyst occasionally tweet about EK activity. Today's diary reviews a recent example of infection traffic caused by Rig EK.
For the past year, Rig EK has been using Flash exploits based on CVE-2018-8174 as noted in this May 2018 blog post from @kafeine. Since then, other sources have reported Rig EK delivering a variety of malware like the Grobios Trojan or malware based on a Monero cryptocurrency miner. Like other EKs, Rig EK is most often used in malvertising distribution campaigns. In today's infection, Rig EK delivered AZORult, and the infection followed-up with other malware I was unable to identify.
I used a gate from malvertising traffic in a recent tweet from @nao_sec. See images below for details.
Shown above: Follow-up malware EXE retrieved by my infected Windows host.
Indicators of Compromise (IOCs)
Redirect domain that led to Rig EK:
AZORult post-infection traffic:
Infected Windows host retrieved follow-up malware:
My infected Windows host retrieved follow-up malware after the initial AZORult infection. However, I was using a virtual environment, and I didn't see any further post-infection traffic, so I could not identify the follow-up malware.
A pcap of the infection traffic along with the associated malware and artifacts can be found here.
brad [at] malware-traffic-analysis.net
Sysmon Version 10.0 brings DNS query logging.
By default, DNS query logging is not enabled. You need to provide a configuration file, like this simple config.xml:
This config file will log all DNS queries: using onmatch="exclude" without any filters excludes no events at all.
Remark also that the event is DnsQuery (and not DNSQuery as listed on Sysinternals page for Sysmon).
Here is a simple "ping google.com" command, resulting in event 22 being logged in the Sysmon Windows event log:
Remark that event 22 does not only log the DNS query, but also the replies and the program that issued the query.
If you enable DNS logging like I did (not exclusions) in a production environment, you will have too many events. SwiftOnSecurity's Sysmon config can help you exclude many queries that are not important for IR.
Sysmon DNS logging did not work on my Windows 7 VM, but I just noticed that Sysmon version 10.1 was released, I will test this again.
Update: version 10.1 on Windows 7 does not log DNS events.