Skip to content

created a module for targetedkerbroast - #1042

Closed
liyander wants to merge 1 commit into
Pennyw0rth:mainfrom
liyander:main
Closed

liyander wants to merge 1 commit into
Pennyw0rth:mainfrom
liyander:main

Conversation

@liyander

Copy link
Copy Markdown

Feature: Add Targeted Kerberoasting Module

Description

This PR adds a new module targeted_kerberoast to NetExec. This module implements the functionality of the standalone targetedKerberoast.py tool directly within NetExec, allowing for automated SPN manipulation and Kerberoasting.

Features:

  • Targeted Roasting: Can target a specific user (-o USER=username) or automatically iterate through all enabled user accounts in the domain.
  • SPN Management: Checks if a user already has a Service Principal Name (SPN).
    • If an SPN exists, it roasts it directly.
    • If no SPN exists, it adds a temporary SPN, performs the roast, and then removes the SPN to clean up.
  • Flexible Authentication: Leverages NetExec's existing connection handling (supports NTLM, Kerberos, etc.).
  • Robustness:
    • Uses ldap3 for reliable LDAP modifications.
    • Explicitly handles KDC resolution using the target IP to avoid DNS issues.
    • Filters out computer accounts and disabled accounts when running against all users.

Usage

Target a specific user:

nxc ldap <target> -u <user> -p <password> -M targeted_kerberoast -o USER=<target_user>

Target all users:

nxc ldap <target> -u <user> -p <password> -M targeted_kerberoast

@liyander

Copy link
Copy Markdown
Author

i have shown the functionality in the video

nxc_updated.mp4

@NeffIsBack

Copy link
Copy Markdown
Member

Hey thanks for your work!
However, i fear this is duplicate to #840.

@liyander

Copy link
Copy Markdown
Author

Thanks for pointing that out — I missed #840.

I’ll review that issue/PR more closely. If there’s still a gap (e.g., UX, OPSEC controls, or BloodHound-driven targeting), I’m happy to refactor my changes to complement it rather than duplicate functionality.

@NeffIsBack

Copy link
Copy Markdown
Member

Thanks for pointing that out — I missed #840.

I’ll review that issue/PR more closely. If there’s still a gap (e.g., UX, OPSEC controls, or BloodHound-driven targeting), I’m happy to refactor my changes to complement it rather than duplicate functionality.

Sounds great 👍

@NeffIsBack NeffIsBack added the duplicate This issue or pull request already exists label Dec 18, 2025
@liyander liyander closed this by deleting the head repository Dec 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

duplicate This issue or pull request already exists

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants