Skip to content
Vol. 1 · Ed. 2026
CyberGlossary
Entry № 695

LLMNR Poisoning

Reviewed byCybersecurity entrepreneur & security researcher

What is LLMNR Poisoning?

LLMNR PoisoningAn adversary-in-the-middle technique (MITRE T1557.001) that abuses the Link-Local Multicast Name Resolution protocol on UDP/5355 to redirect victims to attacker-controlled hosts.


LLMNR (RFC 4795) is a Windows fallback name-resolution protocol used when DNS returns no answer. The client broadcasts a UDP/5355 multicast query for the unresolved name, and any host on the local link may answer — there is no authentication. An attacker on the same broadcast domain simply responds "that name is me," then prompts the victim's SMB or HTTP client to authenticate, capturing the NTLMv2 challenge-response for offline cracking with hashcat or for live NTLM relay with ntlmrelayx. The canonical tool, Laurent Gaffié's Responder, poisons LLMNR, NBT-NS (UDP/137) and mDNS (UDP/5353) simultaneously.

The attack is one of the most reliable footholds in internal pentests because Windows still fires these multicast queries for typos, dead file shares, decommissioned printers, and WPAD lookups — no user error required beyond normal activity. Captured hashes either crack to plaintext or, when SMB signing is not enforced, relay directly into code execution on another host.

Microsoft announced in 2022 a plan to phase out NetBIOS and LLMNR in favour of mDNS, but LLMNR is not disabled by default yet, so defenders must act: disable LLMNR via Group Policy ("Turn off multicast name resolution"), disable NBT-NS, enforce SMB signing to blunt relay, and segment untrusted VLANs. Detection signals include anomalous UDP/5355 and UDP/137 traffic and Event ID 4624 logons originating from rogue hosts.

flowchart TB
  V["Victim mistypes a share name<br/>DNS returns no answer"] --> Q["Windows broadcasts<br/>LLMNR query (UDP/5355)"]
  Q --> A["Attacker (Responder) replies:<br/>'that host is me'"]
  A --> Auth["Victim connects and sends<br/>NTLMv2 authentication"]
  Auth --> C["Attacker captures<br/>NTLMv2 challenge-response"]
  C --> Crack["Offline crack (hashcat)"]
  C --> Relay["NTLM relay to unsigned SMB<br/>(ntlmrelayx) -> code execution"]

● Examples

  1. 01

    An attacker on a guest VLAN harvests dozens of NTLMv2 hashes within an hour by replying to mistyped share names.

  2. 02

    Combining LLMNR poisoning with ntlmrelayx to relay captured authentications to an unsigned SMB target.

● Frequently asked questions

What is LLMNR Poisoning?

An adversary-in-the-middle technique (MITRE T1557.001) that abuses the Link-Local Multicast Name Resolution protocol on UDP/5355 to redirect victims to attacker-controlled hosts. It belongs to the Attacks & Threats category of cybersecurity.

What does LLMNR Poisoning mean?

An adversary-in-the-middle technique (MITRE T1557.001) that abuses the Link-Local Multicast Name Resolution protocol on UDP/5355 to redirect victims to attacker-controlled hosts.

How do you defend against LLMNR Poisoning?

Defences for LLMNR Poisoning typically combine technical controls and operational practices, as detailed in the full definition above.

What are other names for LLMNR Poisoning?

Common alternative names include: LLMNR spoofing, T1557.001.

● Related terms