huntrule

Windows Named Pipe Creation for PsExec Default Pipe

Alerts on creation of the default PsExec named pipe (\\PSEXESVC) using Windows named pipe creation telemetry.

FreeReviewedSigma · Low · v5
Product
windows
Category
pipe_created
Author
Thomas Patzke (SigmaHQ), DRL 1.1
Published
2017-06-12
Updated
2026-07-31
AnalysisDetection

ATT&CK techniques

Execution

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule detects creation of the PsExec default named pipe (\PSEXESVC) on Windows. Attackers may use PsExec-style execution mechanisms that rely on Windows named pipes for service communication and remote command execution. It relies on telemetry that records named pipe events, specifically Sysmon pipe creation events (Event ID 17/18).

Reporting behind it

Related detections9 linkedT1569.002 — drag to rearrange
Suspicious Executable Launched from Public Music Staging Directory (via process_creation)
Malicious Service Execution via PAExec
Suspicious RemCom Service Named Pipe for Lateral Movement (via pipe_created)
Malicious CACTUS Ransomware Deployment via TotalExec Script (via ps_script)
Malicious PsExec Service Binary Execution from Windows Directory via services.exe (via process_creation)
Malicious Remote Command Execution via smbexec Output Redirection Pattern
Malicious Lateral Movement via PsExec File-List Target
Malicious PsExec SYSTEM Interactive Shell Execution (via process_creation)
Suspicious PsExec Service Named Sliver
Windows Named Pipe Creation for PsExec Default Pipe
Pivot detection · T1569.002 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. 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.