Detection rules › Splunk

WinLogon Registry Key Modified (Sysmon)

Group by
_time, host
Source
github.com/anvilogic-forge/armory

Malicious modifications to specific registry keys may cause Winlogon to load and execute malicious DLLs and/or executables. Adversaries may take advantage of these features to repeatedly execute malicious code and establish persistence. This use case detects modifications to registry values affecting Winlogon behaviors that can be abused to achieve persistence

MITRE ATT&CK coverage

References

Telemetry coverage

Rule body

id: '18431.31579'
title: WinLogon Registry Key Modified
description: 'Malicious modifications to specific registry keys may cause Winlogon
  to load and execute malicious DLLs and/or executables. Adversaries may take advantage
  of these features to repeatedly execute malicious code and establish persistence.
  This use case detects modifications to registry values affecting Winlogon behaviors
  that can be abused to achieve persistence. -- Software Association: Akira -- Atomics
  T1547.004 Test #1 Atomics T1547.004 Test #2 Atomics T1547.004 Test #3 Atomics T1547.004
  Test #4 Atomics T1547.004 Test #5 Atomics T1547.001 Test #14 Atomics T1547.001 Test
  #15'
logic_format: Splunk
logic: '`get_endpoint_data` `get_endpoint_data_sysmon` (TERM(EventCode=12) OR "<EventID>12<"
  OR TERM(EventCode=13) OR "<EventID>13<") "winlogon" | regex process="(?i)CurrentVersion\x5cWinlogon"
  | table _time, host, user, parent_process*, process, process_*, signature_id, user_id
  | bin span=1s | stats values(*) as * by _time, host '
techniques:
- persistence:boot or logon autostart execution:winlogon helper dll
- privilege-escalation:boot or logon autostart execution:winlogon helper dll
technique_id:
- T1547.004
data_category:
- Windows Sysmon
references:
- https://github.com/redcanaryco/atomic-red-team/blob/master/atomics/T1547.004/T1547.004.md#atomic-test-1---winlogon-shell-key-persistence---powershell

Stages and Predicates

Stage 1: search

`get_endpoint_data` `get_endpoint_data_sysmon` (TERM(EventCode=12) OR "<EventID>12<" OR TERM(EventCode=13) OR "<EventID>13<") "winlogon"

Stage 2: regex

| regex process="(?i)CurrentVersion\x5cWinlogon"

Stage 3: table

| table _time, host, user, parent_process*, process, process_*, signature_id, user_id

Stage 4: bucket

| bin span=1s

Stage 5: stats

| stats values(*) as * by _time, host

Indicators

These rows show field, operator, and value matches.

FieldKindValuesSearch
EventCodeeq
  • 12 corpus 9 (splunk 9)
  • 13 corpus 23 (splunk 18, kusto 5)
field:"EventID" kind:eq
processregex_match
  • "(?i)CurrentVersion\x5cWinlogon"
field:"CommandLine" kind:regex_match

Search terms

These SPL tokens match against raw event text.

StageTerm
1"<EventID>12<"
1"<EventID>13<"
1"winlogon"