huntrule

Windows Named Pipe Creation Alert for Known Malicious Pipe Names

Alert on Windows named pipe creations where the PipeName matches known malware-associated pipe identifiers.

FreeReviewedSigma · Critical · v2
Product
windows
Category
pipe_created
Author
Florian Roth (Nextron Systems), blueteam0ps, elhoim (SigmaHQ), DRL 1.1
Published
2017-11-06
Updated
2026-07-31
AnalysisDetection

ATT&CK techniques

Priv Esc → Defense Evasion

  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 creation of Windows named pipes when the pipe name matches a set of identifiers associated with known malware and threat tools. Named pipes can be used for covert inter-process communication, staging, and payload control, helping attackers blend into normal Windows functionality. It relies on telemetry from Windows named pipe creation events, typically provided by Sysmon pipe event logging.

Reporting behind it

Related detections9 linkedT1055 — drag to rearrange
Suspicious Office Application Spawning Script Or Shell Interpreter
Suspicious Network Connection From wabmig.exe (Turian Injection)
Suspicious Outbound Network Connection from Explorer Process
Suspicious AppLaunch.exe Spawned As Injection Target (via process_creation)
Suspicious BugSleep Marker File in Public Directory
Suspicious CRAT Injection Named Pipe ChromeUpdatePipe (via pipe_created)
AsyncRAT Injector libPK.dll Written to Public Folder (via file_event)
FlawedGrace spawning threat injection target
In-Memory Ramnit Process Injection Target Spawned by WmiPrvSE in drIBAN Fraud Operation (via process_creation)
Windows Named Pipe Creation Alert for Known Malicious Pipe Names
Pivot detection · T1055 · 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.