The following analytic identifies suspicious PowerShell script execution via EventCode 4104, where WMI is performing an event query looking for running processes or running services. This technique is commonly found in malware and APT events where the adversary will map all running security applications or services on the compromised machine. During triage, review parallel processes within the same timeframe. Review the full script block to identify other related artifacts.
- Type: TTP
Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
- Last Updated: 2021-06-14
- Author: Teoderick Contreras, Splunk
- ID: b5cd5526-cce7-11eb-b3bd-acde48001122
|T1592||Gather Victim Host Information||Reconnaissance|
Kill Chain Phase
1 2 3 4 5 `powershell` EventCode=4104 Message= "*SELECT*" AND (Message="*Win32_Process*" OR Message="*Win32_Service*") | stats count min(_time) as firstTime max(_time) as lastTime by EventCode Message ComputerName User | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)` | `wmi_recon_running_process_or_services_filter`
The SPL above uses the following Macros:
Note that wmi_recon_running_process_or_services_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
How To Implement
To successfully implement this analytic, you will need to enable PowerShell Script Block Logging on some or all endpoints. Additional setup here https://docs.splunk.com/Documentation/UBA/220.127.116.11/GetDataIn/AddPowerShell#Configure_module_logging_for_PowerShell.
Known False Positives
network administrator may used this command for checking purposes
Associated Analytic story
|30.0||30||100||Suspicious powerShell script execution by $user$ on $ComputerName$ via EventCode 4104, where WMI is performing an event query looking for running processes or running services|
source | version: 1