huntrule

Windows PsExec Named Pipe Creation from Suspicious Paths (PSEXESVC)

Alerts on PsExec pipe \PSEXESVC creation when the executing image path is in public/temp/desktop/downloads locations.

FreeReviewedSigma · Medium · v2
Product
windows
Category
pipe_created
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-08-04
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 flags PsExec service named pipe creation events where the creating executable path contains common user-writable or staging locations such as \:\Users\Public\, \:\Windows\Temp\, \AppData\Local\Temp\, \Desktop\, or \Downloads\, and the pipe name matches \PSEXESVC. Attackers often stage tools in writable directories and then execute them to establish remote execution capabilities via the PsExec service. It relies on telemetry for named pipe creation events that include both the PipeName and the Image path of the process creating the pipe.

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 PsExec Named Pipe Creation from Suspicious Paths (PSEXESVC)
Pivot detection · T1569.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.