Name:Windows User Profile Binary Terminating Process Via Taskkill id:9bb17e12-719b-4158-adec-e002879f42aa version:1 date:None author:Onur Mustafa Erdogan, Splunk status:production type:TTP Description:The following analytic detects taskkill.exe being launched with a process ID (/pid) argument by an executable that resides directly within
a user profile folder, such as the Downloads or Desktop folder. Filtering for parent processes located two to three directory levels deep
under root folder. This activity is significant because browser hijackers and adware droppers executed from the Downloads folder forcefully
terminate the running browser by PID so that they can modify its profile and relaunch it with their own settings. If confirmed malicious, this
could allow an attacker to tamper with browser preference files, side-load extensions and redirect the victim's browsing traffic.
Data_source:
-Sysmon EventID 1
-Windows Event Log Security 4688
-CrowdStrike ProcessRollup2
search:| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time) as lastTime
from datamodel=Endpoint.Processes where
( Processes.process_name=taskkill.exe OR Processes.original_file_name=taskkill.exe ) Processes.process IN ("* /pid *", "* -pid *") Processes.parent_process_path="*:\\Users\\*"
how_to_implement:The detection is based on data that originates from Endpoint Detection and Response (EDR) agents. These agents are designed to provide
security-related telemetry from the endpoints where the agent is installed. To implement this search, you must ingest logs that contain
the process GUID, process name, and parent process. Additionally, you must ingest complete command-line executions. These logs must be
processed using the appropriate Splunk Technology Add-ons that are specific to the EDR product. The logs must also be mapped to the
`Processes` node of the `Endpoint` data model. Use the Splunk Common Information Model (CIM) to normalize the field names and speed up
the data modeling process. known_false_positives:Portable applications, installers and updaters executed from a user's Downloads or Desktop folder may legitimately use taskkill.exe to
close a running instance of themselves or another application. Filter as needed based on the parent process name or path. References: -https://www.joesandbox.com/analysis/1965188/0/html -https://www.gdatasoftware.com/blog/2025/11/38298-learning-about-browser-hijacking -https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/taskkill drilldown_searches: name:'View the detection results for - "$dest$" and "$user$"' search:'%original_detection_search% | search dest = "$dest$" user = "$user$"' earliest_offset:'$info_min_time$' latest_offset:'$info_max_time$' name:'View risk events for the last 7 days for - "$dest$" and "$user$"' search:'| from datamodel Risk.All_Risk | search normalized_risk_object IN ("$dest$", "$user$") | stats count min(_time) as firstTime max(_time) as lastTime values(search_name) as "Search Name" values(risk_message) as "Risk Message" values(analyticstories) as "Analytic Stories" values(annotations._all) as "Annotations" values(annotations.mitre_attack.mitre_tactic) as "ATT&CK Tactics" by normalized_risk_object | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)`' earliest_offset:'7d' latest_offset:'0' analytic_story:['Browser Hijacking', 'Living Off The Land']