Has conducted Kerberoasting attacks using a module from GitHub.1
Kerberoasting T1558.003
- Tactic
- Credential Access
- Platform
- Windows
- Version
- 1.3
- Created
- 11 February 2020
- Last modified
- 24 October 2025
- Contributor
- Praetorian
Adversaries may abuse a valid Kerberos ticket-granting ticket (TGT) or sniff network traffic to obtain a ticket-granting service (TGS) ticket that may be vulnerable to Brute Force.[1][2]
Kerberoasting MITRE reference T1558.003
3 groups have been recorded using this technique. Newest first; each entry carries MITRE’s procedure text and a link to the group’s full record. Click a name to filter the rules below.
Has used Rubeus, MimiKatz Kerberos module, and the Invoke-Kerberoast cmdlet to steal AES hashes.12345
Has used Kerberoasting PowerShell commands such as, Invoke-Kerberoast for credential access and to enable lateral movement.12
All 3 groups for this technique
3 campaigns have been recorded using this technique. Listed newest first; dates are year-granularity and attribution is MITRE’s.
Leviathan used Kerberoasting techniques during Leviathan Australian Intrusions.1
During the SolarWinds Compromise, APT29 obtained Ticket Granting Service (TGS) tickets for Active Directory Service Principle Names to crack offline.1
During Operation Wocao, threat actors used PowerSploit's Invoke-Kerberoast module to request encrypted service tickets and bruteforce the passwords of Windows service accounts offline.1
All 3 campaigns for this technique
6 software entries are documented implementing this technique. MITRE files each as a tool or as malware; newest first, then by how many groups carry them.
Can use the KerberosRequestorSecurityToken.GetRequest method to request kerberoastable service tickets.1
Can decode Kerberos 5 tickets and convert it to hashcat format for subsequent cracking.1
Contains a module to conduct Kerberoasting.1
Uses PowerSploit's Invoke-Kerberoast to request service tickets and return crackable ticket hashes.1
Modules like GetUserSPNs can be used to get Service Principal Names (SPNs) for user accounts. The output is formatted to be compatible with cracking tools like John the Ripper and Hashcat.1
PowerSploit's Invoke-Kerberoast module can request service tickets and return crackable ticket hashes.12
All 6 software entries for this technique
Offense vs defense T1558.003
Is defensive coverage keeping up with adversary use? Eight counts, each ranked against all 697 ATT&CK techniques. Attack sits left, defense right, so a shape leaning left means adversaries are better documented here than defenders are equipped. Hover any spoke for its percentile and the share of techniques that have more. The timeline below shows when each side arrived.
How it got here
Adversary activity (campaign spans) over cumulative rule output. Each source is plotted independently from zero, so neither line includes the other. Campaign dates are year-granularity.
Kerberoasting detection strategy DET0157
MITRE names one behaviour worth catching for this technique and breaks it into 1 analytic, one per platform. Each carries the log sources it needs and the fields you tune per environment.
Detect Kerberoasting Attempts (T1558.003)
AN0444 · Windows
Detects Kerberoasting attempts by monitoring for anomalous Kerberos TGS requests (Event ID 4769) with RC4 encryption (etype 0x17), accounts requesting an unusual number of service tickets in a short period, or service accounts targeted outside normal usage baselines. Also correlates suspicious process activity (e.g., Mimikatz invoking LSASS access) with Kerberos ticket anomalies.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Process AccessDC0035 | WinEventLog:Sysmon | EventCode=10 |
| Logon Session CreationDC0067 | WinEventLog:Security | EventCode=4624, 4648 |
| Active Directory Credential RequestDC0084 | WinEventLog:Security | EventCode=4769 |
| Logon Session MetadataDC0088 | WinEventLog:Security | EventCode=4672 |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| TGSRequestThreshold | Number of TGS requests per account within a defined window; higher than baseline may indicate Kerberoasting. |
| AllowedEncryptionTypes | Permitted Kerberos encryption algorithms; RC4 (etype 0x17) usage in modern environments is suspicious. |
| ServiceAccountBaselines | Expected SPNs requested by specific accounts; anomalies may indicate adversarial targeting. |
| TimeWindow | Correlation window for bursts of TGS requests; adjustable to reduce false positives. |
Enable AES Kerberos encryption (or another stronger encryption algorithm), rather than RC4, where possible.
Ensure strong password length (ideally 25+ characters) and complexity for service accounts and that these passwords periodically expire. Also consider using Group Managed Service Accounts or another third party product such as password vaulting.
Limit service accounts to minimal required privileges, including membership in privileged groups such as Domain Administrators.
Tests from Atomic Red Team (MIT licence) · technique definition