Operator On The Wire
Join
← Back to Knowledge Base
BLUE TEAM / THREAT HUNT / ACTIVE DIRECTORY / RELAY ATTACKS

Responder Attacks

This note documents detection patterns related to LLMNR / Responder Poisoning within Windows environments.


Direct Indicators

Log SourceEvent ID / Error CodeMeaningForensic ValueNotes
Custom Script / EventLogLLMNRDetectionLLMNR query answered by rogue responderCriticalDirect indicator when custom PowerShell detection logs rogue LLMNR responders. Review returned IP addresses.
Sysmon22DNS queryCriticalDetect failed hostname lookups leading to LLMNR fallback. Suspicious if mistyped names resolve to attacker-controlled IP.
Security4648Explicit credentials usedHighVictim may authenticate explicitly to rogue SMB share exposed by attacker.
Security4624Successful logonHighNTLM authentication to rogue host after poisoning. Review target host and source account.
Sysmon3Network connectionCriticalVictim initiates SMB/HTTP connection toward responder host (ports 445, 80, 139).
Sysmon1Process creationMediumUseful when victim launches explorer, cmd, or script triggering mistyped UNC access.
Sysmon7Image loadedLow-MediumNetwork DLL activity may appear depending on calling process.
PowerShell4104Script block loggingHighDetects manual UNC testing or scripts generating mistyped network calls.

Indirect Indicators

IndicatorWhat To Look ForForensic ValueNotes
Failed hostname lookupNon-existent hostname queriedCriticalTriggers LLMNR fallback mechanism.
Mistyped UNC pathAccess to invalid file shareCriticalCommon trigger for Responder attacks.
SMB connection to unusual hostVictim authenticates to rogue machineCriticalStrong poisoning evidence.
IPv6 local response::1 or rogue IPv6 responder appearsHighResponder frequently abuses IPv6 first.
Repeated failed share accessMultiple unresolved file requestsHighOften attacker-induced or user typo.

Common Tools

ToolUsage
ResponderLLMNR / NBT-NS poisoning and NTLM capture
InveighPowerShell-based responder alternative
Metasploit SMB CaptureCaptures NTLM credentials
Custom rogue SMB listenerManual credential collection

Relevant Artifacts

  • Sysmon Event ID 22 DNS queries
  • Security logs (4648, 4624)
  • Sysmon Event ID 3 network connections
  • SMB authentication logs
  • PowerShell detection logs
  • Packet captures showing LLMNR multicast traffic
  • EDR network telemetry
  • DNS Client Operational logs

MITRE ATT&CK References

  • T1557 Adversary-in-the-Middle
  • T1557.001 LLMNR/NBT-NS Poisoning and SMB Relay
  • T1187 Forced Authentication

Decision Tree

  1. Is suspicious hostname resolution present?

    • Identify non-existent hostname queries.
  2. Did victim fall back to LLMNR?

    • Check Sysmon 22 or multicast traffic.
  3. Was rogue responder present?

    • Review returned IP addresses.
  4. Pivot:

    • Rogue IP → inspect SMB authentication.
    • Victim host → inspect process causing query.
    • Account → check 4648 / 4624.
  5. Confirm credential exposure

    • Determine whether NTLM authentication reached attacker host.

Example Detection Templates

KQL

DeviceNetworkEvents
| where RemotePort in (5355,445)
| summarize count() by InitiatingProcessAccountName, RemoteIP, bin(TimeGenerated,5m)
DeviceEvents
| where ActionType == "DnsQueryResponse"
| where AdditionalFields contains "QueryName"

EQL

any where event.code == "22"

Sigma

title: LLMNR Poisoning Detection
id: llmnr-poisoning-detection
status: experimental
description: Detects suspicious hostname resolution consistent with LLMNR poisoning
logsource:
  product: windows
  category: dns_query
detection:
  selection:
    EventID: 22
  condition: selection
fields:
  - QueryName
  - QueryResults
falsepositives:
  - Legitimate failed hostname lookups
level: high
tags:
  - attack.credential_access
  - attack.t1557.001

Splunk

index=main earliest=1690290078 latest=1690291207 SourceName=LLMNRDetection
| table _time, ComputerName, SourceName, Message
index=main earliest=1690290078 latest=1690291207 EventCode=22
| table _time, Computer, user, Image, QueryName, QueryResults
index=main earliest=1690290814 latest=1690291207 EventCode=4648
| table _time, EventCode, source, name, user, Target_Server_Name, Message
| sort 0 _time

Mitigation & Hardening

Control AreaMitigationEffectivenessNotes
LLMNRDisable LLMNR via GPOCriticalPrimary prevention
NBT-NSDisable NetBIOS Name ServiceHighReduces poisoning surface
SMB SigningEnforce SMB signingCriticalPrevents relay
DNS HygieneEnsure correct DNS registrationMediumReduces fallback events
MonitoringAlert on rogue LLMNR responsesHighStrong detection surface