Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
8,410 detections
Filters
Last updated
All Time
Detection languages
3,122
2,732
773
499
379
Contributors
1,502
1,474
1,085
844
510
Categories
2,697
1,321
905
813
750
Platforms
5,935
913
886
299
280
Products / Services
1,617
1,401
1,093
454
419
MITRE Techniques
18,128
15,651
12,599
8,410
6,235
CVEs
29
27
16
16
15
IDS Classtypes
97
50
21
14
8
IDS Protocols
98
93
9
1
Detects when a security-enabled global group is deleted in a Windows environment. This activity can be indicative of an adversary attempting to remove traces of their presence or disrupt normal operations by deleting critical groups.
Detects the invocation of TabTip.exe via DCOM with a specific error ID, which is indicative of the JuicyPotatoNG tool being used in brute force mode for local privilege escalation. This technique leverages a DCOM vulnerability to elevate privileges.
Detects the execution of Scheduled Tasks where the program being run is located in a suspicious location or it's an unusual program to be run from a Scheduled Task. This rule specifically looks for Event ID 129 (Created Task Process) in the Task Scheduler Operational logs and checks if the executable path contains common temporary or user-download directories.
Detects msdt.exe creating files in suspicious directories, which could indicate exploitation of vulnerabilities like Follina (CVE-2022-30190) or Dogwalk. The rule specifically looks for file creations in common startup locations, public user directories, or system logs directories.
Detects a phishing attack which expands a ZIP file containing a malicious shortcut. If the victim expands the ZIP file via the explorer process, then the explorer process expands the malicious ZIP file and drops a malicious shortcut redirected to a backdoor into the Startup folder. Additionally, the file name of the malicious shortcut in Startup folder contains {0AFACED1-E828-11D1-9187-B532F1E9575D} meaning the folder shortcut operation.
Detects potential DLL sideloading of 'AVKkid.dll' by monitoring image load events. The rule specifically looks for 'AVKkid.dll' being loaded by any process, and then filters out legitimate loads by G DATA antivirus software from its expected installation paths. This helps identify malicious instances where 'AVKkid.dll' might be used for persistence, defense evasion, or privilege escalation outside of its legitimate context.
Detects the execution of the hacktool SharPersist, which is used to deploy various persistence mechanisms on Windows systems. The rule specifically identifies SharPersist.exe being executed with command-line arguments indicative of creating scheduled tasks, modifying startup folders, adding registry run keys, or installing new services for persistence.
This rule detects the creation of a suspicious child process by 'userinit.exe'. Userinit.exe is a legitimate Windows process responsible for initializing the user environment during logon. Malicious actors may attempt to leverage or compromise this process to execute arbitrary code, establish persistence, or elevate privileges. The rule specifically filters out legitimate child processes like 'explorer.exe' and processes related to netlogon to reduce false positives.
Detects modifications to registry keys associated with Microsoft Office add-ins, which can be used for persistence. Adversaries may abuse these autostart extensibility points (ASEPs) to execute malicious code every time an Office application starts.
This rule detects modifications to the 'DelegateExecute' registry value within the 'HKCU\Software\Classes\Folder\shell\open\command' key. This specific registry modification is a known technique used for COM hijacking, often leveraged in UAC bypasses, such as those involving sdclt.exe. An attacker can modify this key to execute an arbitrary program when a user attempts to open a folder, leading to persistence or privilege escalation.
Monitors for the creation or modification of scheduled tasks in the Windows registry by processes other than common legitimate ones like svchost.exe. This can indicate an adversary establishing persistence or executing malicious code via scheduled tasks.
Detects the setting of a new value in the Windows Registry Run key that is used by the Kapeka backdoor for persistence. Specifically, it looks for entries in `SOFTWARE\Microsoft\Windows\CurrentVersion\Run` that end with `\Sens Api` or `\OneDrive` and contain `rundll32.exe`, `.wll`, and `#1` in their details, which are indicators of Kapeka's persistence mechanism.
This rule detects the creation of scheduled tasks using `schtasks.exe` where the parent process originates from a suspicious temporary or user-specific directory. Adversaries often use scheduled tasks for persistence and privilege escalation, and executing the task creation utility from locations like `Temp`, `AppData\Local`, `AppData\Roaming`, `Temporary Internet Files`, or `Users\Public` can indicate malicious activity. Multiple malware strains have been observed employing this technique.
Detects the setting of a registry value within the `\Shell\Open\Command` key using PowerShell classes from the `System.Security.Cryptography` namespace. This technique can be used by adversaries for defense evasion, for example, to decrypt malicious payloads on the fly.
Detects when a user without the necessary permissions attempts to invite a guest user in an Azure environment, indicated by a failed 'Invite external user' operation in the audit logs. This could signify an attempt at unauthorized access, privilege escalation, or persistence.
This rule detects the successful creation of a new administrative account within an Azure environment. It specifically looks for audit log entries indicating both 'Add user' and 'Add member to role' actions occurring successfully, which signifies a user being created and then assigned a privileged role.
Detects failed authentication attempts originating from geographic locations (countries) that are not part of the organization's approved operational regions. This rule helps identify potential unauthorized access attempts or credential stuffing attacks from unexpected sources.
This rule detects a DHCP server error where a specified Callout DLL, configured in the registry, could not be loaded. This event can indicate an attempt to inject a malicious DLL into the DHCP server process for persistence, privilege escalation, or defense evasion.
This rule detects when a DHCP server loads a specified Callout DLL, which can be abused for persistence, privilege escalation, or defense evasion. Adversaries might inject malicious DLLs into legitimate processes like the DHCP server to maintain access or elevate privileges on a system.
This rule detects the creation of an executable file named 'program.exe' directly in the root of the C:\ drive. This specific file name and location are commonly associated with attempts to exploit unquoted service paths, where an attacker places a malicious executable in a higher-level directory to be executed instead of the legitimate program due to the lack of quotation marks in the service path.
This rule detects file write operations performed by 'scrcons.exe' (WMI Scripting Host). This activity is indicative of WMI persistence mechanisms, specifically the creation or modification of WMI script event consumers. Adversaries often use WMI event subscriptions to establish persistence and execute arbitrary code when a defined event occurs, such as system startup or user logon. The detection focuses on the 'Image' field, looking for the specific WMI scripting host executable.
Page 256 of 401