hunting-kerberoasting-and-ticket-attacks
Hunts for Kerberoasting and related ticket attacks by analyzing Kerberos service
v1.0.03 installs+3 in 7 days24 StarsApache-2.0synced 10 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install meltedinhex/hunting-kerberoasting-and-ticket-attacksWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package72762240…59aedf88
727622403647…c59159aedf884 files · 3.0 KBScanMedium2 findings
- Executable script shipped with the skillscripts/analyst.py
- Links to outside domains
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/hunting-kerberoasting-and-ticket-attacks@da7600a
On this page
When to Use
- You have Kerberos service ticket request events (Event ID 4769) and want to detect Kerberoasting (bulk TGS requests with crackable RC4 encryption against service accounts).
- You are investigating AD credential-access activity.
Do not use this for AS-REP roasting (4768 with preauth disabled) — that is a related but separate hunt; this focuses on 4769 TGS requests.
Prerequisites
- Event ID 4769 records with account name, service name (SPN), ticket encryption type, and client address.
Workflow
Step 1: Flag weak-encryption ticket requests
python scripts/analyst.py hunt 4769_events.csvFlags tickets with encryption type 0x17 (RC4-HMAC) — the crackable type Kerberoasting prefers —
and computes per-account SPN request volume.
Step 2: Detect bulk SPN targeting
Surface accounts requesting tickets for many distinct SPNs in a short window (a single user enumerating service accounts).
Step 3: Confirm
Correlate with the requesting host and whether the account legitimately needs those services.
Step 4: Operationalize
Write a detection for RC4 4769 requests from non-machine accounts above a volume threshold.
Validation
- RC4 (
0x17) requests are distinguished from AES (0x11/0x12). - Per-account distinct-SPN counts identify bulk targeting.
- Findings map to ATT&CK T1558.003.
Pitfalls
- Legacy applications legitimately using RC4 — baseline before alerting.
- Failure code 0x0 (success) only; some logs include failures that skew counts.
- Service accounts with many SPNs producing benign volume — combine with encryption-type weakness.
References
- See
references/api-reference.mdfor the hunter. - ATT&CK T1558.003 and Event 4769 docs (linked in frontmatter).
Files in this version
references/11.2 KB
- api-reference.md1.2 KB
scripts/12.8 KB
- analyst.py2.8 KB
- LICENSE340 B
- SKILL.md2.7 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | Yes | Yes |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- MediumFile · Executable script shipped with the skillscripts/analyst.py
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v1.0.0 | Nov 13, 2026 | da7600a | 72762240 | Signed | – |
More from meltedinhex
All from this publisher- writing-yara-rules-from-reversed-codemeltedinhex/writing-yara-rules-from-reversed-code4
- validating-detections-with-atomic-testsmeltedinhex/validating-detections-with-atomic-tests4
- writing-suricata-and-snort-rulesmeltedinhex/writing-suricata-and-snort-rules3
- writing-sigma-detection-rulesmeltedinhex/writing-sigma-detection-rules3
More in DFIR and threat hunting
See the category- hunting-for-command-and-control-beaconingmukul975/hunting-for-command-and-control-beaconing5
- audit-context-buildingtrailofbits/audit-context-building4
- incident-response-forensicssecurityskills/incident-response-forensics3
- extracting-credentials-from-memory-dumpmukul975/extracting-credentials-from-memory-dump3
- analyzing-browser-forensics-with-hindsightmukul975/analyzing-browser-forensics-with-hindsight3
- forensics-ctfaeondave/forensics-ctf3
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login