Windows WMI Event Consumer (scrcons.exe) Created Named Pipe

title: Windows WMI Event Consumer (scrcons.exe) Created Named Pipe
id: ca357b0d-1338-40e4-a9db-7aa6bb8a1e84
status: test
description: This rule identifies when the WMI Event Consumer process (scrcons.exe) creates a named pipe on Windows. Named pipes can be used for inter-process communication, and creating them from system services can indicate suspicious execution or tooling behaviors. It relies on telemetry from named pipe creation events that include the creating process image path.
references:
  - https://github.com/RiccardoAncarani/LiquidSnake
  - https://github.com/SigmaHQ/sigma/blob/master/rules/windows/pipe_created/pipe_created_scrcons_wmi_consumer_namedpipe.yml
author: Florian Roth (Nextron Systems), Huntrule Team
date: 2021-09-01
modified: 2023-11-30
tags:
  - attack.t1047
  - attack.execution
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:
    Image|endswith: \scrcons.exe
  condition: selection
falsepositives:
  - Unknown
level: medium
license: DRL-1.1
related:
  - id: 493fb4ab-cdcc-4c4f-818c-0e363bd1e4bb
    type: derived