Files
hayabusa/rules/sigma/windows/pipe_created/sysmon_mal_cobaltstrike.yml
T
2021-11-22 08:45:44 +09:00

47 lines
1.5 KiB
YAML

title: CobaltStrike Named Pipe
author: Florian Roth, Wojciech Lesicki
date: 2021/05/25
description: Detects the creation of a named pipe as used by CobaltStrike
detection:
SELECTION_1:
EventID: 17
SELECTION_2:
EventID: 18
SELECTION_3:
PipeName: '*\MSSE-*'
SELECTION_4:
PipeName: '*-server*'
SELECTION_5:
PipeName: \postex_*
SELECTION_6:
PipeName: \postex_ssh_*
SELECTION_7:
PipeName: \status_*
SELECTION_8:
PipeName: \msagent_*
condition: ((SELECTION_1 or SELECTION_2) and ((SELECTION_3 and SELECTION_4) or SELECTION_5
or SELECTION_6 or SELECTION_7 or SELECTION_8))
falsepositives:
- Unknown
id: d5601f8c-b26f-4ab0-9035-69e11a8d4ad2
level: critical
logsource:
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). In the current popular sysmon configuration
(https://github.com/SwiftOnSecurity/sysmon-config) this is not there, you have
to add it yourself or use this extended version that logs the Named Pipes used
in this Sigma repo (https://github.com/Neo23x0/sysmon-config)
product: windows
references:
- https://twitter.com/d4rksystem/status/1357010969264873472
- https://labs.f-secure.com/blog/detecting-cobalt-strike-default-modules-via-named-pipe-analysis/
- https://github.com/Neo23x0/sigma/issues/253
- https://blog.cobaltstrike.com/2021/02/09/learn-pipe-fitting-for-all-of-your-offense-projects/
status: experimental
tags:
- attack.defense_evasion
- attack.privilege_escalation
- attack.t1055