The following analytic identifies the Windows Explorer process with a URL within the command-line. Explorer.exe is known Windows process that handles start menu, taskbar, desktop and file manager. Many adversaries abuse this process, like DCRat malware, where it attempts to open the URL with the default browser application on the target host by putting the URL as a parameter on explorer.exe process. This anomaly detection might be a good pivot to check which user and how this process was executed, what is the parent process and what is the URL link. This technique is not commonly used to open an URL.
- Type: TTP
Product: Splunk Behavioral Analytics
- Last Updated: 2022-09-13
- Author: Michael Haag, Splunk
- ID: 695bfad6-9662-4f9e-a576-bf02a951aa60
Kill Chain Phase
- Command and Control
- CIS 10
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 $main = from source | eval timestamp = time | eval metadata_uid = metadata.uid | eval process_pid = process.pid | eval process_file = process.file | eval process_file_path = process_file.path | eval process_file_name = lower(process_file.name) | eval process_cmd_line = process.cmd_line | eval actor_user = actor.user | eval actor_user_name = actor_user.name | eval actor_process = actor.process | eval actor_process_pid = actor_process.pid | eval actor_process_file = actor_process.file | eval actor_process_file_path = actor_process_file.path | eval actor_process_file_name = actor_process_file.name | eval device_hostname = device.hostname | where (process_cmd_line LIKE "%https://%" OR process_cmd_line LIKE "%http://%") AND process_file_name="explorer.exe" --finding_report--
The SPL above uses the following Macros:
windows_ingress_tool_transfer_using_explorer_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
List of fields required to use this analytic.
How To Implement
To successfully implement this search you need to be ingesting information on process that include the name of the process responsible for the changes from your endpoints.
Known False Positives
False positives may be present based on legitimate applications or third party utilities. Filter out any additional parent process names.
Associated Analytic Story
|25.0||50||50||An instance of $parent_process_name$ spawning $process_name$ was identified on endpoint $dest_device_id$ by user $dest_user_id$ attempting to access a remote destination to download an additional payload.|
The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.
source | version: 1