Suspicious Process Creation CallTrace

  1[metadata]
  2creation_date = "2021/10/24"
  3integration = ["windows"]
  4maturity = "production"
  5updated_date = "2026/05/04"
  6
  7[rule]
  8author = ["Elastic"]
  9description = """
 10Identifies when a process is created and immediately accessed from an unknown memory code region and by the same parent
 11process. This may indicate a code injection attempt.
 12"""
 13from = "now-9m"
 14index = ["winlogbeat-*", "logs-windows.sysmon_operational-*"]
 15language = "eql"
 16license = "Elastic License v2"
 17name = "Suspicious Process Creation CallTrace"
 18note = """## Triage and analysis
 19
 20### Investigating Suspicious Process Creation CallTrace
 21
 22Attackers may inject code into child processes' memory to hide their actual activity, evade detection mechanisms, and decrease discoverability during forensics. This rule looks for a spawned process by Microsoft Office, scripting, and command line applications, followed by a process access event for an unknown memory region by the parent process, which can indicate a code injection attempt.
 23
 24#### Possible investigation steps
 25
 26- 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.
 27- Investigate any abnormal behavior by the subject process such as network connections, registry or file modifications, and any spawned child processes.
 28- Investigate other alerts associated with the user/host during the past 48 hours.
 29- Inspect the host for suspicious or abnormal behavior in the alert timeframe.
 30- Create a memory dump of the child process for analysis.
 31
 32### False positive analysis
 33
 34- This activity is unlikely to happen legitimately. Benign true positives (B-TPs) can be added as exceptions if necessary.
 35
 36### Response and remediation
 37
 38- Initiate the incident response process based on the outcome of the triage.
 39- Isolate the involved host to prevent further post-compromise behavior.
 40- Remove and block malicious artifacts identified during triage.
 41- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 42- 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.
 43- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
 44- 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).
 45"""
 46
 47setup = """## Setup
 48
 49This rule requires Sysmon telemetry to be enabled and ingested.
 50
 51Setup instructions (enable the Sysmon events used by this rule):
 52- [Sysmon Event ID 1 - Process Creation](https://ela.st/sysmon-event-1-setup)
 53- [Sysmon Event ID 10 - Process Access](https://ela.st/sysmon-event-10-setup)
 54"""
 55
 56risk_score = 47
 57rule_id = "3ed032b2-45d8-4406-bc79-7ad1eabb2c72"
 58severity = "medium"
 59tags = [
 60    "Domain: Endpoint",
 61    "OS: Windows",
 62    "Use Case: Threat Detection",
 63    "Tactic: Defense Evasion",
 64    "Resources: Investigation Guide",
 65    "Data Source: Sysmon",
 66]
 67type = "eql"
 68
 69query = '''
 70sequence by host.id with maxspan=1m
 71  [process where host.os.type == "windows" and event.code == "1" and
 72   /* sysmon process creation */
 73   process.parent.name : ("winword.exe", "excel.exe", "outlook.exe", "powerpnt.exe", "eqnedt32.exe", "fltldr.exe",
 74                          "mspub.exe", "msaccess.exe","cscript.exe", "wscript.exe", "rundll32.exe", "regsvr32.exe",
 75                          "mshta.exe", "wmic.exe", "cmstp.exe", "msxsl.exe") and
 76
 77   /* noisy FP patterns */
 78   not (process.parent.name : "EXCEL.EXE" and process.executable : "?:\\Program Files\\Microsoft Office\\root\\Office*\\ADDINS\\*.exe") and
 79   not (process.executable : "?:\\Windows\\splwow64.exe" and process.args in ("8192", "12288") and process.parent.name : ("winword.exe", "excel.exe", "outlook.exe", "powerpnt.exe")) and
 80   not (process.parent.name : "rundll32.exe" and process.parent.args : ("?:\\WINDOWS\\Installer\\MSI*.tmp,zzzzInvokeManagedCustomActionOutOfProc", "--no-sandbox")) and
 81   not (process.executable :
 82            ("?:\\Program Files (x86)\\Microsoft\\EdgeWebView\\Application\\*\\msedgewebview2.exe",
 83             "?:\\Program Files\\Adobe\\Acrobat DC\\Acrobat\\Acrobat.exe",
 84             "?:\\Windows\\SysWOW64\\DWWIN.EXE") and
 85        process.parent.name : ("winword.exe", "excel.exe", "outlook.exe", "powerpnt.exe")) and
 86   not (process.parent.name : "regsvr32.exe" and process.parent.args : ("?:\\Program Files\\*", "?:\\Program Files (x86)\\*"))
 87   ] by process.parent.entity_id, process.entity_id
 88  [process where host.os.type == "windows" and event.code == "10" and
 89   /* Sysmon process access event from unknown module */
 90   winlog.event_data.CallTrace : "*UNKNOWN*"] by process.entity_id, winlog.event_data.TargetProcessGUID
 91'''
 92
 93
 94[[rule.threat]]
 95framework = "MITRE ATT&CK"
 96
 97[[rule.threat.technique]]
 98id = "T1055"
 99name = "Process Injection"
100reference = "https://attack.mitre.org/techniques/T1055/"
101
102[[rule.threat.technique.subtechnique]]
103id = "T1055.012"
104name = "Process Hollowing"
105reference = "https://attack.mitre.org/techniques/T1055/012/"
106
107[rule.threat.tactic]
108id = "TA0005"
109name = "Defense Evasion"
110reference = "https://attack.mitre.org/tactics/TA0005/"