Windows: Detects Access to ADMIN$ Network Share (Event 5140)

Alerts on Windows Security event 5140 entries where an access request targets the ADMIN$ share.

FreeReviewedSigma · Low · v2
Product
windows
Service
security
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2017-03-04
Updated
2026-07-31

ATT&CK techniques

Lateral Movement
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags Windows Security events where a client attempts to access the ADMIN$ hidden administrative network share. Access to ADMIN$ is a common step in Windows lateral movement because it can expose administrative file system paths used for remote control and deployment. Detection relies on audit event 5140 with ShareName set to Admin$ and applies an exclusion for subjects ending with a dollar sign.

Related detections9 linkedT1021.002 — drag to rearrange
Malicious WMIexec Style Command Output Redirection to Local Admin Share
Malicious Cobalt Strike Default Named Pipe Activity
Suspicious PsExec Service Launching Encoded PowerShell Payload
Suspicious Impacket Style Command Execution with ADMIN Share Output Redirect
Suspicious Active Directory Reconnaissance via In-Memory Offensive PowerShell (via ps_script)
Suspicious NetExec Post-Exploitation Tool Execution via nxc (via process_creation)
Suspicious SMB Admin Share Mapping for Lateral Tool Transfer (via process_creation)
Suspicious Impacket Remote Execution Tool Usage via process_creation
Suspicious Remote Service Execution via PsExec (via process_creation)
Windows: Detects Access to ADMIN$ Network Share (Event 5140)
Pivot detection · T1021.002 · 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.