Suspicious PsExec Named Pipe Creation on Target Host

PremiumReviewedSigma · Medium · v1
Product
windows
Category
pipe_created
Author
HuntRule
Published
2026-11-03
Updated
2026-11-03

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 detects creation of the stdin stdout and stderr named pipes used by PsExec style remote execution as described in the WithSecure lab where communication rode over three PsExec named pipes on the IPC share. This pipe naming convention persists even when the service binary is renamed which makes it an effective detection for renamed PsExec and similar remote execution utilities.

Related detections9 linkedT1021.002 — drag to rearrange
Suspicious Process Spawned by WmiPrvSE for Remote Execution
Suspicious PsExec Remote Execution Command Line
Malicious NetExec SMB Enumeration Execution (via process_creation)
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 PsExec Named Pipe Creation on Target Host
Pivot detection · T1021.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.