responder-poison

Captures NTLMv2 hashes via LLMNR/NBT-NS/mDNS poisoning with Responder in Windows domain networks.

1.7k|238|Updated Dec 7, 2019
One-click install
npx skills add https://github.com/wgpsec/AboutSecurity --skill responder-poison
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: responder-poison
Source: https://github.com/wgpsec/AboutSecurity/tree/main/skills/tool/responder-poison
Command: npx skills add https://github.com/wgpsec/AboutSecurity --skill responder-poison

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

In authorized Windows domain penetration tests, credentials are often needed to move laterally, but actively attacking services is noisy. This Skill explains how to passively capture NTLMv2 authentication hashes by poisoning LLMNR, NBT-NS, and mDNS name resolution broadcasts with Responder, then crack them offline or relay them to other services.

Core Features & Use Cases

  • Passive Hash Capture: Run Responder on a network interface to answer name resolution broadcasts and record NTLMv2 hashes to log files.
  • Hash Cracking Workflow: Feed captured hashes directly into hashcat (mode 5600 for NTLMv2, 5500 for NTLMv1) for offline password recovery.
  • NTLM Relaying: Disable Responder's SMB/HTTP listeners and pair it with ntlmrelayx to relay captured authentication to targets without SMB signing.
  • WPAD and DHCPv6 Attacks: Use WPAD proxy poisoning and DHCPv6/mitm6 techniques to capture additional authentication traffic.
  • Use Case: During an internal assessment, start Responder in analysis mode to confirm broadcast traffic, then run responder -I eth0 -wv during business hours to collect hashes from mistyped hostnames and stale shortcuts.

Quick Start

Ask the AI to start Responder on interface eth0 in verbose mode with WPAD enabled and show any captured NTLMv2 hashes from the Responder logs directory.

Frequently Asked Questions about responder-poison

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture NTLMv2 hashes with Responder?

Run Responder on a network interface with `responder -I eth0 -wv` to poison LLMNR, NBT-NS, and mDNS broadcasts. Captured NTLMv2 hashes are written to the Responder logs directory, typically /usr/share/responder/logs/.

How do I crack Responder NTLMv2 hashes with hashcat?

Extract the hashes from the Responder logs into a file and run hashcat with mode 5600, for example `hashcat -m 5600 ntlmv2_hashes.txt rockyou.txt`. NTLMv1 hashes from older systems use mode 5500 instead.

Should I crack hashes or relay them with ntlmrelayx?

Relaying with ntlmrelayx is preferred when the target has SMB signing disabled, since it works without knowing the plaintext password. If SMB signing is enabled on the target, relaying fails and offline cracking with hashcat is the remaining option.

Why is Responder not capturing any hashes?

First run `responder -I eth0 -A` in analyze mode to confirm LLMNR/NBT-NS traffic exists on the subnet. Also delete the Responder.db database file, since Responder skips hashes it has already recorded.

What is WPAD poisoning in Responder?

WPAD poisoning uses the -w flag so Responder answers browser proxy discovery requests and serves a PAC file pointing browsers at itself. The proxy then demands NTLM authentication, capturing hashes from all proxied HTTP traffic.