responder

Poison LLMNR, NBT-NS, and mDNS to capture Net-NTLMv2 hashes from Windows hosts.

15|1|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/AeonDave/malskill --skill responder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: responder
Source: https://github.com/AeonDave/malskill/tree/main/offensive-tools/network/responder
Command: npx skills add https://github.com/AeonDave/malskill --skill responder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill captures Net-NTLMv2 hashes from Windows hosts on a local network by poisoning name resolution protocols like LLMNR, NBT-NS, and mDNS.

Core Features & Use Cases

  • Hash Capture: Intercepts and saves Net-NTLMv2 hashes from authenticating Windows hosts.
  • Poisoning Attacks: Actively poisons LLMNR, NBT-NS, and mDNS to force authentication.
  • Rogue Servers: Can set up rogue SMB, HTTP, and other servers for credential capture.
  • Use Case: When asked to capture NTLM hashes from Windows machines on the network for offline cracking or relay attacks.

Quick Start

Start Responder in active poisoning mode on the eth0 interface, capturing hashes and enabling verbose output.

Frequently Asked Questions about responder

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

FAQPage Schema
How do I capture Net-NTLMv2 hashes from Windows hosts on a local network?

Net-NTLMv2 hash capture is done by poisoning LLMNR, NBT-NS, and mDNS name resolution protocols to intercept authentication attempts from Windows machines. This Skill sets up rogue SMB and HTTP servers to actively force credential capture.

What is LLMNR and NBT-NS poisoning for credential capture?

LLMNR and NBT-NS poisoning is a technique that exploits fallback name resolution protocols on Windows hosts. By responding to failed DNS queries, it forces target machines to authenticate against rogue servers, allowing Net-NTLMv2 hash interception.

Do I need root privileges to run Responder for hash interception?

Yes, you need root privileges to execute Responder for hash interception on a local network. The tool must be run on the same network segment as the target Windows hosts to successfully poison traffic and capture credentials.

Can I use captured NTLM hashes for relay attacks and offline cracking?

Yes, captured Net-NTLMv2 hashes can be used directly for NTLM relay attacks or saved for offline hash cracking. The interception mechanism gathers authentication responses that are formatted for these downstream exploitation processes.

How do I start capturing hashes in active poisoning mode on a specific interface?

To start capturing hashes in active poisoning mode, you run the tool on your network interface, such as eth0. This enables verbose output and actively poisons local name resolution protocols to intercept Windows authentication traffic.

What are the limitations of using local network poisoning for hash capture?

The primary limitation of local network poisoning is that it requires execution on the same network segment as the targets and root privileges. It relies on Windows hosts failing standard DNS resolution and falling back to vulnerable protocols.