This analytic identifies excessive usage of
taskkill.exe application. This application is commonly used by adversaries to evade detections by killing security product processes or even other processes to evade detection.
- Type: Anomaly
- Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
- Datamodel: Endpoint- Datasource: Splunk Add-on for Sysmon
- Last Updated: 2021-05-04
- Author: Teoderick Contreras, Splunk
- ID: fe5bca48-accb-11eb-a67c-acde48001122
Kill Chain Phase
1 2 3 4 5 6 7 | tstats `security_content_summariesonly` values(Processes.process) as process values(Processes.process_id) as process_id count min(_time) as firstTime max(_time) as lastTime from datamodel=Endpoint.Processes where Processes.process_name = "taskkill.exe" by Processes.parent_process_name Processes.process_name Processes.dest Processes.user _time span=1m | where count >=10 | `drop_dm_object_name(Processes)` | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)` | `excessive_usage_of_taskkill_filter`
The SPL above uses the following Macros:
Note that excessive_usage_of_taskkill_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
How To Implement
To successfully implement this search, you need to be ingesting logs with the process name, parent process, and command-line executions from your endpoints. If you are using Sysmon, you must have at least version 6.0.4 of the Sysmon TA. Tune and filter known instances where renamed taskkill.exe may be used.
Known False Positives
Unknown. Filter as needed.
Associated Analytic story
|28.0||40||70||Excessive usage of taskkill.exe with process id $process_id$ (more than 10 within 1m) has been detected on $dest$ with a parent process of $parent_process_name$.|
source | version: 1