Suspicious Remote Connection to ADWS Port 9389 via security

PremiumReviewedSigma · Medium · v1
Product
windows
Service
security
Author
HuntRule
Published
2026-07-11
Updated
2026-08-28

ATT&CK techniques

Discovery
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects Windows Filtering Platform event 5156 recording an allowed inbound connection to TCP port 9389, the Active Directory Web Services port. Correlating the real source address from event 5156 exposes remote ADWS enumeration that would otherwise appear as localhost in Directory Service logs, so non-loopback connections to 9389 indicate potential SOAPHound style directory collection.

Related detections9 linkedT1087.002 — drag to rearrange
Suspicious AdFind Active Directory Reconnaissance Tool Execution (via process_creation)
Suspicious Active Directory Enumeration via ADWS PowerShell Cmdlets via ps_script
Windows Process Creation: Renamed AdFind.exe Executions
PowerShell: Active Directory computer enumeration via Get-AdComputer
Windows Process Creation: AdFind Executed with Suspicious Recon Flags
Windows Process Creation: Execution of Net.exe or Net1.exe
Malicious Active Directory Enumeration via SharpHound or BloodHound (via process_creation)
Suspicious Group Discovery - Command (via process_creation)
SharpHound Host Enumeration Over Kerberos (via security)
Suspicious Remote Connection to ADWS Port 9389 via security
Pivot detection · T1087.002 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.