ad-delegation-abuse
Abuse Kerberos delegation to impersonate users and take over hosts — unconstrained, constrained (S4U2Self/S4U2Proxy), and resource-based (RBCD), including the coercion → NTLM-relay-to-LDAP → RBCD chain. Load in an AD environment when BloodHound/enum shows delegation rights, a machine account you con
v2026.10.14-ee0e0c53 installazioni+3 in 7 giorni27 StelleMITsincronizzato 22 ore fa
Installa
Non hai ancora la CLI di NotHoly? Installala prima.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/ad-delegation-abuseScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchettod588789f…55547856
d588789fdd4c…1fb5555478561 file · 2.0 KBScansioneBassonessuna segnalazione
Sorgentegithub.com/NoorQureshi/security-skills/tree/main/skills/ad/ad-delegation-abuse@ee0e0c5
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
When it applies
An AD engagement where enumeration (BloodHound, nxc, LDAP) shows a delegation primitive: a host
trusted for unconstrained delegation, an account with constrained delegation (msDS-AllowedToDelegateTo),
or — most commonly — write access over a computer object so you can set RBCD. Coercion + relay turns
"can authenticate a DC" into "control a DC". This is the modern lateral-movement/DA path.
Why it works
Delegation lets a service act on behalf of a user. Kerberos implements it with S4U2Self (get a
ticket to yourself as any user) and S4U2Proxy (forward it to a target service). If you control an
account permitted to delegate — or can write msDS-AllowedToActOnBehalfOfOtherIdentity on a target
(RBCD) — you can mint a service ticket as any user, including Domain Admin, to that target.
Method
- Enumerate the primitive. BloodHound edges (
AllowedToDelegate,AllowedToAct,GenericWrite/GenericAllon a computer), ornxc ldap ... --trusted-for-delegation/ LDAP queries for the delegation attributes. - Unconstrained — on a host trusted for unconstrained delegation, capture TGTs of any user who
authenticates to it (
Rubeus monitor), and coerce a DC to authenticate (below) to grab the DC's TGT → DCSync. - Constrained (S4U) — with an account that has
msDS-AllowedToDelegateTo <spn>:getST.py -spn <spn> -impersonate Administrator '<domain>/<svc>:<pass>'(orRubeus s4u).altservice/SPN-substitution lets one allowed SPN pivot to others on the same host. - RBCD (the write-driven path) — when you control a computer account and can write the target's
msDS-AllowedToActOnBehalfOfOtherIdentity:- Set it:
rbcd.py -delegate-to <TARGET$> -delegate-from <YOURMACHINE$> -action write ... - Impersonate:
getST.py -spn cifs/<target> -impersonate Administrator '<domain>/<YOURMACHINE$>:<pass>' - Use the ticket (
KRB5CCNAME=...) withpsexec.py -k -no-pass,secretsdump.py -k, etc.
- Set it:
- Coercion → relay → RBCD (no creds needed to start) — coerce a target/DC to authenticate to
you (
PetitPotam.py,coercer), relay that NTLM to LDAP(S) and grant yourself RBCD:ntlmrelayx.py -t ldaps://<dc> --delegate-access, then S4U as above. (Seenetwork-ntlm-relay.)
Gotchas
altserviceonly works within the same host's SPNs — you can swapcifs→host→httpon the target, not jump machines.ProtectedUsers/ "Account is sensitive and cannot be delegated" blocks impersonating that principal — pick another admin, or a computer account.- Clock skew breaks every Kerberos step — sync to the DC (
ntpdate/faketime) first. - RC4 disabled / AES-only domains need AES keys in your tooling flags; RC4 tickets get rejected.
- RBCD needs write on the target computer, and creating a fake computer needs
ms-DS-MachineAccountQuota > 0(or use a machine account you already own).
Verify success
A service ticket as a privileged user to the target service, used to run a command / dump secrets
(secretsdump.py -k) you could not before — e.g. local admin on the target or DCSync from a
coerced DC.
References
Elad Shamir "Wagging the Dog" (RBCD); Impacket getST.py/rbcd.py/ntlmrelayx.py; Rubeus S4U docs;
MITRE ATT&CK T1558.003. Coercion+relay mechanics: network-ntlm-relay.
File di questa versione
- SKILL.md4.1 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | No | No |
| Esegue comandi shell | Sì | Sì |
| Usa la rete | No | No |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
La scansione non ha trovato nulla da segnalare in questa versione.
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 nov 2026 | ee0e0c5 | d588789f | Firmata | – |
Altro da NoorQureshi
Tutto da questo editoreAltro in Active Directory e Windows
Vai alla categoria- offensive-windows-mitigationssnailsploit/offensive-windows-mitigations4
- active-directory-attack-pathssecurityskills/active-directory-attack-paths3
- analyzing-powershell-script-block-loggingmukul975/analyzing-powershell-script-block-logging3
- offensive-windows-boundariessnailsploit/offensive-windows-boundaries3
- evil-winrmaeondave/evil-winrm3
- bloodyadaeondave/bloodyad3
Chiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login