Cross-source coverage

T1546.008 / ATT&CK

Event Triggered Execution: Accessibility Features

9 rules across 4 sources.

From MITRE ATT&CK 19.2

Adversaries may establish persistence and/or elevate privileges by executing malicious content triggered by accessibility features. Windows contains accessibility features that may be launched with a key combination before a user has logged in (ex: when the user is on the Windows logon screen). An adversary can modify the way these programs are launched to get a command prompt or backdoor without logging in to the system.

Two common accessibility programs are C:\Windows\System32\sethc.exe, launched when the shift key is pressed five times and C:\Windows\System32\utilman.exe, launched when the Windows + U key combination is pressed. The sethc.exe program is often referred to as "sticky keys", and has been used by adversaries for unauthenticated access through a remote desktop login screen.

Depending on the version of Windows, an adversary may take advantage of these features in different ways. Common methods used by adversaries include replacing accessibility feature binaries or pointers/references to these binaries in the Registry. In newer versions of Windows, the replaced binary needs to be digitally signed for x64 systems, the binary must reside in %systemdir%\, and it must be protected by Windows File or Resource Protection (WFP/WRP). The Image File Execution Options Injection debugger method was likely discovered as a potential workaround because it does not require the corresponding accessibility feature binary to be replaced.

For simple binary replacement on Windows XP and later as well as and Windows Server 2003/R2 and later, for example, the program (e.g., C:\Windows\System32\utilman.exe) may be replaced with "cmd.exe" (or another program that provides backdoor access). Subsequently, pressing the appropriate key combination at the login screen while sitting at the keyboard or when connected over Remote Desktop Protocol will cause the replaced file to be executed with SYSTEM privileges.

Other accessibility features exist that may also be leveraged in a similar fashion:

  • On-Screen Keyboard: C:\Windows\System32\osk.exe
  • Magnifier: C:\Windows\System32\Magnify.exe
  • Narrator: C:\Windows\System32\Narrator.exe
  • Display Switcher: C:\Windows\System32\DisplaySwitch.exe
  • App Switcher: C:\Windows\System32\AtBroker.exe
Platforms
Windows
Telemetry
WinEventLog:Sysmon

How MITRE says to detect it DET0033

Detection Strategy for Accessibility Feature Hijacking via Binary Replacement or Registry Modification

Windows Analytic 0094

Defenders can observe suspicious replacement or tampering of system accessibility binaries (e.g., utilman.exe, sethc.exe, osk.exe) and anomalous modifications to registry keys used to redirect accessibility programs (such as IFEO keys). Additionally, execution of cmd.exe or other suspicious binaries triggered from the login screen by SYSTEM can be correlated as part of a behavior chain.

  • WinEventLog:Sysmon EventCode=11
  • WinEventLog:Sysmon EventCode=1
  • WinEventLog:Sysmon EventCode=13, 14
  • WinEventLog:Sysmon EventCode=15

SigmaHQ/sigma

6 rules
Detection Severity Format
Persistence Via Sticky Key Backdoor Critical Sigma
Sticky Key Like Backdoor Execution Critical Sigma
Sticky Key Like Backdoor Usage - Registry Critical Sigma
Potential Privilege Escalation Using Symlink Between Osk and Cmd High Sigma
Suspicious Debugger Registration Cmdline High Sigma
Potential Suspicious Activity Using SeCEdit Medium Sigma

Azure/Azure-Sentinel

1 rule
Detection Severity Format
Modification of Accessibility Features Medium KQL

elastic/detection-rules

1 rule
Detection Severity Format
Potential Modification of Accessibility Binaries High Elastic TOML

splunk/security_content

1 rule
Detection Severity Format
Overwriting Accessibility Binaries Undefined SPL

Detection rules belong to the projects that publish them and remain under their own licenses. This site indexes and links to them; it claims no rights in them.