rules/windows/pipe_created/pipe_created_psexec_default_pipe.yml

title: PsExec Default Named Pipe
id: f3f3a972-f982-40ad-b63c-bca6afdfad7c
related:
    - id: 42c575ea-e41e-41f1-b248-8093c3e82a28
      type: derived
status: test
description: Detects PsExec service installation and execution events (service and Sysmon)
references:
    - https://www.jpcert.or.jp/english/pub/sr/ir_research.html
    - https://jpcertcc.github.io/ToolAnalysisResultSheet
author: Thomas Patzke
date: 2017/06/12
modified: 2022/10/09
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'
    condition: selection
fields:
    - EventID
    - CommandLine
    - ParentCommandLine
    - ServiceName
    - ServiceFileName
    - TargetFilename
    - PipeName
falsepositives:
    - Unknown
level: low
Update PsExec Rules 2022-10-26 23:15:01 +02:00			`title: PsExec Default Named Pipe`
$frack113$ split global win_tool_psexec.yml 2021-09-21 10:10:48 +02:00			`id: f3f3a972-f982-40ad-b63c-bca6afdfad7c`
			`related:`
			`- id: 42c575ea-e41e-41f1-b248-8093c3e82a28`
$frack113$ Fix related 2022-10-09 17:28:05 +02:00			`type: derived`
$frack113$ old experimental rule promotion 2022-10-09 16:54:04 +02:00			`status: test`
$frack113$ split global win_tool_psexec.yml 2021-09-21 10:10:48 +02:00			`description: Detects PsExec service installation and execution events (service and Sysmon)`
			`references:`
			`- https://www.jpcert.or.jp/english/pub/sr/ir_research.html`
			`- https://jpcertcc.github.io/ToolAnalysisResultSheet`
$frack113$ old experimental rule promotion 2022-10-09 16:54:04 +02:00			`author: Thomas Patzke`
			`date: 2017/06/12`
			`modified: 2022/10/09`
$frack113$ split global win_tool_psexec.yml 2021-09-21 10:10:48 +02:00			`tags:`
			`- attack.execution`
			`- attack.t1569.002`
			`- attack.s0029`
Renamed rule filename for conformity 2022-08-04 15:57:43 +01:00			`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'`
			`condition: selection`
$frack113$ split global win_tool_psexec.yml 2021-09-21 10:10:48 +02:00			`fields:`
			`- EventID`
			`- CommandLine`
			`- ParentCommandLine`
			`- ServiceName`
			`- ServiceFileName`
			`- TargetFilename`
			`- PipeName`
$frack113$ Order yaml field 2022-10-25 12:00:56 +02:00			`falsepositives:`
			`- Unknown`
			`level: low`