Operator On The Wire
Join
← Back to Knowledge Base
BLUE TEAM / THREAT HUNT / ACTIVE DIRECTORY / LATERAL MOVEMENT / PASS

Overpass the Hash

This note documents detection patterns related to Overpass the Hash within Active Directory environments.


Direct Indicators

LogEvent IDMeaningForensic ValueNotes
Security4768Kerberos TGT requestCriticalOverpass-the-Hash converts an NTLM hash into a Kerberos TGT request. Look for unusual TGT requests originating from workstations using NTLM-derived credentials. Communication with the DC (TCP/UDP port 88) from an unusual process (e.g. Rubeus.exe) can serve as an indicator of a potential Overpass-the-Hash attack.
Security4769Kerberos service ticket requestHighService ticket requests following suspicious TGT generation.
Security4624Successful logonHighLogonType 3 or 9 sessions may appear when Kerberos authentication is performed using injected credentials.
Security4648Explicit credentials usedHighExplicit credential usage may appear when attacker initiates authentication using manipulated credential material.
Security4672Special privileges assignedHighPrivileged session may occur if attacker authenticates using privileged account hash.
Sysmon10Process accessed LSASSCriticalLSASS access used to extract NTLM hashes prior to ticket generation.
Sysmon1Process creationHighExecution of tools such as Mimikatz or Rubeus performing sekurlsa::pth or Kerberos ticket requests.

Indirect Indicators

IndicatorWhat To Look ForForensic ValueNotes
Kerberos authentication from unusual workstationAccount requesting TGT from host it normally does not useHighPossible attacker-controlled host.
TGT request after LSASS memory accessProcess accesses LSASS followed by Kerberos authenticationCriticalStrong indicator of credential extraction followed by Overpass-the-Hash.
Rapid service ticket requests after TGT issuanceMultiple 4769 events shortly after 4768HighIndicates attacker leveraging new Kerberos session.
Authentication to multiple systems quicklyAccount authenticating across hostsHighPossible lateral movement.
Execution of credential manipulation toolsProcesses like mimikatz.exe, rubeus.exeCriticalDirect evidence of credential abuse.

Common Tools

ToolUsage
MimikatzPerforms Overpass-the-Hash using sekurlsa::pth to request Kerberos TGTs.
RubeusRequests Kerberos tickets using NTLM hashes.
ImpacketgetTGT.py uses NTLM hash to request Kerberos ticket.
KekeoKerberos manipulation toolkit.
Invoke-MimikatzPowerShell wrapper executing credential abuse techniques.

Relevant Artifacts

  • Domain controller Security logs (4768, 4769, 4624)
  • Kerberos operational logs
  • Sysmon logs (1, 10)
  • LSASS memory artifacts
  • EDR telemetry detecting credential dumping tools
  • Network authentication telemetry
  • Prefetch artifacts showing execution of Mimikatz or Rubeus
  • Kerberos ticket cache analysis

MITRE ATT&CK References

  • T1550 Use Alternate Authentication Material
  • T1550.003 Pass the Ticket
  • T1558 Steal or Forge Kerberos Tickets
  • T1078 Valid Accounts

Decision Tree

  1. Is the suspicious event present?
    • Identify Kerberos TGT request events (4768) from unusual hosts.
  2. What host generated the event?
    • Determine workstation performing authentication.
  3. Is the account expected to perform this action?
    • Investigate authentication patterns and workstation relationships.
  4. Pivot:
    • Source host → inspect LSASS access events or execution of Mimikatz / Rubeus.
    • Account → review privileges associated with the session.
    • Network → analyze service ticket requests following TGT issuance.
  5. Confirm exploitation
    • Determine whether NTLM hash was used to request Kerberos authentication.

Example Detection Templates

KQL

SecurityEvent
| where EventID == 4768
| summarize count() by TargetUserName, IpAddress, bin(TimeGenerated, 5m)
SecurityEvent
| where EventID == 4769
| summarize count() by ServiceName, TargetUserName, IpAddress, bin(TimeGenerated, 5m)

EQL

any where event.code == "4768"

Sigma

title: Suspicious Kerberos TGT Request Activity
id: overpass-the-hash-detection
status: experimental
description: Detects suspicious Kerberos ticket granting ticket requests potentially indicating Overpass-the-Hash activity
logsource:
  product: windows
  service: security
detection:
  selection:
    EventID: 4768
  condition: selection
fields:
  - TargetUserName
  - IpAddress
falsepositives:
  - Legitimate Kerberos authentication
level: medium
tags:
  - attack.lateral_movement
  - attack.t1550

Splunk

index=main earliest=1690443407 latest=1690443544 source="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" (EventCode=3 dest_port=88 Image!=*lsass.exe) OR EventCode=1 | eventstats values(process) as process by process_id | where EventCode=3 | stats count by _time, Computer, dest_ip, dest_port, Image, process | fields - count

Mitigation & Hardening

Control AreaMitigationEffectivenessNotes
Credential protectionEnable Credential Guard and LSASS protectionCriticalPrevents hash extraction from memory.
Privileged access managementRestrict usage of high privilege accountsHighLimits value of stolen hashes.
Kerberos monitoringMonitor unusual TGT requests from workstationsHighDetects abnormal authentication patterns.
EDR monitoringDetect execution of credential manipulation toolsHighStops attacker tooling early.
Network segmentationLimit lateral movement across systemsHighReduces attack impact.