Windows Credentials from Password Stores Chrome Login Data Access

name: Windows Credentials from Password Stores Chrome Login Data Access
id: 0d32ba37-80fc-4429-809c-0ba15801aeaf
version: 23
creation_date: '2023-05-02'
modification_date: '2026-07-08'
author: Teoderick Contreras, Splunk
status: production
type: Anomaly
description: |-
    The following analytic identifies non-Chrome processes accessing the Chrome user data file "login data."
    This file is an SQLite database containing sensitive information, including saved passwords.
    The detection leverages Windows Security Event logs, specifically event code 4663, to monitor access attempts.
    This activity is significant as it may indicate attempts by threat actors to extract and decrypt stored passwords, posing a risk to user credentials.
    If confirmed malicious, attackers could gain unauthorized access to sensitive accounts and escalate their privileges within the environment.
data_source:
    - Windows Event Log Security 4663
search: |
    `wineventlog_security`
    EventCode=4663
    object_file_path="*\\AppData\\Local\\Google\\Chrome\\User Data\\Default\\Login Data"
    NOT process_path IN (
        "*:\\Windows\\explorer.exe",
        "*:\\Windows\\System32\\dllhost.exe",
        "*\\AppData\\Local\\Google\\Chrome Beta\\Application\\chrome.exe",
        "*\\AppData\\Local\\Google\\Chrome Dev\\Application\\chrome.exe",
        "*\\AppData\\Local\\Google\\Chrome SxS\\Application\\chrome.exe",
        "*\\AppData\\Local\\Google\\Chrome Unstable\\Application\\chrome.exe",
        "*\\AppData\\Local\\Google\\Chrome\\Application\\chrome.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_login_data_access_filter`
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: |-
    The chrome uninstaller will access these set of files and folders. Filter as needed.
references:
    - https://malpedia.caad.fkie.fraunhofer.de/details/win.redline_stealer
intermediate_findings:
    entities:
        - field: dest
          type: system
          score: 20
          message: A non-chrome process $process_name$ accessing Chrome "Login Data" file on $dest$
analytic_story:
    - StealC Stealer
    - DarkGate Malware
    - Malicious Inno Setup Loader
    - NjRAT
    - Phemedrone Stealer
    - Salt Typhoon
    - Amadey
    - Earth Alux
    - Warzone RAT
    - Quasar RAT
    - PXA Stealer
    - RedLine Stealer
    - SnappyBee
    - Meduza Stealer
    - Braodo Stealer
    - MoonPeak
    - Snake Keylogger
    - China-Nexus Threat Activity
    - 0bj3ctivity Stealer
    - Lokibot
    - Scattered Lapsus$ Hunters
    - BlankGrabber Stealer
    - VIP Keylogger
    - Salat Stealer
    - Phantom Stealer
asset_type: Endpoint
mitre_attack_id:
    - T1012
product:
    - Splunk Enterprise
    - Splunk Enterprise Security
    - Splunk Cloud
category: endpoint
security_domain: endpoint