Detections

Explore public detection logic contributed by the community across SIEM and rule languages.

60 detections

This rule detects the execution of common accessibility tools (osk.exe, powershell.exe, pwsh.exe, cmd.exe, reg.exe) with command-line arguments indicating an attempt to modify or leverage Windows accessibility features for persistence or privilege escalation. Specifically, it looks for command lines referencing 'Software\Microsoft\Windows NT\CurrentVersion\Accessibility' and 'ATConfig\osk' or 'Accessibility\Session'. This behavior is often associated with adversaries attempting to maintain access or elevate privileges by manipulating accessibility programs like the On-Screen Keyboard.
avatar
Sotiris Mavrakis@smavrakis
avatar
Detections.ai Community
8 months ago
150282
Detects behavioral patterns
avatar
Daniel Jeremiah@daniyyell
avatar
Detections.ai Community
10 months ago
0017
Detects the creation of a symbolic link between "cmd.exe" and the accessibility on-screen keyboard binary (osk.exe) using "mklink". This technique provides an elevated command prompt to the user from the login screen without the need to log in.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
11 months ago
000
This rule detects attempts to establish persistence and elevate privileges by replacing the sticky keys executable (sethc.exe) with cmd.exe. This technique allows an attacker to gain a privileged command prompt on the Windows logon screen without authentication, typically by pressing the Shift key five times. The rule specifically looks for command-line arguments indicating the copying of cmd.exe to sethc.exe.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
1 year ago
0018
Detects the creation or modification of registry keys associated with Windows Assistive Technology applications, specifically focusing on changes to the 'ATs' and 'Configuration' keys under 'Software\Microsoft\Windows NT\CurrentVersion\Accessibility'. This activity can be indicative of persistence or privilege escalation attempts by adversaries abusing accessibility features like 'atbroker.exe'. The rule includes filters to reduce false positives from legitimate 'atbroker.exe' activity or MSI installers.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
1 year ago
0017
By replacing the sticky keys executable with the local admins CMD executable, an attacker is able to access a privileged windows console session without authenticating to the system.
When the sticky keys are "activated" the privilleged shell is launched.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
1 year ago
000
Detects scenarios where an attacker changed the IFEO settings related to sethc.
SIGMA Detection Rules@SIGMADetectionRules
SIGMA Detection Rules
1 year ago
0024
Detects scenarios where an attacker attempts to replace the original sethc.exe file by cmd.exe.
SIGMA Detection Rules@SIGMADetectionRules
SIGMA Detection Rules
1 year ago
0017
Detects scenarios where an attacker failed to replace the original sethc.exe file by cmd.exe.
SIGMA Detection Rules@SIGMADetectionRules
SIGMA Detection Rules
1 year ago
0013
Detects scenarios where an attacker attempts to replace the original sethc.exe file by cmd.exe.
SIGMA Detection Rules@SIGMADetectionRules
SIGMA Detection Rules
1 year ago
0012
Detects scenarios where an attacker attempts to enable the Image File Execution Options (IFEO) debugger for sethc.
SIGMA Detection Rules@SIGMADetectionRules
SIGMA Detection Rules
1 year ago
008
Detects scenarios where an attacker calls the stickey key and execute CMD.
SIGMA Detection Rules@SIGMADetectionRules
SIGMA Detection Rules
1 year ago
004
Detects potential suspicious behaviour using secedit.exe. Such as exporting or modifying the security policy
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
0045
Detects the registration of a debugger for a program that is available in the logon screen (sticky key backdoor).
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
0023
Detects the usage and installation of a backdoor that uses an option to register a malicious debugger for built-in tools that are accessible in the login screen
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
0019
Detects potential suspicious behaviour using secedit.exe. Such as exporting or modifying the security policy
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
0015
'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. [1]
Ref: https://attack.mitre.org/techniques/T1546/008/'
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
3096
Detects the registration of a debugger for a program that is available in the logon screen (sticky key backdoor).
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
0011
Detects the usage and installation of a backdoor that uses an option to register a malicious debugger for built-in tools that are accessible in the login screen
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
0011
This query looks for persistence or priviledge escalation done using Windows Accessibility features.
It covers some of the techniques that could be used to utilize these features for malicious purposes,.
Including attaching a debugger using a registry config or overwriting these files.
Note: some developers might use such hacks for all sort of troubleshooting and testing purposes,.
But this better be prohibited, as it allows any account with access to the machine to run processes as SYSTEM.
Read more here: https://attack.mitre.org/wiki/Technique/T1015.
Tags: #AccessibilityFeatures, #StickyKeys, #ImageFileExecutionOptions, #Debugger, #PriviledgeEscalation, #Persistence.
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
2040
Detects the usage and installation of a backdoor that uses an option to register a malicious debugger for built-in tools that are accessible in the login screen
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
006
Page 2 of 3