Uncommon ADWS (Port 9389) Connections from Non-Standard Windows Binaries

Alerts on unexpected process-to-ADWS (TCP/9389) connections on Windows to highlight potential directory discovery.

FreeReviewedSigma · Medium · v2
Product
windows
Category
network_connection
Author
@kostastsale (SigmaHQ), DRL 1.1
Published
2024-01-26
Updated
2026-07-31

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 flags network connections to Active Directory Web Services using TCP port 9389 when the initiating process is not one of the expected ADWS management binaries. Attackers may use ADWS to query or discover Active Directory data, so uncommon process-to-ADWS communication can indicate misuse. The rule relies on Windows network connection telemetry (destination port and initiated connection) and process image path context to identify unexpected callers.

Related detections9 linkedT1087 — drag to rearrange
Suspicious Active Directory Discovery via ADFind
Suspicious Active Directory Enumeration via Sysinternals AD Explorer Snapshot (via process_creation)
Suspicious SimpleHelp Remote Access Client Spawning Discovery Commands (via process_creation)
Windows Process Creation: SOAPHound Execution via AD Data Collection Command-Line Arguments
Windows Process Creation Signals for Pikabot System Discovery
Windows PowerShell module commandlet names matching known exploitation and post-exploitation tooling
Windows Process Creation: Suspicious PowerShell Commandlets Used by Known Exploitation Tools
Windows Process Creation: Seatbelt.exe PUA Discovery Command-Line Execution
Windows Process Creation: China Chopper Webshell Command Pattern via W3WP
Uncommon ADWS (Port 9389) Connections from Non-Standard Windows Binaries
Pivot detection · T1087 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

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