Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
9,759 detections
Filters
Last updated
All Time
Detection languages
3,724
2,036
1,335
1,055
969
Contributors
2,963
2,050
1,372
1,226
485
Categories
5,718
3,075
1,138
900
659
Platforms
9,646
658
432
53
30
Products / Services
10,676
9,759
6,693
4,421
3,749
MITRE Techniques
3,828
3,376
1,980
1,617
1,042
CVEs
18
14
12
12
11
This rule detects the creation of files with specific web-related extensions (.ashx, .asp, .ph, .soap) in common web server directories such as '\inetpub\wwwroot\', '\www\', '\htdocs\', or '\html\'. This activity is often indicative of an attacker uploading a web shell to maintain persistence or execute commands on the compromised web server.
Detects when an Office application loads the 'kerberos.dll' library. This behavior is unusual for standard Office operations and could indicate an attempt to manipulate Kerberos authentication, potentially for credential access or privilege escalation.
Detects the creation of named pipes commonly used by credential dumping tools such as Mimikatz (wceservicepipe) and other tools that might use 'cachedump' or 'lsadump' in their pipe names to extract credentials.
Detects access to the LSASS process by a Python-based tool, indicated by specific call trace patterns involving Python DLLs and KERNELBASE.dll/ntdll.dll, combined with a broad granted access right (0x1FFFFF). This activity is characteristic of credential dumping tools like LaZagne or Pypykatz.
Detects the creation of a PowerShell process (powershell.exe or pwsh.exe) as a child of WmiPrvSE.exe. This activity is indicative of potential lateral movement or execution via Windows Management Instrumentation (WMI), where WMI is used to spawn a PowerShell process on a system.
This rule detects modifications to registry keys that enable the Dynamic Data Exchange (DDE) protocol in Microsoft Word or Excel. Specifically, it looks for changes to 'AllowDDE' in Word or 'DisableDDEServerLaunch'/'DisableDDEServerLookup' in Excel to a value that enables DDE. Adversaries may enable DDE to execute arbitrary commands, often as part of phishing campaigns or through embedded files, to bypass macro-based defenses.
Detects specific command-line arguments used by the Conti ransomware during its execution phase. The rule looks for a combination of arguments including '-m ', '-net ', '-size ', '-nomutex ', and '-p \\', which are characteristic of Conti's encryption process. This pattern indicates the ransomware is likely attempting to encrypt files on the system or network shares.
This rule detects specific filenames, 'jpsetup.exe' and 'jpinst.exe', when they appear as the target filename in file events. These filenames have been associated with the SNAKE malware, as detailed in a CISA report. The rule aims to identify potential installations or presence of this malware on Windows systems.
Detects the creation of an Alternate Data Stream (ADS) named ':Zone.Identifier' within the WinGet temporary directory, specifically when the ZoneId is '3' (Internet) and the source URL contains suspicious IP address patterns (e.g., '://1', '://2', etc.). This indicates a file downloaded from the internet via WinGet that might originate from an untrusted or suspicious source, potentially used for defense evasion or persistence.
Detects the creation of an "Active Directory Schema Cache File" (.sch) by an uncommon process. This activity can be indicative of tools performing Active Directory-related operations, potentially for reconnaissance or command and control, such as LDAPFragger. The rule filters out common legitimate processes that create these files.
Detects suspicious local connections via a named pipe to the AD FS configuration database (Windows Internal Database). This database contains sensitive information used to sign SAML tokens. The rule specifically looks for connections to the '\MICROSOFT##WID\tsql\query' named pipe by processes other than known legitimate AD FS or Windows Internal Database components.
Detects the execution of PowerShell via the creation of a named pipe starting with 'PSHost'. This method can be used by adversaries to execute PowerShell commands or scripts, potentially bypassing traditional PowerShell logging mechanisms.
Detects uncommon or suspicious child processes of "eventvwr.exe" which might indicate a User Account Control (UAC) bypass attempt. The rule specifically filters out legitimate child processes like 'mmc.exe' and 'WerFault.exe' to reduce false positives.
This rule detects the creation of potentially suspicious child processes by 'regsvr32.exe'. Regsvr32.exe is a legitimate Windows utility that can be abused by adversaries to proxy execution of malicious code, often referred to as 'Squiblydoo'. The rule specifically looks for regsvr32.exe spawning common Windows utilities or scripting engines like calc.exe, powershell.exe, cmd.exe (implied by net.exe, net1.exe, reg.exe, schtasks.exe), mshta.exe, cscript.exe, and wscript.exe. This behavior is often indicative of defense evasion or execution techniques where regsvr32.exe is used to bypass application whitelisting or security controls.
Detects the creation of new processes using the 'wmic.exe' utility with the 'process call create' command-line arguments. This is a common technique used by adversaries for execution.
Detects tampering of RDP Terminal Service/Server sensitive settings. This includes modifications to allow unsolicited remote assistance, disable security settings, or enable RDP via specific registry keys. It also covers changes related to RDP hijacking via the 'ServiceDll' key and the 'Shadow' RDP technique.
This rule detects the creation of any Portable Executable (PE) file that is monitored by the Sysmon configuration. It specifically triggers on Sysmon Event ID 29, which corresponds to 'FileExecutableDetected'. This event indicates that Sysmon has identified and logged the creation of an executable file based on its internal configuration.
Detects the creation of specific files associated with the Goofy Guineapig malware, which attempts to impersonate Google Update components. The rule looks for 'config.dat', 'GoogleUpdate.exe', 'tmp.bat', and 'goopdate.dll' within the 'C:\ProgramData\GoogleUpdate\' directory.
This rule detects when the "System.Drawing.ni.dll" library is loaded by a process. This DLL is often used for graphical operations, including screen capturing. Its loading can indicate an attempt to capture screen content, which is a common technique used by adversaries for reconnaissance or data exfiltration.
This rule detects when PowerShell (powershell.exe or pwsh.exe) creates a new PowerShell script file (.ps1). While this behavior can be benign in many cases, it can also indicate a dropper script attempting to establish persistence on a system. The rule filters out common legitimate scenarios such as PowerShell's internal script policy tests and temporary files created in user AppData\Local\Temp or C:\Windows\Temp directories.
Detects the creation of the PROCEXP152.sys file in the application-data local temporary folder. This driver is used by Sysinternals Process Explorer but also by KDU (Kernel Driver Utility) or Ghost-In-The-Logs, which uses KDU. This activity can indicate an attempt to load a malicious driver for defense evasion or other purposes.
Page 441 of 465
