Lion Cipher Lab

Poison LLMNR/NBT-NS and relay NTLM in your own lab (Responder)

Why it matters

On almost every internal penetration test of a Windows/Active Directory network, the very first foothold comes not from an exploit but from a design behavior: when a Windows machine cannot resolve a name through DNS, it FALLS BACK to shouting the question to the whole local network segment and trusting whichever host answers first. An attacker who is simply present on that segment answers 'that's me', and the victim machine authenticates to the attacker -- handing over a NetNTLMv2 response, a cryptographic proof of the user's identity. From there the attacker either cracks that response…

What you'll learn

Steps in this lab

  1. Read this first: your own lab only -- the authorization firewall
  2. Why LLMNR, NBT-NS, and mDNS are poisonable in the first place
  3. Get the attacker VM and install Responder
  4. Run Responder and capture a NetNTLMv2 hash
  5. Two ways to use the capture: crack it offline, or RELAY it live
  6. Now shut it down: disable LLMNR/NBT-NS, require signing, detect it
  7. When it works, when it doesn't, and when NOT to use it
  8. What you did, and the one sentence to keep

Open the full interactive lab →