Over the past few hours, we’ve observed malicious phishing emails associated with the delivery affiliate TR in multiple customer environments. The infection scheme was consistent, executing in the following pattern: OneDrive phishing page -> ZIP download -> malicious XLSB -> Qbot
The ZIP file and XLSB had formats similar to `123 (1).zip/123.xlsb`. The Excel macros downloaded a Qbot binary with an OCX file extension to the TR-specific folder “C:\Watdan” and executed it with the command `regsvr32 C:\Watdan\tle1.ocx`
We observed reconnaissance commands and lateral movement next, and the adversary dropped Cobalt Strike and Bloodhound, common post-exploitation tools, into victims’ environments. This progression of activity is a common ransomware precursor.
#RCIntel wanted to provide some detection opportunities for the community based on this information to empower defenders to respond to this activity in near real-time.
First, we recommend looking for instances of regsvr32 spawning from an excel.exe parent process. Additionally, if regsvr32 spawns an explorer.exe process, this should be prioritized for immediate investigation.
Also look out for rundll32.exe processes with no command-line arguments, with a file modification that contains ‘\pipe’. This could be an indication of Cobalt Strike behavior. It is also suspicious if rundll32 has no CLI arguments and a network connection.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
SQUIRRELWAFFLE is a malware loader that first emerged in September 2021 and is often a delivery mechanism for Qbot. We’ve seen it rapidly deliver Cobalt Strike and Bloodhound, which we frequently observe preceding impactful threats like ransomware. 1/4
This activity is novel due to its speed. SQUIRRELWAFFLE can lead to Cobalt Strike and Bloodhound within 90 minutes of the initial infection. The adversary is using a legitimate NVIDIA binary to load a malicious Cobalt Strike DLL, making the threat potentially evasive. 2/4
DETECTION OPPORTUNITIES:
1) look for =`excel.exe` spawning `regsvr32.exe` with `test1.test` in the command line
2) look for a process with an internal name of `net.exe or `net1.exe` along with a command line that includes `domain admins`.
3/4
We sat down with @likethecoins, director of intelligence at Red Canary, to chat about the Microsoft Exchange activity happening and share what we’re seeing. Check out what she had to say in the thread. #RCintel
Q1: What do we know about the adversaries exploiting the recent Exchange vulnerabilities? #RCintel
There’s a lot of confusion rn. Based on our visibility and that of researchers from Microsoft, FireEye, & others, there are at least 5 different clusters of activity that appear to be exploiting the vulnerabilities. -Katie Nickels #RCintel (1/2)
We’ve detected suspicious activity in multiple environments today, and, while we haven’t yet observed a payload, we’re concerned the activity may be the result of Exchange Server compromise. 1/7 #RCintel
What we’re observing is consistent with DLTminer precursor activity uncovered by @vmw_carbonblack in 2019, specifically its use of scheduled tasks to execute PowerShell and make external network connections. carbonblack.com/blog/cb-tau-te… 2/7
Prior to the Scheduled Task and PowerShell activity, we’re seeing the adversary leverage the IIS Worker process (w3wp.exe) to spawn the Command Processor in a manner that’s consistent with web shell activity. 3/7