Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
8,407 detections
Filters
Last updated
All Time
Detection languages
3,122
2,729
773
499
379
Contributors
1,502
1,474
1,085
844
510
Categories
2,695
1,319
905
813
749
Platforms
5,933
913
885
299
280
Products / Services
1,617
1,401
1,090
454
419
MITRE Techniques
18,127
15,648
12,596
8,407
6,231
CVEs
29
27
16
16
15
IDS Classtypes
97
50
21
14
8
IDS Protocols
98
93
9
1
Detects the execution of 'unshare' with flags (such as --user/--net or CLONE_NEWUSER/CLONE_NEWNET) by unprivileged users. This behavior is indicative of attempts to gain CAP_NET_ADMIN capabilities within a new namespace, a necessary precursor to exploiting the pedit COW (CVE-2026-46331) vulnerability for privilege escalation.
Detects modifications or renames to critical Windows accessibility feature binaries (sethc.exe, utilman.exe, osk.exe, magnify.exe) located in System32. Adversaries frequently replace these binaries with malicious counterparts or command shells to achieve persistence and gain SYSTEM-level execution via accessibility shortcuts at the logon screen.
Detects when common Microsoft Office applications (Word, Excel, PowerPoint, Outlook) load a DLL file from suspicious or user-writable locations such as AppData, Downloads, Documents, or Temp folders. The rule specifically alerts on DLLs that are unsigned or where the loading process itself is unsigned, which is a common indicator of side-loading or malicious library injection.
Detects the modification of registry keys within the Active Setup 'Installed Components' path, specifically targeting keys named '{RAGE-MASTER}'. The rule flags the creation or modification of a 'StubPath' value or any value containing 'win_guard_' or 'RageCore_', which are typical indicators of persistence mechanisms used by malware to execute code upon user logon.
Detects PHP processes reading both /proc/self/maps and /proc/self/mem within a short time window. This activity is indicative of an Address Space Layout Randomization (ASLR) bypass technique, specifically associated with exploits attempting to compute memory offsets for sensitive functions (e.g., zend_execute_internal, zif_system) to facilitate Remote Code Execution (RCE).
Detects Azure Privileged Identity Management (PIM) role activations that occur outside of standard business hours (before 07:00 or after 19:00 UTC, or on weekends) or involve high-privilege roles (e.g., Global Administrator, Privileged Role Administrator, Security Administrator).
Detects potential UAC bypass attempts using COM surrogate (dllhost.exe) or MMC (mmc.exe) to spawn child processes from suspicious or user-writable locations like AppData or Temp. It also monitors for specific command-line artifacts associated with BeepRAT and other potentially malicious activity.
Detects SystemBC (Coroxy) malware attempting to establish persistence by writing to Windows Registry Run or RunOnce keys. The rule specifically monitors for registry value names associated with 'socks5' proxy functionality, the presence of 'stmbc.exe' in registry data, or hidden PowerShell command strings often used by the malware for execution.
Detects the BeepRAT malware establishing persistence by creating a scheduled task named 'WindowsUpdateTempFileCleanUp' via 'schtasks.exe'. The task is configured to execute a malicious loader chain using the Tiny C Compiler to run a hidden config file, often spawned from a binary named 'HFY.exe'.
Detects anomalous activities associated with the SystemInformer (formerly Process Hacker) kernel driver service (phsvc), which is known to be leveraged for local privilege escalation (LPE). The rule identifies the execution of rundll32 with suspicious command line parameters, the spawning of SYSTEM-level child processes by the phsvc service context, and unauthorized access to the SiSvcApiPort named pipe, which is used for inter-process communication with the kernel driver.
Detects multiple suspicious activities associated with the AnyDesk remote access application, including the creation of specific named pipes, execution of processes with sensitive command-line arguments (e.g., comsvcs, impersonation privileges), non-standard DLL loads by the application, and the spawning of system-level processes. These behaviors are indicative of abuse of remote access software for post-exploitation activities or privilege escalation.
This rule detects potential persistence mechanisms by monitoring the creation of scheduled tasks using the 'schtasks' utility or modifications to Windows Registry 'Run' keys, specifically targeting suspicious paths (AppData, Temp, or ProgramData). The detection logic correlates these suspicious persistence artifacts with network activity by joining the events with Sysmon Event ID 3 (Network connection) to identify hosts communicating over common C2-associated ports (4000, 4001, 4002, 443) to non-private IP addresses. A risk score is calculated based on the presence of these persistence markers and outbound network connections.
This rule detects activity associated with the SHARDLOADER malware loader. It monitors for the presence of specific DLL files ('SolidPDFCreator.dll' or 'MediumInstStart.exe') in process image paths or process names, and explicitly checks for the creation of a unique mutex artifact named 'uydgcfteionxcfd' as a high-confidence indicator of execution.
This rule detects the creation of scheduled tasks that point to executable files located in suspicious directories such as ProgramData, Temp, or AppData. This behavior is indicative of persistence mechanisms commonly employed by the The Gentlemen Ransomware-as-a-Service (RaaS) group to maintain access and execute malicious components like backdoors or ransomware binaries.
This rule detects the execution of specific malicious npm packages (jsonwebauth, fake-font) and associated script files (lserver.js, errorHandler.js) linked to Lazarus Group activity. It monitors node.exe processes for suspicious command lines, child processes originating from associated directories, and npm installation activities involving these packages.
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 successful assignment of highly privileged roles (Global Administrator, Privileged Role Administrator, Security Administrator, Exchange Administrator) to a user in Microsoft Entra ID (formerly Azure AD). This is often a sign of privilege escalation or persistence establishment by an attacker.
Detects the creation or modification of registry keys in HKEY_CURRENT_USER\Run, targeting registry values related to remote access applications like AnyDesk, Splashtop, or Comms. The rule specifically looks for evidence that these entries are configured to execute Python interpreter executables (e.g., pythonw.exe or WPy64), which can indicate an attempt to maintain persistence using authorized software or masqueraded scripts.
Detects modifications to the Windows Registry keys under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Network. These keys control which services or drivers are permitted to load during Safe Mode with Networking. Unauthorized changes to these keys can be used to ensure malicious drivers or services load during Safe Mode, providing a persistence mechanism that bypasses many security controls.
Detects evidence of PPID spoofing associated with the StrikeShark/Cobalt Strike framework. The detection identifies suspicious child processes (e.g., cmd.exe, powershell.exe) originating from common system processes (e.g., explorer.exe, svchost.exe) while the actual ancestor is a malicious SystemSettings.exe binary located in non-standard AppData paths. It correlates these process events with account mismatches between the spoofed parent and child process, indicating CreateProcessWithTokenW usage for token impersonation.
Detects the creation of a Windows scheduled task via 'schtasks.exe' that specifically involves the 'MasterPackager.Updater' and execution of a 'script.vbs' file. This behavior is indicative of potential software deployment or persistence mechanisms utilizing VBScript within a scheduled task.
Page 42 of 401