Detectionmediumtest

PsExec Tool Execution From Suspicious Locations - PipeName

Detects PsExec default pipe creation where the image executed is located in a suspicious location. Which could indicate that the tool is being used in an attack

Convert In Phoenix Studio

Open this Sigma rule in the converter with the YAML preloaded and ready for backend selection.

Launch
Nasreddine Bencherchali (Nextron Systems)Created Thu Aug 04Updated Wed Sep 2041504465-5e3a-4a5b-a5b4-2a0baadd4463windows
Log Source
WindowsNamed Pipe Created
ProductWindows← raw: windows
CategoryNamed Pipe Created← raw: 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 Logic
Detection Logic1 selector
detection:
    selection:
        PipeName: '\PSEXESVC'
        Image|contains: # Add or remove locations depending on how and if you execute Psexec in your env
            - ':\Users\Public\'
            - ':\Windows\Temp\'
            - '\AppData\Local\Temp\'
            - '\Desktop\'
            - '\Downloads\'
    condition: selection
False Positives

Rare legitimate use of psexec from the locations mentioned above. This will require initial tuning based on your environment.

Rule Metadata
Rule ID
41504465-5e3a-4a5b-a5b4-2a0baadd4463
Status
test
Level
medium
Type
Detection
Created
Thu Aug 04
Modified
Wed Sep 20
Path
rules/windows/pipe_created/pipe_created_sysinternals_psexec_default_pipe_susp_location.yml
Raw Tags
attack.executionattack.t1569.002attack.s0029
View on GitHub