Windows Credentials from Password Stores Chrome LocalState Access
The following analytic identifies a non-chrome process accessing Chrome user data "local state" file. This file stores various settings and information related to the browser's operation on your computer. Threat actor, adversaries and malware author also abused this file to attempt to extract the encrypted master key to decrypt password saved in chrome browser. This anomaly detection can be a good pivot of analysis for suspicious process aside from chrome.exe and explorer.exe executable.
- Type: Anomaly
Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
- Last Updated: 2023-04-26
- Author: Teoderick Contreras, Splunk
- ID: 3b1d09a8-a26f-473e-a510-6c6613573657
Kill Chain Phase
- CIS 10
1 2 3 4 5 `wineventlog_security` EventCode=4663 object_file_path="*\\AppData\\Local\\Google\\Chrome\\User Data\\Local State" NOT (process_name IN ("*\\chrome.exe","*:\\Windows\\explorer.exe")) | stats count min(_time) as firstTime max(_time) as lastTime by object_file_name object_file_path process_name process_path process_id EventCode dest | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)` | `windows_credentials_from_password_stores_chrome_localstate_access_filter`
The SPL above uses the following Macros:
windows_credentials_from_password_stores_chrome_localstate_access_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 must ingest Windows Security Event logs and track event code 4663. For 4663, enable "Audit Object Access" in Group Policy. Then check the two boxes listed for both "Success" and "Failure."
Known False Positives
Uninstall chrome application may access this file and folder path to removed chrome installation in target host. Filter is needed.
Associated Analytic Story
|25.0||50||50||A non-chrome process $process_name$ accessing "Chrome\User Data\Local State" file on $dest$|
The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.
Replay any dataset to Splunk Enterprise by using our
replay.py tool or the UI.
Alternatively you can replay a dataset into a Splunk Attack Range
source | version: 1