Potential Windows Error Manager Masquerading

  1[metadata]
  2creation_date = "2020/08/24"
  3integration = ["endpoint", "windows"]
  4maturity = "production"
  5updated_date = "2025/03/20"
  6
  7[transform]
  8[[transform.osquery]]
  9label = "Osquery - Retrieve DNS Cache"
 10query = "SELECT * FROM dns_cache"
 11
 12[[transform.osquery]]
 13label = "Osquery - Retrieve All Services"
 14query = "SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"
 15
 16[[transform.osquery]]
 17label = "Osquery - Retrieve Services Running on User Accounts"
 18query = """
 19SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE
 20NOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR
 21user_account == null)
 22"""
 23
 24[[transform.osquery]]
 25label = "Osquery - Retrieve Service Unsigned Executables with Virustotal Link"
 26query = """
 27SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,
 28services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =
 29authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'
 30"""
 31
 32
 33[rule]
 34author = ["Elastic"]
 35description = """
 36Identifies suspicious instances of the Windows Error Reporting process (WerFault.exe or Wermgr.exe) with matching
 37command-line and process executable values performing outgoing network connections. This may be indicative of a
 38masquerading attempt to evade suspicious child process behavior detections.
 39"""
 40false_positives = ["Legit Application Crash with rare Werfault commandline value"]
 41from = "now-9m"
 42index = [
 43    "winlogbeat-*",
 44    "logs-endpoint.events.process-*",
 45    "logs-endpoint.events.network-*",
 46    "logs-windows.sysmon_operational-*",
 47]
 48language = "eql"
 49license = "Elastic License v2"
 50name = "Potential Windows Error Manager Masquerading"
 51note = """## Triage and analysis
 52
 53### Investigating Potential Windows Error Manager Masquerading
 54
 55By examining the specific traits of Windows binaries -- such as process trees, command lines, network connections, registry modifications, and so on -- it's possible to establish a baseline of normal activity. Deviations from this baseline can indicate malicious activity, such as masquerading and deserve further investigation.
 56
 57This rule identifies a potential malicious process masquerading as `wermgr.exe` or `WerFault.exe`, by looking for a process creation with no arguments followed by a network connection.
 58
 59> **Note**:
 60> This investigation guide uses the [Osquery Markdown Plugin](https://www.elastic.co/guide/en/security/current/invest-guide-run-osquery.html) introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
 61
 62#### Possible investigation steps
 63
 64- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 65- Investigate other alerts associated with the user/host during the past 48 hours.
 66- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications, and any spawned child processes.
 67- Examine the host for derived artifacts that indicate suspicious activities:
 68  - Analyze the process executable using a private sandboxed analysis system.
 69  - Observe and collect information about the following activities in both the sandbox and the alert subject host:
 70    - Attempts to contact external domains and addresses.
 71      - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process' `process.entity_id`.
 72      - Examine the DNS cache for suspicious or anomalous entries.
 73        - $osquery_0
 74    - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
 75    - Examine the host services for suspicious or anomalous entries.
 76      - $osquery_1
 77      - $osquery_2
 78      - $osquery_3
 79  - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
 80- Investigate potentially compromised accounts. Analysts can do this by searching for login events (for example, 4624) to the target host after the registry modification.
 81
 82
 83### False positive analysis
 84
 85- This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 86
 87### Response and remediation
 88
 89- Initiate the incident response process based on the outcome of the triage.
 90- Isolate the involved host to prevent further post-compromise behavior.
 91- If the triage identified malware, search the environment for additional compromised hosts.
 92  - Implement temporary network rules, procedures, and segmentation to contain the malware.
 93  - Stop suspicious processes.
 94  - Immediately block the identified indicators of compromise (IoCs).
 95  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 96- Remove and block malicious artifacts identified during triage.
 97- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 98- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
 99- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
100"""
101references = [
102    "https://twitter.com/SBousseaden/status/1235533224337641473",
103    "https://www.hexacorn.com/blog/2019/09/20/werfault-command-line-switches-v0-1/",
104    "https://app.any.run/tasks/26051d84-b68e-4afb-8a9a-76921a271b81/",
105    "https://www.elastic.co/security-labs/elastic-security-uncovers-blister-malware-campaign",
106]
107risk_score = 47
108rule_id = "6ea41894-66c3-4df7-ad6b-2c5074eb3df8"
109severity = "medium"
110tags = [
111    "Domain: Endpoint",
112    "OS: Windows",
113    "Use Case: Threat Detection",
114    "Tactic: Defense Evasion",
115    "Resources: Investigation Guide",
116    "Data Source: Elastic Defend",
117    "Data Source: Sysmon",
118]
119type = "eql"
120
121query = '''
122sequence by host.id, process.entity_id with maxspan = 5s
123  [process where host.os.type == "windows" and event.type:"start" and process.name : ("wermgr.exe", "WerFault.exe") and process.args_count == 1]
124  [network where host.os.type == "windows" and process.name : ("wermgr.exe", "WerFault.exe") and network.protocol != "dns" and
125    network.direction : ("outgoing", "egress") and destination.ip !="::1" and destination.ip !="127.0.0.1"
126  ]
127'''
128
129
130[[rule.threat]]
131framework = "MITRE ATT&CK"
132[[rule.threat.technique]]
133id = "T1036"
134name = "Masquerading"
135reference = "https://attack.mitre.org/techniques/T1036/"
136[[rule.threat.technique.subtechnique]]
137id = "T1036.005"
138name = "Match Legitimate Name or Location"
139reference = "https://attack.mitre.org/techniques/T1036/005/"
140
141
142
143[rule.threat.tactic]
144id = "TA0005"
145name = "Defense Evasion"
146reference = "https://attack.mitre.org/tactics/TA0005/"