ATT&CK coverage › Technique

Browser Session Hijacking T1185

Adversaries may take advantage of security vulnerabilities and inherent functionality in browser software to change content, modify user-behaviors, and intercept information as part of various browser session hijacking techniques.

Events covered

3 catalog events are tagged with this technique by at least one rule.

ProviderEvent IDTitle
Sysmon1Process creation
Sysmon13RegistryEvent (Value Set)
Security-Auditing4688A new process has been created.

Authoring guide

Patterns shared across the 5 rules above: which fields they filter on, what specific values they look for, and what they exclude. Field names are normalized across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.

Fields filtered most (6 distinct)

The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.

FieldRulesHowSample values
CommandLine3match 2, in 1 --remote-debugging-, -start-debugger-server, --user-data-dir, --headless, --remote-debugging-
registry_path2eq 2"*\\Google\\Update*", "*\\Google\\Chrome\\ExtensionInstallAllowlist*"
Image1ends_with 1\firefox.exe
process_name1in 1"firefox.exe", "brave.exe", "chrome.exe"
Details1eq 10x00000000, 0x00000001
registry_value_name1eq 1, in 1"UpdateDefault", "Update{8A69D345-D564-463C-AFF1-A69D9E530F96}", "DisableAutoUpdateChecksCheckboxValue"

Top indicator values (21 distinct)

Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique.

FieldKindValueRules (here)Corpus reach
CommandLinematch -start-debugger-server1
Imageends_with\firefox.exe16
CommandLinematch --remote-debugging-1
CommandLinematch--user-data-dir1
CommandLinematch--headless15
CommandLinematch--remote-debugging-1
CommandLinein"*--mute-audio*"1
process_namein"brave.exe"1
process_namein"firefox.exe"1
process_namein"msedge.exe"1
CommandLinein"*--no-de-elevate*"1
CommandLinein"*--do-not-de-elevate*"1
process_namein"chrome.exe"1
registry_value_namein"AutoUpdateCheckPeriodMinutes"1
registry_value_namein"UpdateDefault"1
registry_value_namein"Update{8A69D345-D564-463C-AFF1-A69D9E530F96}"1
Detailseq0x0000000018
registry_value_nameeq"DisableAutoUpdateChecksCheckboxValue"1
registry_patheq"*\\Google\\Update*"1
Detailseq0x00000001112

Common exclusions (8 distinct)

Field/operator/value combinations that rules under this technique routinely exclude (top-level not() clauses). These are the false-positive paths the community has learned to filter out. A new rule that ignores the high-count entries here will likely fire on the same noisy paths.

FieldKindValueRules excluding
parent_process_namein"msedge.exe"1
ParentImagein"C:\\Program Files*"1
ParentImagein"C:\\Windows\\System32\\*"1
ParentImagein"C:\\Windows\\SysWow64\\*"1
parent_process_namein"chrome.exe"1
parent_process_namein"brave.exe"1
parent_process_namein"explorer.exe"1
parent_process_namein"firefox.exe"1

Rules under this technique

Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.

Sigma 2 rules

Splunk 3 rules