Trickbot is a Trojan that was initially used to steal banking credentials. Now this malware is known in Microsoft Windows operating systems where it targets Microsoft Defender to prevent its detection and removal, then steals credentials using multi-component modules that collect and exfiltrate data.
These searches detect and investigate unusual activities that might relate to Trickbot, including looking for file writes associated with its payload, process injection, shellcode execution, and data collection.
How to use Splunk software for this use case
To deploy this use case, make sure that you have the Splunk ES Content Updates installed on your Splunk Enterprise Security deployment. This extensive content library empowers you to deploy out-of-the-box security detections and analytic stories to enhance your investigations and improve your security posture. If you do not have Splunk Enterprise Security, these detections will still give you an idea of what you can accomplish with SPL in the Splunk platform or with the free app, Splunk Security Essentials.
Some of the detections that can help you with this use case include:
- Account discovery With Net App
- Attempt to stop security service
- Cobalt Strike named pipes
- Executable file written in administrative SMB share
- Executables or script creation in suspicious path
- Mshta spawning Rundll32 or Regsvr32 process
- Office application spawn rundll32 process
- Office document executing macro code
- Office product spawn CMD process
- Office product spawning CertUtil
- Powershell remote thread to known Windows process
- Schedule task with Rundll32 command trigger
- Scheduled task deleted or created via CMD
- Suspicious process file path
- Suspicious Rundll32 StartW
- Trickbot named pipe
- Wermgr process connecting to IP check web services
- Wermgr process create executable file
- Wermgr process spawned CMD or Powershell process
Splunk OnDemand Services: Use these credit-based services for direct access to Splunk technical consultants with a variety of technical services from a pre-defined catalog. Most customers have OnDemand Services per their license support plan. Engage the ODS team at OnDemand-Inquires@splunk.
In addition, these Splunk resources might help you understand and implement this use case:
- Blog: Threat Hunting with Splunk: Hands-on Tutorials for the Active Hunter
- If you are a Splunk Enterprise Security customer, you can also get help from the Security Research team's support options on GitHub.