splunk-security_content/docs/_posts/2021-03-01-ryuk_wake_on_lan_command.md

title, excerpt, categories, last_modified_at, toc, toc_label, tags

title	excerpt	categories	last_modified_at	toc	toc_label	tags
Ryuk Wake on LAN Command	Command and Scripting Interpreter, Windows Command Shell	Endpoint	2021-03-01	true		Command and Scripting Interpreter Execution Windows Command Shell Execution Splunk Enterprise Splunk Enterprise Security Splunk Cloud Endpoint

Try in Splunk Security Cloud{: .btn .btn--success}

Description

This Splunk query identifies the use of Wake-on-LAN utilized by Ryuk ransomware. The Ryuk Ransomware uses the Wake-on-Lan feature to turn on powered off devices on a compromised network to have greater success encrypting them. This is a high fidelity indicator of Ryuk ransomware executing on an endpoint. Upon triage, isolate the endpoint. Additional file modification events will be within the users profile (\appdata\roaming) and in public directories (users\public). Review all Scheduled Tasks on the isolated endpoint and across the fleet. Suspicious Scheduled Tasks will include a path to a unknown binary and those endpoints should be isolated until triaged.

• Type: TTP
• Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
• Datamodel: Endpoint
• Last Updated: 2021-03-01
• Author: Michael Haag, Splunk
• ID: 538d0152-7aaa-11eb-beaa-acde48001122

ATT&CK

ID	Technique	Tactic
T1059	Command and Scripting Interpreter	Execution

| T1059.003 | Windows Command Shell | Execution |

Search

| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time) as lastTime from datamodel=Endpoint.Processes where (Processes.process="*8 LAN*" OR Processes.process="*9 REP*") by Processes.dest Processes.user Processes.parent_process Processes.process_name Processes.process Processes.process_id Processes.parent_process_id 
| `drop_dm_object_name(Processes)` 
| `security_content_ctime(firstTime)`
| `security_content_ctime(lastTime)` 
| `ryuk_wake_on_lan_command_filter`

Associated Analytic Story

• Ryuk Ransomware

How To Implement

To successfully implement this search you need to be ingesting information on process that include the name of the process responsible for the changes from your endpoints into the Endpoint datamodel in the Processes node.

Required field

• _time
• Processes.process
• Processes.dest
• Processes.user
• Processes.parent_process
• Processes.process_name
• Processes.process
• Processes.process_id
• Processes.parent_process_id

Kill Chain Phase

• Exploitation
• Lateral Movement

Known False Positives

Limited to no known false positives.

RBA

Risk Score	Impact	Confidence	Message
63.0	70	90	A process process_name with wake on LAN commandline process in host dest

Reference

• https://www.bleepingcomputer.com/news/security/ryuk-ransomware-uses-wake-on-lan-to-encrypt-offline-devices/
• https://www.bleepingcomputer.com/news/security/ryuk-ransomware-now-self-spreads-to-other-windows-lan-devices/
• https://www.cert.ssi.gouv.fr/uploads/CERTFR-2021-CTI-006.pdf

Test Dataset

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

• https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1059.003/ryuk/windows-sysmon.log

source | version: 1