Operator On The Wire
Join
← Back to Knowledge Base
BLUE TEAM / THREAT HUNT / WINDOWS / PRIVILEGE ESCALATION

Token Abuse

This note documents detection patterns related to Token Abuse within Windows environments.


Direct Indicators

LogEvent IDMeaningForensic ValueNotes
Security4672Special privileges assignedCriticalElevated token granted to session.
Security4688Process creationCriticalDetects token abuse tooling and spawned elevated processes.
Sysmon1Process creationCriticalBest lineage source for token manipulation chains.
Security4648Explicit credentials usedHighOften adjacent to token abuse workflows.
Sysmon10Process accessHighSensitive handle access before token theft.
Security4624Successful logonHighSession origin for token abuse context.

Indirect Indicators

IndicatorWhat To Look ForForensic ValueNotes
Non-admin spawns admin processPrivilege jump without expected pathCriticalStrong token abuse clue.
SeImpersonate present before escalationPotato-style preconditionCriticalVery common privesc chain.
Sensitive process accessedToken theft from SYSTEM processCriticalHigh-value indicator.
Duplicate elevated shellscmd / powershell with SYSTEMCriticalCommon outcome.
Short-lived elevated processFast abuse then cleanupHighOperator behavior.
Service token followed by shellSYSTEM inheritanceHighCommon pattern.

Common Tools

ToolUsage
mimikatzToken impersonation
incognitoToken stealing
PowerShellToken duplication helpers
potato familySeImpersonate exploitation

Relevant Artifacts

  • Security Event IDs 4672, 4688, 4648, 4624
  • Sysmon Event IDs 1, 10
  • Process integrity levels
  • Token privilege fields
  • EDR token lineage
  • Prefetch for abuse tooling

MITRE ATT&CK References

  • T1134 Access Token Manipulation

Decision Tree

  1. Which account/session?

    • User
    • Service
    • SYSTEM source
  2. Which privilege present?

    • SeImpersonate
    • SeAssignPrimaryToken
    • SeDebug
  3. Elevated child appears?

    • cmd
    • powershell
    • service action
  4. Sensitive process touched?

    • lsass
    • winlogon
    • services
  5. Expand:

    • Adjacent privesc
    • Named pipes
    • Service abuse
  6. Scope:

    • Single escalation
    • Repeated abuse
    • Toolkit chain

Example Detection Templates

KQL

SecurityEvent
| where EventID == 4672
| project TimeGenerated, Computer, Account, Privileges
Sysmon
| where EventID == 10
| project TimeGenerated, Computer, SourceImage, TargetImage, GrantedAccess

EQL

process where event.code == "4672"
sequence by host.name with maxspan=5m
  [ any where event.code == "4672" ]
  [ process where process.name in ("cmd.exe","powershell.exe") ]

Sigma

title: Token Abuse Detection
id: 1c5e7a20-token-abuse
status: experimental
description: Detects suspicious privilege token abuse patterns
references:
  - https://attack.mitre.org/
author: Vergil
date: 2026-03-07
logsource:
  product: windows
  service: security
detection:
  selection:
    EventID: 4672
  condition: selection
fields:
  - Account
  - Privileges
falsepositives:
  - Legitimate admin sessions
level: high
tags:
  - attack.privilege_escalation
  - attack.t1134

Mitigation & Hardening

Control AreaMitigationEffectivenessNotes
Alert on unexpected 4672Watch non-admin hostsCriticalStrong signal
Restrict SeImpersonateReduce escalation surfaceCriticalKey hardening
Process access monitoringDetect token theft setupHighStrong precursor
Integrity trackingSpot sudden elevationHighValuable enrichment
EDR lineageTrack token inheritanceCriticalBest operational visibility