CyberKit

NTLM Relay

Also called SMB relay.

Forwarding captured NTLM authentication to a target as the victim.

What it is

An attack that intercepts an NTLM authentication attempt and relays it to a different service, authenticating to that service as the victim without ever knowing their password or hash. It exploits the challenge-response handshake when message signing is not enforced.

Why it matters

It converts coerced or poisoned authentication into access on a chosen target, and remains effective wherever SMB signing, channel binding, or LDAP signing are not required. Mandatory signing and Extended Protection are the core mitigations.

In practice

An attacker poisons name resolution to capture a server's NTLM authentication, relays it to LDAP, and grants themselves rights in the directory.

What to look for

  • NTLM logons whose source address does not match the claimed workstation.
  • Authentication arriving at servers that do not require SMB or LDAP signing.
  • A burst of NTLM logons from one host to many targets.

Common mistake

Patching the poisoning but not the relay target. Enforce signing and EPA so relayed authentication fails.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Microsoft Defender for Identity Commercial

    Watches domain controller traffic and events for attacks such as Kerberoasting and DCSync.

  • BloodHound Open source

    Maps attack paths through Active Directory, the same view an attacker builds.

  • Splunk Enterprise Security Commercial

    Where many teams search domain controller logs, such as Kerberos ticket events, for these attacks.

Read next

Sources