Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
442 detections
Filters
Last updated
All Time
Detection languages
177
95
67
56
11
Contributors
86
58
55
51
21
Categories
20,424
11,812
5,870
5,145
4,864
Platforms
441
8
3
3
1
Products / Services
144
116
86
36
21
MITRE Techniques
343
237
197
130
121
CVEs
3
2
1
1
1
IDS Classtypes
10
IDS Protocols
10
This rule detects attempts to modify the Windows Registry remotely, specifically targeting the 'HKLM' hive and paths containing 'shell\open\command'. This pattern is often used by adversaries to establish persistence or achieve privilege escalation by modifying how applications or the system execute commands, for example, by hijacking file associations or application startup commands. The detection is based on network traffic over TCP port 445, which is commonly used for SMB/CIFS, indicating a remote registry operation.
This rule detects modifications to Windows Registry Run keys (Run, RunOnce, RunOnceEx, Policies\Run) where the new value contains common scripting interpreters like PowerShell, cmd, cscript, or wscript, and the path is not within the System32 directory. This behavior is indicative of an adversary attempting to establish persistence by ensuring their malicious script or command executes upon user login.
This rule detects remote modification attempts of the 'Run' key within the Windows Registry, which is commonly used for persistence by malware and legitimate applications to automatically start programs when a user logs in. The detection specifically looks for network traffic on port 445 (SMB) containing the string 'CurrentVersion\Run', indicating an attempt to interact with this registry path remotely.
Detects the creation or modification of a registry run key entry named 'DadaBank' within 'Software\Microsoft\Windows\CurrentVersion\Run'. This specific registry modification is associated with the LotusLite dropper, used by the Mustang Panda threat group, to establish persistence on a compromised system.
Detects modification of registry Run keys for autostart persistence
This rule detects suspicious modifications to registry keys under 'Software\Microsoft\Windows\CurrentVersion\Policies' where the registry value data contains '.exe' or '.dll'. Such changes, especially multiple occurrences within a short timeframe (3 or more changes within an hour), can indicate ransomware activity attempting to alter file associations or execution policies to maintain persistence or execute malicious payloads.
This rule detects attempts to modify the 'Image File Execution Options' (IFEO) registry key to set a debugger for an application. This technique is often used by adversaries for persistence, allowing them to execute their malicious code whenever the legitimate application starts. The rule specifically looks for network traffic (TCP, port 445, typically SMB) containing the strings 'Image File Execution Options' and 'Debugger' in a case-insensitive manner, indicating a potential attempt to manipulate this registry setting over the network.
This rule detects network traffic to port 445 (SMB) containing the case-insensitive string "Authentication Packages". This string is often associated with the registration of malicious authentication package DLLs via the Windows Registry, a technique used for persistence and credential access. The rule specifically looks for this content in established TCP connections flowing to the home network.
Detects the creation or modification of the non-standard registry key (ms-pu\CLSID) used by the Mustang Panda PlugX variant to store its 16-character hex client identifier. This specific registry path is highly indicative of PlugX activity.
This rule generates a comprehensive forensic timeline for a specific executable file, analyzing its origin (file creation/drops), execution context (process creation and child processes), network communications (outbound connections), and persistence mechanisms (registry modifications for run keys/startup and scheduled task creation/updates). It correlates events across different data sources based on the executable's file name or SHA256 hash.
This rule detects network traffic containing the string "HKCU\\Software\\Classes\\CLSID" on TCP port 135 (DCE/RPC) directed towards the home network. This pattern is indicative of an attempt to modify registry keys related to COM objects, which can be used for persistence or privilege escalation by hijacking COM object execution.
Explorer File Visibility Downgrade
Cortex XDR
Detects modifications to Windows Explorer registry keys (Hidden, ShowSuperHidden, HideFileExt) to conceal files. This technique is often used by malware, such as GammaWorm, as a defense evasion mechanism to hide malicious artifacts from users and security tools. The rule specifically looks for changes to the 'Advanced' registry key path within 'Software\Microsoft\Windows\CurrentVersion\Explorer' that would result in files or file extensions being hidden.
Detects IFEO debugger key modification used for accessibility backdoors
This rule detects attempts to modify default file associations via the remote registry, specifically looking for 'HKCR' (HKEY_CLASSES_ROOT) and 'shell\\open\\command' within TCP traffic on port 445 (SMB). This activity is often associated with persistence mechanisms where an attacker alters how certain file types are handled to execute malicious code.
This rule detects modifications to registry keys or values associated with Potentially Unwanted Application (PUA) protection settings, specifically 'PUAProtection' and 'MpEnablePus'. Such modifications could indicate an attempt to disable or alter security features related to PUA detection.
This rule detects suspicious modifications to registry keys under 'Software\Microsoft\Windows\CurrentVersion\Policies' where the registry value data contains '.exe' or '.dll'. Such changes, especially multiple occurrences within a short timeframe (3 or more changes within an hour), can indicate ransomware activity attempting to alter file associations or execution policies to maintain persistence or execute malicious payloads.
This rule detects network traffic on TCP port 445 (SMB) containing the string "DisableRealtimeMonitoring" (case-insensitive). This string is often associated with attempts to disable real-time monitoring features of security products, typically by modifying registry keys. The detection is focused on traffic flowing from any source to the home network, specifically to the SMB port, and only on established connections. This activity is indicative of an attacker attempting to evade detection by crippling security software.
Detects the creation or modification of the 'WinDiagTrack' registry value within the Windows Run key, a known persistence mechanism used by the 10FXRAT malware. This rule specifically looks for actions that create or set registry values in 'Software\Microsoft\Windows\CurrentVersion\Run' with the name 'WinDiagTrack'.
This rule detects indicators of compromise (IOCs) associated with the Red Lamassu (JFMBackdoor) campaign. It identifies malicious file hashes, network communication with known command and control (C2) domains and IP addresses, specific file paths and names used by the malware, and registry modifications for persistence. The rule looks for file events, process creations, network connections, and registry changes that match the defined IOCs.
This rule detects modifications to registry keys or values associated with Potentially Unwanted Application (PUA) protection settings, specifically 'PUAProtection' and 'MpEnablePus'. Such modifications could indicate an attempt to disable or alter security features related to PUA detection.
This Suricata rule detects network traffic on TCP port 445 (SMB) that contains the strings "SpecialAccounts" and "UserList" (case-insensitive). This pattern is indicative of an attempt to hide a user account on a Windows system by modifying the registry's SpecialAccounts\UserList key. This technique is often used by adversaries for defense evasion.
Page 10 of 22