Adversaries may abuse features of Winlogon to execute DLLs and/or executables when a user logs in. Winlogon.exe is a Windows component responsible for actions at logon/logoff as well as the secure attention sequence (SAS) triggered by Ctrl-Alt-Delete. Registry entries in HKLM\Software[\Wow6432Node\]\Microsoft\Windows NT\CurrentVersion\Winlogon\ and HKCU\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\ are used to manage additional helper programs and functionalities that support Winlogon.[1]
Malicious modifications to these Registry keys may cause Winlogon to load and execute malicious DLLs and/or executables. Specifically, the following subkeys have been known to be possibly vulnerable to abuse: [1]
Adversaries may take advantage of these features to repeatedly execute malicious code and establish persistence.
| ID | Name | Description |
|---|---|---|
| S0534 | Bazar |
Bazar can use Winlogon Helper DLL to establish persistence.[2] |
| S0351 | Cannon |
Cannon adds the Registry key |
| S1066 | DarkTortilla |
DarkTortilla has established persistence via the |
| S0200 | Dipsind |
A Dipsind variant registers as a Winlogon Event Notify DLL to establish persistence.[5] |
| S0168 | Gazer |
Gazer can establish persistence by setting the value "Shell" with "explorer.exe, %malware_pathfile%" under the Registry key |
| S0387 | KeyBoy |
KeyBoy issues the command |
| S0375 | Remexi |
Remexi achieves persistence using Userinit by adding the Registry key |
| S0379 | Revenge RAT |
Revenge RAT creates a Registry key at |
| G0081 | Tropic Trooper |
Tropic Trooper has created the Registry key |
| G0010 | Turla |
Turla established persistence by adding a Shell value under the Registry key |
| G0102 | Wizard Spider |
Wizard Spider has established persistence using Userinit by adding the Registry key HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon.[14] |
| ID | Mitigation | Description |
|---|---|---|
| M1038 | Execution Prevention |
Identify and block potentially malicious software that may be executed through the Winlogon helper process by using application control [15] tools like AppLocker [16] [17] that are capable of auditing and/or blocking unknown DLLs. |
| M1018 | User Account Management |
Limit the privileges of user accounts so that only authorized administrators can perform Winlogon helper changes. |
| ID | Data Source | Data Component | Detects |
|---|---|---|---|
| DS0017 | Command | Command Execution |
Monitor executed commands and arguments that may abuse features of Winlogon to execute DLLs and/or executables when a user logs in. |
| DS0011 | Module | Module Load |
New DLLs written to System32 that do not correlate with known good software or patching may also be suspicious. Look for abnormal process behavior that may be due to a process loading a malicious DLL. Data and events should not be viewed in isolation, but as part of a chain of behavior that could lead to other activities, such as network connections made for Command and Control, learning details about the environment through Discovery, and Lateral Movement. |
| DS0009 | Process | Process Creation |
Monitor for the execution of processes that may abuse features of Winlogon to execute DLLs and/or executables when a user logs in. Analytic 1 - Modification of the Winlogon Registry Key
|
| DS0024 | Windows Registry | Windows Registry Key Modification |
Monitor for changes to Registry entries associated with Winlogon that do not correlate with known software, patch cycles, etc. Tools such as Sysinternals Autoruns may also be used to detect system changes that could be attempts at persistence, including listing current Winlogon helper values. [18] Analytic 1 - Registry Edit with Modification of Userinit, Shell or Notify
|