PUA - PAExec Default Named Pipe

 1title: PUA - PAExec Default Named Pipe
 2id: f6451de4-df0a-41fa-8d72-b39f54a08db5
 3status: test
 4description: Detects PAExec default named pipe
 5references:
 6    - https://github.com/microsoft/Microsoft-365-Defender-Hunting-Queries/blob/efa17a600b43c897b4b7463cc8541daa1987eeb4/Command%20and%20Control/C2-NamedPipe.md
 7    - https://github.com/poweradminllc/PAExec
 8author: Nasreddine Bencherchali (Nextron Systems)
 9date: 2022/10/26
10tags:
11    - attack.execution
12    - attack.t1569.002
13logsource:
14    category: pipe_created
15    product: windows
16    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'
17detection:
18    selection:
19        PipeName|startswith: '\PAExec'
20    condition: selection
21falsepositives:
22    - Unknown
23level: medium

References

• Microsoft-365-Defender-Hunting-Queries/Command and Control/C2-NamedPipe.md at efa17a600b43c897b4b7463cc8541daa1987eeb4 · microsoft/Microsoft-365-Defender-Hunting-Queries

  

  Sample queries for Advanced hunting in Microsoft 365 Defender - microsoft/Microsoft-365-Defender-Hunting-Queries

  
  Read More

• GitHub - poweradminllc/PAExec: Remote execution, like PsExec

  

  Remote execution, like PsExec. Contribute to poweradminllc/PAExec development by creating an account on GitHub.

  
  Read More

Related rules

• PSExec and WMI Process Creations Block
• PUA - CSExec Default Named Pipe
• PUA - RemCom Default Named Pipe
• ProcessHacker Privilege Elevation
• Potential CVE-2022-26809 Exploitation Attempt