1/x For the past couple of weeks, #IcedID has been hitting hard, with post-exploitation activities beginning within ~1 hour from the initial infection.
Here are some TTPs and IOCs from these post-exploitation activities that will keep defenders ready.
🧵👇
2/x 🎯TTPs
➡️IcedID use of VNC
💡Over port 8080
➡️Multiple Cobalt Strike DLLs on disk
💡Overused directories - "C:\Windows\Tasks" & - "%user%\AppData\Local\Temp"
➡️Heavy use of PowerShell
💡Downloading payloads, exec PowerShell Cobalt Strike Loaders & other processes
3/x ➡️Used multiple privilege escalation methods
💡zerologon, Invoke-Kerberoast, Invoke-EnvBypass
➡️Reverse proxy via Cobalt Strike and then RDPing into the network
➡️Invoke-BloodHound & Invoke-ShareFinder for network and open-shares discovery
#BruteRatel is difficult to detect without having access to WinAPI, NTAPI, and Syscalls as everything is done in memory. This hurts our efforts to hunt across behaviors upon executing the BRC4 payload.
Although all hope is not lost,there are some good indicators in the wires🧵👇
Looking into the unencrypted network traffic, there are some indicators we can hunt for and create detections based on the default BRC4 profile:
➡️Multiple POST requests against certain destinations
➡️All responses (apart from initial check-in) have 0 content with 200 status👇
➡️Base64 encoded body and encrypted upon deobfuscation
➡️Default user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36
As a defender, I read reports to stay up to date with recent threats reported by others in the industry. It also helps me generate ideas for future research, threat hunting, detection, or a deeper dive into TA's infra.
This is what I am looking for when I read them🧵
1/11
I'll use a couple of good and one not-so-good report example from this week's awesome collection of reports from thisweekin4n6.com.
🔥Useful reports🔥
- Bitter APT adds Bangladesh to their targets (@TalosSecurity)
- Cozy Smuggled Into The Box (@cluster25_io)
2/11
The above reports are jam-packed with tactical and operationally actionable threat intelligence. They both provide a solid description of the threat actor's activities as well as how the intrusion unfolded. Finally, they feature detections in the form of Yara/Sigma rules.
3/11
Last week, @TheDFIRReport received a MS-themed phishing email with an HTML attachment. The email made a significant effort to appear legitimate.
When we open the file, the code renders into what appears to be an HTML page mirroring the official MS account login page.
1/🧵
@TheDFIRReport Looking into the code of the HTML file, we notice a couple of layers of obfuscation. Without much effort, we decoded the content. The script element contains URL and Base64 encoded code that will be executed by the browser. 2/
@TheDFIRReport When the user opens the HTML file, the browser will initiate a GET request to alufohaicement[.]com/monochrome.js containing the victim's and attacker's email addresses passed as base64 encoded parameters to a PHP script configured by the attacker. 3/