Suspicious PUA - PAExec Default Named Pipe (via pipe_created)
This rule detects PAExec default named pipe
SigmamediumWindowsv1
sigma
suspicious-pua-paexec-default-named-pipe-via-pipe-created
title: Suspicious PUA - PAExec Default Named Pipe (via pipe_created)
id: d4cb0bb8-b48f-5a2a-99b4-2a7a7a473e29
status: stable
description: This rule detects PAExec default named pipe
references:
- https://attack.mitre.org/techniques/T1569/002/
- https://github.com/microsoft/Microsoft-365-Defender-Hunting-Queries/blob/efa17a600b43c897b4b7463cc8541daa1987eeb4/Command%20and%20Control/C2-NamedPipe.md
- https://github.com/poweradminllc/PAExec
author: Huntrule Team
date: 2026-05-04
tags:
- attack.execution
- attack.t1569.002
logsource:
category: pipe_created
product: windows
definition: 'Note that you have to configure logging for Named Pipe Events in Sysmon config (Event ID 17 and Event ID 18). The basic configuration is in popular sysmon configuration (https://github.com/SwiftOnSecurity/sysmon-config), but it is worth verifying. You can also use other repo, e.g. https://github.com/Neo23x0/sysmon-config, https://github.com/olafhartong/sysmon-modular. How to test detection? You can check powershell script from this site https://svch0st.medium.com/guide-to-named-pipes-and-hunting-for-cobalt-strike-pipes-dc46b2c5f575'
detection:
selection:
PipeName|startswith: '\PAExec'
condition: selection
falsepositives:
- Unknown
level: medium
Known false positives
- Unknown
Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.