Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
769 detections
Filters
Last updated
All Time
Detection languages
293
239
59
42
39
Contributors
188
145
112
101
29
Categories
20,440
11,814
5,871
5,145
4,864
769
Platforms
710
56
10
9
6
Products / Services
317
159
152
133
37
MITRE Techniques
603
504
364
327
195
CVEs
5
4
2
2
1
IDS Classtypes
7
1
IDS Protocols
9
1
Detects the creation or modification of Windows kernel-mode services using the sc.exe utility when the process is not initiated by the legitimate service control manager (services.exe). This behavior is often associated with the loading of malicious drivers or rootkits, which may attempt to bypass standard service management processes to maintain persistence or elevate privileges.
This rule correlates the creation of a new .sys file (excluding standard Windows driver directories) with the subsequent execution of sc.exe to register a kernel service. This behavior is indicative of an attacker attempting to load a malicious driver, often for persistence or rootkit capabilities, using a potentially non-standard path.
Detects the unauthorized installation and service configuration of OpenSSH Server on Windows workstations. This technique is used to establish persistent, redundant backdoor access, as observed in Operation Poisson, where adversaries deploy it to maintain access alongside other tools like Tailscale.
Detects the creation or configuration of Windows services using sc.exe or PowerShell where the binary path points to suspicious, writable directories (Temp, AppData, or ProgramData). This behavior is often associated with persistence mechanisms where adversaries place malicious binaries in user-writable locations to execute with higher privileges.
This rule monitors for suspicious activity originating from RMM software (specifically SimpleHelp) and associated TaskWeaver processes, including process execution, service/scheduled task installation, file creation consistent with Djinn Stealer, and non-standard outbound network connections.
This rule detects activities associated with 'Bring Your Own Vulnerable Driver' (BYOVD) attacks, including the loading of known vulnerable drivers, the installation or configuration of drivers via system services, and the execution of tools known to facilitate driver-based kernel manipulation.
This rule detects the 'Bring Your Own Vulnerable Driver' (BYOVD) technique by monitoring for the creation of new kernel-mode drivers in temporary locations (followed by an immediate registration as a service) that correlate with known vulnerable drivers. It checks file system events for driver drops and links them to service installation events (EventCode 7045) within a 5-minute window.
This rule detects the installation of a new Windows service by monitoring Security Event IDs 4697 and 601. It extracts details about the service name, file path, and account used. The rule flags services that have suspicious binary paths, such as those within user-writable directories (Temp, AppData, Downloads) or paths containing common living-off-the-land binaries, which may indicate persistence or the loading of malicious drivers.
Detects unauthorized usage of the RustDesk remote access tool, including process execution from suspicious parents, service installation, outbound connections to known relay infrastructure, and DNS queries for RustDesk relay domains originating from non-browser processes. This rule is designed to identify secondary or redundant remote access channels potentially established by adversaries.
Detects inbound RPC calls to the Service Control Manager interface with operation numbers corresponding to service creation and modification, which may indicate lateral movement via remote service installation.
Detects modifications to Windows service registry keys (ImagePath, Start, or Type) performed by the native reg.exe or regedit.exe command-line utilities. This behavior is often associated with the creation or modification of services for persistence or privilege escalation.
Detects the installation of a new Windows service using sc.exe from a non-standard parent process (not services.exe) or the installation of a service with an executable path located in suspicious directories such as Temp, AppData, ProgramData, or Users folders.
Detects the creation of a kernel service pointing to a .sys file located outside the standard Windows system driver directory. This pattern is indicative of a kernel driver being dropped and registered for persistence, a common step in the installation of rootkits or malicious kernel-mode drivers.
This rule detects potentially malicious modifications to Windows service registry keys. It monitors the 'Services' registry hive for changes to the 'Start' value to identify services set to start automatically or at boot, or modifications to the 'ImagePath' value that do not conform to expected system-protected paths. This behavior is indicative of an adversary attempting to establish persistence by creating or modifying a malicious service.
This rule monitors for the creation of a new .sys file outside of the standard Windows system driver directories (System32 or SysWOW64) within a 15-minute window of a corresponding registry update to the 'ImagePath' of a service. This sequence is indicative of a persistence mechanism involving the installation of a potentially malicious kernel-mode driver, often used by rootkits or malware to achieve high-privilege execution.
This rule detects suspicious activity associated with the 'MixedSvc' service and potential DLL side-loading. It identifies the creation of a Windows service named 'MixedSvc' using sc.exe, the execution of 'Mixed Reality.exe' from a Windows Media Player directory, the side-loading of 'nvdaHelperRemote.dll' within the Windows Media Player directory, and the execution of svchost.exe with 'Mixed Reality.exe' as its parent/causality actor, which is indicative of malicious injection and persistence mechanisms.
Detects indicators of 'Bring Your Own Vulnerable Driver' (BYOVD) attacks or suspicious kernel driver installations. The rule monitors for known vulnerable driver files being written to disk, unauthorized creation of .sys files in temporary directories, the installation of new kernel driver services via System Event ID 7045 (referencing temp paths or known malicious drivers), and the use of the sc.exe utility to create services with a kernel driver type.
Detects the installation of a new Windows service where the ImagePath contains strings commonly associated with remote access or remote control software, such as 'remotepc' or 'rpclient'. This may indicate the unauthorized deployment of remote administration tools.
This rule detects the installation of new Windows services (EventID 7045) where the service's executable path (ServiceFileName) contains common scripting interpreters like 'cmd', 'powershell', or 'wscript'. This pattern can indicate an adversary attempting to establish persistence or execute malicious code via a newly created service that leverages scripting capabilities.
This rule detects the creation of a Windows service where the service type is set to 'kernel' via the sc.exe command-line utility. This behavior is indicative of an attempt to load a kernel driver or perform low-level system modifications, which is often used by rootkits or malicious drivers. The rule filters out known trusted publishers to reduce noise.
Detects the creation of new Windows services through suspicious or unexpected process chains. This includes services spawned by WinGet/DSC components, services created by sc.exe where the process path points to user-writable directories (e.g., Temp, AppData, User profiles), or system event logs (Event ID 7045) indicating service installation from non-standard locations. This rule is designed to identify potential persistence mechanisms or privilege escalation attempts involving unauthorized service creation.
Page 16 of 37