Yesterday news emerged about a new ransomware outbreak dubbed Bad Rabbit. The new ransomware has some similarities to the Petya/Not Petya ransomware attack that took the world by storm last summer. Both ransomware families encrypt the entire disk. As of now, it appears that most reported victims are in Eastern Europe with some reports suggesting that some victims were detected in the United States. While the US-CERT issued a notice that it is aware of the attacks, it has no specific information on US victims.
Bad Rabbit binary is currently being delivered to the victim as a fake Adobe Flash update (SHA256: 630325cac09ac3fab908f903e3b00d0dadd5fdaa0875ed8496fcbb97a558d0da) through compromised websites, and one particular delivery domain, 1dnscontrol[.]com, has been identified in numerous Industry reports. Researchers at Cisco Talos demonstrated how BadRabbit victims were redirected to this delivery domain via compromised websites.
First, there was a POST request to 185.149.120[.]3/scholargoogle to collect some information such as user agent, referring site, cookie and domain name of the session. Next, the ransomware dropper was delivered via two paths:
At this time, it appears that the delivery domain is no longer active; however, both the IP and domain have been placed into FirstWatch C2 feeds available in RSA Live with the following meta tags:
- threat.category = "ransomware"
- threat.desc = "badrabbit"
Executing the malware on a 32bits Windows machine, it dropped the following files on the system (names of the dropped files might vary from one system to another):
Executing the malware on a 64bits Windows machine, it dropped the following files:
Here is a process tree after running the dropper:
The malware creates two scheduled tasks to perform the following:
- A scheduled task to run the open source utility DiskCryptor to encrypt the entire disk.
- A scheduled task to reboot the system at a certain time.
Strings embedded in the unpacked DLL suggest that the malware also targets a certain list of files for encryption:
- Note: It remains unclear why the malware has a list of target file extensions, while it's behavior encrypts the whole disk.
The malware also drops mimikatz-like binaries to harvest credentials. Communication between those binaries and the malware is done through a named pipe as shown in the process tree above.
In addition to the stealers, the malware comes embedded with a list of default usernames and passwords. These credentials are used by the malware to try to login to other systems via SMB and infect them. It should be noted, that BadRabbit does not currently use the EternalBlue vulnerability for lateral movement; instead this is basic scanning and login attempts for the following shares.
If a login attempt is successful, 'infpub.dat' is dropped into Windows directory and executed via SCManager and rundll.exe.
In it's final stages, Bad Rabbit executes a system reboot, after which the victim is presented with a ransom note:
The helpful message on caforssztxqzf2nm[.]onion notifies victims of 0.05 Bitcoin ransom with a message suggesting that the price will go up after some 10+ hours.
Microsoft recently released a threat bulletin on Bad Rabbit . It has the following instructions to stop the system from rebooting (thus stopping it from encrypting the disk):
- Check event logs for the following IDs: 1102 and 106
Event 1102 indicates that the audit log has been cleared, so previous activities can’t be seen.
Event 106 indicates that scheduled tasks "drogon" and "Rhaegel" have been registered (these are ransomware wipers)
If events 1102 and 106 are present, issue a shutdown -a to prevent a reboot
Halim Abouzeid has a detailed post on how the post infection activity looks in both NetWitness Packets and NetWitness Endpoint.