Windows Security 4663: Access to Microsoft Teams token and local storage files

Identifies non-Teams.exe processes accessing Microsoft Teams cookies or local storage objects on Windows (Event 4663).

FreeReviewedSigma · High · v2
Product
windows
Service
security
Author
@SerkinValery (SigmaHQ), DRL 1.1
Published
2022-09-16
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 Windows object access events where the accessed object name contains paths associated with Microsoft Teams cookies and Local Storage (leveldb). Adversaries may target these areas to obtain authentication/session tokens or persist via locally stored data. It relies on Security event 4663 telemetry and filters for accesses involving Teams.exe while matching the specific object name substrings.

Related detections9 linkedT1528 — drag to rearrange
Suspicious Microsoft Entra Device Code Authentication Flow
Suspicious Google Workspace OAuth Authorization for Chrome Web Store Scope via Token Audit
Suspicious OAuth Application Consent Grant via Azure Audit Logs
Suspicious OAuth Application Consent Granted High Privilege Mail Scopes (via m365)
Suspicious Token Request Using Microsoft Authentication Broker Client to Obtain Primary Refresh Token (via azure)
Suspicious Salesforce Connected App OAuth Authorization from VPN Egress
Suspicious M365 Device Code Authentication Flow via m365
Possible Illicit Consent Grant to OAuth Application via Azure AD
Suspicious Device Code Authentication via Microsoft Authentication Broker
Windows Security 4663: Access to Microsoft Teams token and local storage files
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.