huntrule

Windows Named Pipe Creation with "\coerced\" PipeName Segment

Detects Windows named pipe creations where the pipe name contains the '\coerced\' pattern.

FreeReviewedSigma · High · v2
Product
windows
Category
pipe_created
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2023-10-11
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 Windows named pipe creation events where the PipeName contains the specific substring "\coerced\". Such naming patterns can indicate usage of tools or behaviors associated with coercion-based privilege escalation and related stealth techniques. It relies on telemetry from Windows named pipe creation logging, such as Sysmon named pipe event monitoring.

Reporting behind it

Related detections9 linkedT1055 — drag to rearrange
Suspicious Rundll32 Spawning Injection Target Process via Qakbot (via process_creation)
Malicious AddInProcess32 Network Beacon on PureRAT C2 Ports
Suspicious Payload Staging in ProgramData IntelDriver Folder (via file_event)
Possible DarkGate Process Injection via iTunesHelper Spawning vbc.exe
Suspicious PowerShell Shellcode Loader via Function Pointer Delegate
Suspicious Named Pipe Created by Kazuar Backdoor for Interprocess Command Channel
Suspicious SmallTiger Backdoor DLL Load via Image Load
Suspicious svchost Execution With Anomalous Arguments via DeedRAT (via process_creation)
Suspicious Sang Loader Execution with Install or PassUAC Arguments
Windows Named Pipe Creation with "\coerced\" PipeName Segment
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.