name: Remote WMI Command Attempt id: 272df6de-61f1-4784-877c-1fbc3e2d0838 version: 4 date: '2018-12-03' author: Rico Valdez, Michael Haag, Splunk status: production type: TTP description: The following analytic identifies usage of `wmic.exe` spawning a local or remote process, identified by the `node` switch. During triage, review parallel processes for additional commands executed. Look for any file modifications before and after `wmic.exe` execution. In addition, identify the remote endpoint and confirm execution or file modifications. Contain and isolate the endpoint as needed. data_source: - Sysmon Event ID 1 search: selection1: OriginalFileName: wmic.exe selection2: Image|endswith: wmic.exe selection3: CommandLine: '*node*' condition: (selection1 or selection2) and selection3 how_to_implement: To successfully implement this search you need to be ingesting information on process that include the name of the process responsible for the changes from your endpoints into the `Endpoint` datamodel in the `Processes` node. In addition, confirm the latest CIM App 4.20 or higher is installed and the latest TA for the endpoint product. Deprecated because duplicate of Remote Process Instantiation via WMI. known_false_positives: Administrators may use this legitimately to gather info from remote systems. Filter as needed. references: - https://github.com/redcanaryco/atomic-red-team/blob/master/atomics/T1047/T1047.yaml tags: analytic_story: - Suspicious WMI Use - Living Off The Land asset_type: Endpoint confidence: 60 impact: 60 message: A wmic.exe process $process$ contain node commandline $process$ in host $dest$ mitre_attack_id: - T1047 observable: - name: dest type: Hostname role: - Victim - name: user type: User role: - Victim product: - Splunk Enterprise - Splunk Enterprise Security - Splunk Cloud risk_score: 36 security_domain: endpoint tests: - name: True Positive Test attack_data: - data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1047/atomic_red_team/windows-sysmon.log source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational sourcetype: xmlwineventlog