rules/windows/pipe_created/pipe_created_powershell_execution_pipe.yml

title: New PowerShell Instance Created
id: ac7102b4-9e1e-4802-9b4f-17c5524c015c
related:
    - id: 58cb02d5-78ce-4692-b3e1-dce850aae41a
      type: derived
status: test
description: Detects the execution of PowerShell via the creation of a named pipe starting with PSHost
references:
    - https://threathunterplaybook.com/hunts/windows/190610-PwshAlternateHosts/notebook.html
    - https://threathunterplaybook.com/hunts/windows/190410-LocalPwshExecution/notebook.html
author: Roberto Rodriguez (Cyb3rWard0g), OTR (Open Threat Research)
date: 2019-09-12
modified: 2023-11-30
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:
    - Likely
level: informational
Merge PR #4577 from @nasbench - Multiple Fixes & Updates 2023-12-21 21:04:18 +01:00			`title: New PowerShell Instance Created`
10 rules from THP - contributing soon 2020-10-12 15:42:34 -04:00			`id: ac7102b4-9e1e-4802-9b4f-17c5524c015c`
Merge PR #4577 from @nasbench - Multiple Fixes & Updates 2023-12-21 21:04:18 +01:00			`related:`
			`- id: 58cb02d5-78ce-4692-b3e1-dce850aae41a`
			`type: derived`
$frack113$ Change status for old rules 2021-11-27 11:33:14 +01:00			`status: test`
Merge PR #4577 from @nasbench - Multiple Fixes & Updates 2023-12-21 21:04:18 +01:00			`description: Detects the execution of PowerShell via the creation of a named pipe starting with PSHost`
10 rules from THP - contributing soon 2020-10-12 15:42:34 -04:00			`references:`
fix: resolves #4015 2023-02-07 14:33:56 +01:00			`- https://threathunterplaybook.com/hunts/windows/190610-PwshAlternateHosts/notebook.html`
			`- https://threathunterplaybook.com/hunts/windows/190410-LocalPwshExecution/notebook.html`
$frack113$ Order yaml field 2022-10-25 12:00:56 +02:00			`author: Roberto Rodriguez (Cyb3rWard0g), OTR (Open Threat Research)`
Merge PR #4950 from @nasbench - Comply With v2 Spec Changes 2024-08-12 12:02:50 +02:00			`date: 2019-09-12`
			`modified: 2023-11-30`
$frack113$ Order yaml field 2022-10-25 12:00:56 +02:00			`tags:`
			`- attack.execution`
			`- attack.t1059.001`
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:`
Merge PR #4577 from @nasbench - Multiple Fixes & Updates 2023-12-21 21:04:18 +01:00			`- Likely`
Fixes&improvements 2021-04-08 00:32:01 +02:00			`level: informational`