Windows Security 4663: Uncommon Processes Access Browser Credential Store Files

Flags 4663 file access to browser credential stores (Chromium/Firefox) by processes outside common system/benign paths.

FreeReviewedSigma · Low · v5
Product
windows
Service
security
Author
Daniel Koifman (@Koifsec), Nasreddine Bencherchali (SigmaHQ), DRL 1.1
Published
2024-10-21
Updated
2026-07-31

ATT&CK techniques

Cred Access
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule identifies Windows file access events (EventID 4663) where a non-system, non-standard application process reads browser credential-related data paths. Accessing Chromium “User Data” login databases or Firefox cookie/history/key/login stores is a common prerequisite for credential theft. It relies on Windows Security audit telemetry for object name/file name matching plus process name exclusions to reduce benign hits.

Related detections9 linkedT1555.003 — drag to rearrange
Malicious Qilin Chrome Credential Harvesting Script Execution via IPScanner (via process_creation)
Malicious Browser Credential Dump File Drop by Phantom Stealer via file_event
Suspicious Chromium Browser Launch with Remote Debugging Port for Cookie Theft (via process_creation)
Malicious dllFake Stealer Execution from WindowsApps Directory (via process_creation)
Malicious macOS Stealer Staging to Users Shared Directory (via process_creation)
Possible Spectre Ops C2 Beacon via nico and yfat Query Parameters via proxy
Suspicious Browser Kiosk Mode Forcing Credential Entry via process_creation
Malicious Live Ledger Stealer Execution via Ledger Lives Masquerade via process_creation
Suspicious Access to Chrome Encrypted Preference MAC Registry Values (via registry_set)
Windows Security 4663: Uncommon Processes Access Browser Credential Store Files
Pivot detection · T1555.003 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.