Windows: Uncommon Process Access to Microsoft Teams Cookies or Local Storage leveldb

Alerts on access to Teams Cookies or leveldb files by processes other than Teams.exe on Windows.

FreeReviewedSigma · Medium · v2
Product
windows
Category
file_access
Author
@SerkinValery (SigmaHQ), DRL 1.1
Published
2024-07-22
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 flags attempts by a process other than Teams.exe to access sensitive Microsoft Teams data locations, specifically Cookies and Local Storage leveldb files. Attackers may target these files to obtain authentication material or session-related data. The detection relies on Windows file access telemetry that includes the accessed path (FileName) and the calling process image (Image).

Related detections9 linkedT1528 — drag to rearrange
Malicious OAuth Application Granted Full Mailbox and EWS Permissions (via m365)
Suspicious GAM OAuth Token Enumeration via Process Creation
Suspicious Entra ID Device Code Flow Authentication
Suspicious Delegated Permission Grant to Entra Agent Access Scope via Azure Audit Logs
Suspicious OAuth Application Registration with Localhost Reply URL via Azure AD
Malicious PRT Token Forging via AADInternals (via ps_script)
Possible VMware Workspace ONE SSRF via instanceHealth hostName At-Injection (via webserver)
Suspicious Entra Device Code Authentication with Office Client and Automated User Agent
Suspicious Access to Kubernetes Service Account Token via Curl or Wget (via process_creation)
Windows: Uncommon Process Access to Microsoft Teams Cookies or Local Storage leveldb
Pivot detection · T1528 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. 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.