Name:Windows Chromium Session Restored With Crash Bubble Suppressed id:ff22a1c5-d30c-40c9-adc0-947ea51cc623 version:1 date:None author:Onur Mustafa Erdogan, Splunk status:production type:TTP Description:The following analytic detects a Chromium-based browser being launched with both the --hide-crash-restore-bubble and --restore-last-session
command-line flags by a process other than the browser itself. Focusing on browser command lines that silently restore the previous session
without showing the "Chrome didn't shut down correctly" notification. This activity is significant because browser hijackers and adware droppers
forcefully terminate the browser to tamper with its preference files, then relaunch it with these flags so that the victim does not notice the
interruption and lands on an attacker-controlled page. If confirmed malicious, this could indicate that the browser profile was modified to
hijack the default search engine, new tab page or to side-load a malicious extension.
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
NOT Processes.parent_process_name IN ("chrome.exe", "msedge.exe", "brave.exe") Processes.process_name IN ("chrome.exe", "msedge.exe", "brave.exe") Processes.process="*--hide-crash-restore-bubble*" Processes.process="*--restore-last-session*"
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:Browser automation and enterprise management or support tools may launch the browser with these flags to restore sessions silently. Filter
as needed based on the parent process. References: -https://www.joesandbox.com/analysis/1965188/0/html -https://www.gdatasoftware.com/blog/2025/11/38298-learning-about-browser-hijacking -https://peter.sh/experiments/chromium-command-line-switches/ 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']