rules/windows/pipe_created/pipe_created_powershell_execution_pipe.yml

title: PowerShell Execution Via Named Pipe
id: ac7102b4-9e1e-4802-9b4f-17c5524c015c
status: test
description: Detects execution of PowerShell via creation of named pipe starting with PSHost
author: Roberto Rodriguez (Cyb3rWard0g), OTR (Open Threat Research)
references:
    - https://threathunterplaybook.com/notebooks/windows/02_execution/WIN-190410151110.html
date: 2019/09/12
modified: 2022/08/04
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
tags:
    - attack.execution
    - attack.t1059.001
Add missing definition for named pipe rules 2022-08-04 15:56:47 +01:00			`title: PowerShell Execution Via Named Pipe`
10 rules from THP - contributing soon 2020-10-12 15:42:34 -04:00			`id: ac7102b4-9e1e-4802-9b4f-17c5524c015c`
$frack113$ Change status for old rules 2021-11-27 11:33:14 +01:00			`status: test`
Add missing definition for named pipe rules 2022-08-04 15:56:47 +01:00			`description: Detects execution of PowerShell via creation of named pipe starting with PSHost`
10 rules from THP - contributing soon 2020-10-12 15:42:34 -04:00			`author: Roberto Rodriguez (Cyb3rWard0g), OTR (Open Threat Research)`
			`references:`
Add missing definition for named pipe rules 2022-08-04 15:56:47 +01:00			`- https://threathunterplaybook.com/notebooks/windows/02_execution/WIN-190410151110.html`
$frack113$ Change status for old rules 2021-11-27 11:33:14 +01:00			`date: 2019/09/12`
Add missing definition for named pipe rules 2022-08-04 15:56:47 +01:00			`modified: 2022/08/04`
10 rules from THP - contributing soon 2020-10-12 15:42:34 -04:00			`logsource:`
Add missing definition for named pipe rules 2022-08-04 15:56:47 +01:00			`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'
10 rules from THP - contributing soon 2020-10-12 15:42:34 -04:00			`detection:`
Add missing definition for named pipe rules 2022-08-04 15:56:47 +01:00			`selection:`
			`PipeName\|startswith: '\PSHost'`
			`condition: selection`
10 rules from THP - contributing soon 2020-10-12 15:42:34 -04:00			`falsepositives:`
Add missing definition for named pipe rules 2022-08-04 15:56:47 +01:00			`- Unknown`
Fixes&improvements 2021-04-08 00:32:01 +02:00			`level: informational`
$frack113$ Change status for old rules 2021-11-27 11:33:14 +01:00			`tags:`
Add missing definition for named pipe rules 2022-08-04 15:56:47 +01:00			`- attack.execution`
			`- attack.t1059.001`