Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
meltedinhex/hunting-kerberoasting-and-ticket-attacksDFIR and threat hunting

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-attacks

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
UaWJuFyrzq…xcWKxKCQ==The CLI checks the SHA-256 and the signature before it writes a file.
Package72762240…59aedf88
727622403647…c59159aedf884 files · ⁦3.0 KB⁩
ScanMedium2 findings
  • Executable script shipped with the skillscripts/analyst.py
  • Links to outside domains
See the full scan
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/hunting-kerberoasting-and-ticket-attacks@da7600a

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

bash
python scripts/analyst.py hunt 4769_events.csv

Flags 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.md for the hunter.
  • ATT&CK T1558.003 and Event 4769 docs (linked in frontmatter).

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumFile · Executable script shipped with the skillscripts/analyst.py
  2. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v1.0.0Nov 13, 2026da7600a72762240Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login