Query: detection rule: Detects default CSExec pipe creation
Matching passage: Sigma rule: Detects default CSExec pipe creation. Logsource: windows / pipe_created. Rule: title: PUA - CSExec Default Named Pipe id: f318b911-ea88-43f4-9281-0de23ede628e related: - id: 9e77ed63-2ecf-4c7b-b09d-640834882028 type: obsolete status: test description: Detects default CSExec pipe creation references: - https://drive.google.com/file/d/1lKya3_mLnR3UQuCoiYruO3qgu052_iS_/view - https://github.com/malcomvetter/CSExec author: Nikita Nazarov, oscd.community, Nasreddine Bencherchali (Nextron Systems) date: 2023-08-07 modified: 2023-11-30 tags: - attack.lateral-movement - attack.t1021.002 - attack.execution - attack.t1569.002 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: PipeName|contains: \csexecsvc condition: selection falsepositives: - Legitimate Administrator activity level: medium
Near-miss passage: Sigma rule: Detects loading of known malicious drivers via the file name of the drivers.. Logsource: windows / driver_load. Rule: title: Malicious Driver Load By Name id: 39b64854-5497-4b57-a448-40977b8c9679 status: test description: Detects loading of known malicious drivers via the file name of the drivers. references: - https://loldrivers.io/ author: Nasreddine Bencherchali (Nextron Systems) date: 2022-10-03 modified: 2023-12-02 tags: - attack.persistence - attack.privilege-escalation - attack.t1543.003 - attack.t1068 logsource: product: windows category: driver_load detection: selection: ImageLoaded|endswith: - \wfshbr64.sys - \ktmutil7odm.sys - \ktes.sys - \a26363e7b02b13f2b8d697abb90cd5c3.sys - \kt2.sys - \4748696211bd56c2d93c21cab91e82a5.sys - \malicious.sys - \a236e7d654cd932b7d11cb604629a2d0.sys - \spwizimgvt.sys - \c94f405c5929cfcccc8ad00b42c95083.sys - \fur.sys - \wantd.sys - \windbg.sys - \4118b86e490aed091b1a219dba45f332.sys - \gmer64.sys - \1fc7aeeff3ab19004d2e53eae8160ab1.sys - \poortry2.sys - \wintapix.sys - \daxin_blank6.sys - \6771b13a53b9c7449d4891e427735ea2.sys - \blacklotus_driver.sys - \air_system10.sys - \dkrtk.sys - \7.sys - \sense5ext.sys - \ktgn.sys - \ndislan.sys - \nlslexicons0024uvn.sys - \be6318413160e589080df02bb3ca6e6a.sys - \4.sys - \wantd_2.sys - \e29f6311ae87542b3d693c1f38e4e3ad.sys - \daxin_blank3.sys - \gftkyj64.sys - \daxin_blank2.sys - \wantd_4.sys - \reddriver.sys - \834761775.sys - \mlgbbiicaihflrnh.sys - \mjj0ge.sys - \daxin_blank.sys - \daxin_blank5.sys - \poortry1.sys - \msqpq.sys - \mimidrv.sys - \e939448b28a4edc81f1f974cebf6e7d2.sys - \prokiller64.sys - \nodedriver.sys - \wantd_3.sys - \lctka.sys - \kapchelper_x64.sys - \daxin_blank4.sys - \a9df5964635ef8bd567ae487c3d214c4.sys - \wantd_6.sys - \ntbios.sys - \wantd_5.sys - \pciecubed.sys - \mimikatz.sys - \nqrmq.sys - \2.sys - \poortry.sys - \ntbios_2.sys - \fgme.sys - \telephonuafy.sys - \typelibde.sys - \daxin_blank1.sys - \ef0e1725aaf0c6c972593f860531a2ea.sys - \5a4fe297c7d42539303137b6d75b150d.sys condition: selection falsepositives: - False positives may occur if one of the vulnerable driver names mentioned above didn't change its name between versions. So always make sure that the driver being loaded is the legitimate one and the non vulnerable version. - If you experience a lot of FP you could comment the driver name or its exact known legitimate location (when possible) level: medium