Try in Splunk Security Cloud


The following analytic detects the wermgr.exe process attempting to connect to known IP check web services. It leverages Sysmon EventCode 22 to identify DNS queries made by wermgr.exe to specific IP check services. This activity is significant because wermgr.exe is typically used for Windows error reporting, and its connection to these services may indicate malicious code injection, often associated with malware like Trickbot. If confirmed malicious, this behavior could allow attackers to recon the infected machine's IP address, aiding in further exploitation and evasion tactics.

  • Type: TTP
  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud

  • Last Updated: 2024-05-27
  • Author: Teoderick Contreras, Mauricio Velazco, Splunk
  • ID: ed313326-a0f9-11eb-a89c-acde48001122




ID Technique Tactic
T1590 Gather Victim Network Information Reconnaissance
T1590.005 IP Addresses Reconnaissance
Kill Chain Phase
  • Reconnaissance
  • DE.CM
  • CIS 10
`sysmon` EventCode =22 process_name = wermgr.exe QueryName IN ("*", "*", "*", "*", "*", "*", "*","*", "", "", "*", "*", "*","*", "*") 
|  stats  min(_time) as firstTime max(_time) as lastTime count by Image process_name ProcessId QueryName QueryStatus QueryResults EventCode Computer 
| rename Computer as dest 
| `security_content_ctime(firstTime)` 
| `security_content_ctime(lastTime)` 
| `wermgr_process_connecting_to_ip_check_web_services_filter`


The SPL above uses the following Macros:

:information_source: wermgr_process_connecting_to_ip_check_web_services_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Required fields

List of fields required to use this analytic.

  • _time
  • process_path
  • process_name
  • process_id
  • QueryName
  • QueryStatus
  • QueryResults
  • dest
  • EventCode

How To Implement

To successfully implement this search, you need to be ingesting logs with the process name, dns query name process path , and query ststus from your endpoints like EventCode 22. If you are using Sysmon, you must have at least version 12 of the Sysmon TA.

Known False Positives


Associated Analytic Story


Risk Score Impact Confidence Message
56.0 70 80 Wermgr.exe process connecting IP location web services on $dest$

:information_source: The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.


Test Dataset

Replay any dataset to Splunk Enterprise by using our tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

source | version: 3