Possible Creation of New PowerShell Instance (via pipe_created)
This rule detects the execution of PowerShell via the creation of a named pipe starting with PSHost
SigmainformationalWindowsv1
sigma
possible-creation-of-new-powershell-instance-via-pipe-created
title: Possible Creation of New PowerShell Instance (via pipe_created)
id: 2f7ceed1-346c-550b-bec0-f3377b9dcfbd
status: stable
description: This rule detects the execution of PowerShell via the creation of a named pipe starting with PSHost
references:
- https://attack.mitre.org/techniques/T1059/001/
- https://threathunterplaybook.com/hunts/windows/190610-PwshAlternateHosts/notebook.html
- https://threathunterplaybook.com/hunts/windows/190410-LocalPwshExecution/notebook.html
author: Huntrule Team
date: 2026-02-02
tags:
- attack.execution
- attack.t1059.001
logsource:
product: windows
category: pipe_created
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: '\PSHost'
condition: selection
falsepositives:
- Unknown
level: informational
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.