Conhost Spawned By Suspicious Parent Process

  1[metadata]
  2creation_date = "2020/08/17"
  3integration = ["endpoint", "windows"]
  4maturity = "production"
  5min_stack_comments = "New fields added: required_fields, related_integrations, setup"
  6min_stack_version = "8.3.0"
  7updated_date = "2024/03/28"
  8
  9[rule]
 10author = ["Elastic"]
 11description = """
 12Detects when the Console Window Host (conhost.exe) process is spawned by a suspicious parent process, which could be
 13indicative of code injection.
 14"""
 15from = "now-9m"
 16index = ["winlogbeat-*", "logs-endpoint.events.process-*", "logs-windows.sysmon_operational-*", "endgame-*"]
 17language = "eql"
 18license = "Elastic License v2"
 19name = "Conhost Spawned By Suspicious Parent Process"
 20note = """## Triage and analysis
 21
 22### Investigating Conhost Spawned By Suspicious Parent Process
 23
 24The Windows Console Host, or `conhost.exe`, is both the server application for all of the Windows Console APIs as well as the classic Windows user interface for working with command-line applications.
 25
 26Attackers often rely on custom shell implementations to avoid using built-in command interpreters like `cmd.exe` and `PowerShell.exe` and bypass application allowlisting and security features. Attackers commonly inject these implementations into legitimate system processes.
 27
 28#### Possible investigation steps
 29
 30- 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.
 31- Investigate abnormal behaviors observed by the subject process, such as network connections, registry or file modifications, and any spawned child processes.
 32- Investigate other alerts associated with the user/host during the past 48 hours.
 33- Inspect the host for suspicious or abnormal behavior in the alert timeframe.
 34- Retrieve the parent process executable and determine if it is malicious:
 35  - Use a private sandboxed malware analysis system to perform analysis.
 36    - Observe and collect information about the following activities:
 37      - Attempts to contact external domains and addresses.
 38      - File and registry access, modification, and creation activities.
 39      - Service creation and launch activities.
 40      - Scheduled task creation.
 41  - Use the PowerShell `Get-FileHash` cmdlet to get the files' SHA-256 hash values.
 42    - Search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
 43
 44### False positive analysis
 45
 46- This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 47
 48### Related rules
 49
 50- Suspicious Process from Conhost - 28896382-7d4f-4d50-9b72-67091901fd26
 51- Suspicious PowerShell Engine ImageLoad - 852c1f19-68e8-43a6-9dce-340771fe1be3
 52
 53### Response and remediation
 54
 55- Initiate the incident response process based on the outcome of the triage.
 56- Isolate the involved hosts to prevent further post-compromise behavior.
 57- If the triage identified malware, search the environment for additional compromised hosts.
 58  - Implement temporary network rules, procedures, and segmentation to contain the malware.
 59  - Stop suspicious processes.
 60  - Immediately block the identified indicators of compromise (IoCs).
 61  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
 62- Remove and block malicious artifacts identified during triage.
 63- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 64- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 65- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
 66- 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).
 67"""
 68references = [
 69    "https://www.fireeye.com/blog/threat-research/2017/08/monitoring-windows-console-activity-part-one.html",
 70]
 71risk_score = 73
 72rule_id = "05b358de-aa6d-4f6c-89e6-78f74018b43b"
 73setup = """## Setup
 74
 75If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
 76events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
 77Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
 78`event.ingested` to @timestamp.
 79For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 80"""
 81severity = "high"
 82tags = ["Domain: Endpoint", "OS: Windows", "Use Case: Threat Detection", "Tactic: Execution", "Tactic: Defense Evasion", "Tactic: Privilege Escalation", "Resources: Investigation Guide", "Data Source: Elastic Endgame", "Data Source: Elastic Defend", "Data Source: Sysmon"]
 83timestamp_override = "event.ingested"
 84type = "eql"
 85
 86query = '''
 87process where host.os.type == "windows" and event.type == "start" and
 88  process.name : "conhost.exe" and
 89  process.parent.name : ("lsass.exe", "services.exe", "smss.exe", "winlogon.exe", "explorer.exe", "dllhost.exe", "rundll32.exe",
 90                         "regsvr32.exe", "userinit.exe", "wininit.exe", "spoolsv.exe", "ctfmon.exe") and
 91  not (process.parent.name : "rundll32.exe" and
 92       process.parent.args : ("?:\\Windows\\Installer\\MSI*.tmp,zzzzInvokeManagedCustomActionOutOfProc",
 93                              "?:\\WINDOWS\\system32\\PcaSvc.dll,PcaPatchSdbTask",
 94                              "?:\\WINDOWS\\system32\\davclnt.dll,DavSetCookie"))
 95'''
 96
 97
 98[[rule.threat]]
 99framework = "MITRE ATT&CK"
100[[rule.threat.technique]]
101id = "T1059"
102name = "Command and Scripting Interpreter"
103reference = "https://attack.mitre.org/techniques/T1059/"
104
105
106[rule.threat.tactic]
107id = "TA0002"
108name = "Execution"
109reference = "https://attack.mitre.org/tactics/TA0002/"
110
111[[rule.threat]]
112framework = "MITRE ATT&CK"
113[[rule.threat.technique]]
114id = "T1036"
115name = "Masquerading"
116reference = "https://attack.mitre.org/techniques/T1036/"
117
118
119[rule.threat.tactic]
120id = "TA0005"
121name = "Defense Evasion"
122reference = "https://attack.mitre.org/tactics/TA0005/"
123
124[[rule.threat]]
125framework = "MITRE ATT&CK"
126[[rule.threat.technique]]
127id = "T1055"
128name = "Process Injection"
129reference = "https://attack.mitre.org/techniques/T1055/"
130
131
132[rule.threat.tactic]
133id = "TA0004"
134name = "Privilege Escalation"
135reference = "https://attack.mitre.org/tactics/TA0004/"