huntrule

Windows Process Creation: Command Line Targets Microsoft Teams Cookies or LevelDB

Alerts when non-Teams processes reference Microsoft Teams Cookies or Local Storage leveldb paths in their command line.

FreeReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
@SerkinValery (SigmaHQ), DRL 1.1
Published
2022-09-16
Updated
2026-07-30
AnalysisDetection

ATT&CK techniques

Cred Access

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule flags Windows process creation events where the command line contains paths to Microsoft Teams Cookies or the Local Storage leveldb directory. Accessing these locations can indicate credential or session token harvesting from Teams, which may expose authentication-related data for logged-in accounts. The detection relies on process creation telemetry and command-line/path substring matching, excluding events originating from the Teams executable.

Reporting behind it

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 Process Creation: Command Line Targets Microsoft Teams Cookies or LevelDB
Pivot detection · T1528 · 9 related

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