Suspicious File Creation via Kworker

  1[metadata]
  2creation_date = "2023/10/26"
  3integration = ["endpoint"]
  4maturity = "production"
  5min_stack_comments = "New fields added: required_fields, related_integrations, setup"
  6min_stack_version = "8.3.0"
  7updated_date = "2024/02/21"
  8
  9[transform]
 10[[transform.osquery]]
 11label = "Osquery - Retrieve File Listing Information"
 12query = """
 13SELECT * FROM file WHERE path = {{file.path}}
 14"""
 15[[transform.osquery]]
 16label = "Osquery - Retrieve Additional File Listing Information"
 17query = """
 18SELECT
 19  f.path,
 20  u.username AS file_owner,
 21  g.groupname AS group_owner,
 22  datetime(f.atime, 'unixepoch') AS file_last_access_time,
 23  datetime(f.mtime, 'unixepoch') AS file_last_modified_time,
 24  datetime(f.ctime, 'unixepoch') AS file_last_status_change_time,
 25  datetime(f.btime, 'unixepoch') AS file_created_time,
 26  f.size AS size_bytes
 27FROM
 28  file f
 29  LEFT JOIN users u ON f.uid = u.uid
 30  LEFT JOIN groups g ON f.gid = g.gid
 31WHERE path = {{file.path}}
 32"""
 33
 34[[transform.osquery]]
 35label = "Osquery - Retrieve Running Processes by User"
 36query = "SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"
 37
 38[[transform.osquery]]
 39label = "Osquery - Retrieve Crontab Information"
 40query = "SELECT * FROM crontab"
 41
 42[[transform.osquery]]
 43label = "Osquery - Retrieve Listening Ports"
 44query = "SELECT pid, address, port, socket, protocol, path FROM listening_ports"
 45
 46[[transform.osquery]]
 47label = "Osquery - Retrieve Open Sockets"
 48query = "SELECT pid, family, remote_address, remote_port, socket, state FROM process_open_sockets"
 49
 50[[transform.osquery]]
 51label = "Osquery - Retrieve Information for a Specific User"
 52query = "SELECT * FROM users WHERE username = {{user.name}}"
 53
 54[[transform.osquery]]
 55label = "Osquery - Investigate the Account Authentication Status"
 56query = "SELECT * FROM logged_in_users WHERE user = {{user.name}}"
 57
 58[rule]
 59author = ["Elastic"]
 60description = """
 61This rule monitors for a file creation event originating from a kworker parent process. kworker, or kernel worker, 
 62processes are part of the kernel's workqueue mechanism. They are responsible for executing work that has been scheduled
 63to be done in kernel space, which might include tasks like handling interrupts, background activities, and other
 64kernel-related tasks. Attackers may attempt to evade detection by masquerading as a kernel worker process.
 65"""
 66from = "now-9m"
 67index = ["logs-endpoint.events.*"]
 68language = "eql"
 69license = "Elastic License v2"
 70name = "Suspicious File Creation via Kworker"
 71note = """## Triage and analysis
 72
 73### Investigating Suspicious File Creation via Kworker
 74
 75Kworker, or kernel worker, processes are part of the kernel's workqueue mechanism. They are responsible for executing work that has been scheduled to be done in kernel space, which might include tasks like handling interrupts, background activities, and other kernel-related tasks.
 76
 77Attackers may attempt to evade detection by masquerading as a kernel worker process.
 78
 79This rule monitors for suspicious file creation events through the kworker process. This is not common, and could indicate malicious behaviour.
 80
 81> **Note**:
 82> This investigation guide uses the [Osquery Markdown Plugin](https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html) introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
 83> This investigation guide uses [placeholder fields](https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html) to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
 84
 85#### Possible Investigation Steps
 86
 87- Investigate the file that was created or modified through OSQuery.
 88  - $osquery_0
 89  - $osquery_1
 90- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
 91  - $osquery_2
 92- Investigate other alerts associated with the user/host during the past 48 hours.
 93- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
 94- Investigate whether the altered scripts call other malicious scripts elsewhere on the file system. 
 95  - If scripts or executables were dropped, retrieve the files and determine if they are malicious:
 96    - Use a private sandboxed malware analysis system to perform analysis.
 97      - Observe and collect information about the following activities:
 98        - Attempts to contact external domains and addresses.
 99          - Check if the domain is newly registered or unexpected.
100          - Check the reputation of the domain or IP address.
101        - File access, modification, and creation activities.
102        - Cron jobs, services and other persistence mechanisms.
103            - $osquery_3
104- Investigate abnormal behaviors by the subject process/user such as network connections, file modifications, and any other spawned child processes.
105  - Investigate listening ports and open sockets to look for potential command and control traffic or data exfiltration.
106    - $osquery_4
107    - $osquery_5
108  - Identify the user account that performed the action, analyze it, and check whether it should perform this kind of action.
109    - $osquery_6
110- Investigate whether the user is currently logged in and active.
111    - $osquery_7
112
113### False Positive Analysis
114
115- If this activity is related to new benign software installation activity, consider adding exceptions — preferably with a combination of user and command line conditions.
116- If this activity is related to a system administrator that performed these actions for administrative purposes, consider adding exceptions for this specific administrator user account. 
117- Try to understand the context of the execution by thinking about the user, machine, or business purpose. A small number of endpoints, such as servers with unique software, might appear unusual but satisfy a specific business need.
118
119### Related Rules
120
121- Suspicious Kworker UID Elevation - 7dfaaa17-425c-4fe7-bd36-83705fde7c2b
122- Network Activity Detected via Kworker - 25d917c4-aa3c-4111-974c-286c0312ff95
123
124### Response and remediation
125
126- Initiate the incident response process based on the outcome of the triage.
127- Isolate the involved host to prevent further post-compromise behavior.
128- If the triage identified malware, search the environment for additional compromised hosts.
129  - Implement temporary network rules, procedures, and segmentation to contain the malware.
130  - Stop suspicious processes.
131  - Immediately block the identified indicators of compromise (IoCs).
132  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
133- 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.
134- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
135- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
136- Leverage the incident response data and logging to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
137"""
138risk_score = 47
139rule_id = "ae343298-97bc-47bc-9ea2-5f2ad831c16e"
140setup = """## Setup
141
142This rule requires data coming in from Elastic Defend.
143
144### Elastic Defend Integration Setup
145Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows
146the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
147
148#### Prerequisite Requirements:
149- Fleet is required for Elastic Defend.
150- To configure Fleet Server refer to the [documentation](https://www.elastic.co/guide/en/fleet/current/fleet-server.html).
151
152#### The following steps should be executed in order to add the Elastic Defend integration on a Linux System:
153- Go to the Kibana home page and click Add integrations.
154- In the query bar, search for Elastic Defend and select the integration to see more details about it.
155- Click Add Elastic Defend.
156- Configure the integration name and optionally add a description.
157- Select the type of environment you want to protect, either Traditional Endpoints or Cloud Workloads.
158- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. [Helper guide](https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html).
159- We suggest to select "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
160- Enter a name for the agent policy in New agent policy name. If other agent policies already exist, you can click the Existing hosts tab and select an existing policy instead.
161For more details on Elastic Agent configuration settings, refer to the [helper guide](https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html).
162- Click Save and Continue.
163- To complete the integration, select Add Elastic Agent to your hosts and continue to the next section to install the Elastic Agent on your hosts.
164For more details on Elastic Defend refer to the [helper guide](https://www.elastic.co/guide/en/security/current/install-endpoint.html).
165"""
166severity = "medium"
167tags = [
168        "Domain: Endpoint",
169        "OS: Linux",
170        "Use Case: Threat Detection",
171        "Tactic: Persistence",
172        "Tactic: Defense Evasion",
173        "Data Source: Elastic Defend"
174        ]
175timestamp_override = "event.ingested"
176type = "eql"
177query = '''
178file where event.action in ("creation", "file_create_event") and process.name : "kworker*" and not (
179  (process.name : "kworker*kcryptd*") or 
180  (file.path : ("/var/log/*", "/var/crash/*", "/var/run/*", "/var/lib/systemd/coredump/*", "/var/spool/*"))
181)
182'''
183
184[[rule.threat]]
185framework = "MITRE ATT&CK"
186
187[[rule.threat.technique]]
188id = "T1547"
189name = "Boot or Logon Autostart Execution"
190reference = "https://attack.mitre.org/techniques/T1547/"
191
192[rule.threat.tactic]
193id = "TA0003"
194name = "Persistence"
195reference = "https://attack.mitre.org/tactics/TA0003/"
196
197[[rule.threat]]
198framework = "MITRE ATT&CK"
199
200[rule.threat.tactic]
201id = "TA0005"
202name = "Defense Evasion"
203reference = "https://attack.mitre.org/tactics/TA0005/"
204
205[[rule.threat.technique]]
206name = "Rootkit"
207id = "T1014"
208reference = "https://attack.mitre.org/techniques/T1014/"