PsExec Utility Execution From Suspicious Locations - PipeName (via pipe_created)
This rule detects PsExec default pipe creation where the image executed is located in an anomalous location. Which could indicate that the tool is being used in an attack
SigmamediumWindowsv1
sigma
psexec-utility-execution-from-suspicious-locations-pipename-via-pipe-created
title: PsExec Utility Execution From Suspicious Locations - PipeName (via pipe_created)
id: ccd926f0-800e-5fb9-a083-914e8c5baa3a
status: stable
description: This rule detects PsExec default pipe creation where the image executed is located in an anomalous location. Which could indicate that the tool is being used in an attack
references:
- https://attack.mitre.org/techniques/T1569/002/
- https://www.jpcert.or.jp/english/pub/sr/ir_research.html
- https://jpcertcc.github.io/ToolAnalysisResultSheet
author: Huntrule Team
date: 2026-02-22
tags:
- attack.execution
- attack.t1569.002
- attack.s0029
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: '\PSEXESVC'
Image|contains:
- ':\Users\Public\'
- ':\Windows\Temp\'
- '\AppData\Local\Temp\'
- '\Desktop\'
- '\Downloads\'
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.