Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
979 detections
Filters
Last updated
All Time
Detection languages
467
248
152
48
27
Contributors
196
172
133
106
90
Categories
463
262
226
216
121
Platforms
968
2
2
1
1
Products / Services
321
203
165
53
46
MITRE Techniques
18,123
15,639
12,580
8,394
6,215
979
CVEs
5
2
1
1
1
IDS Classtypes
2
IDS Protocols
2
Detects the modification of specific CLSID registry keys related to the .NET NGEN scheduled task. This Component Object Model (COM) hijacking technique is used by the threat actor 'Curly COMrades' to establish persistence for their 'MucorAgent' backdoor.
Detects the creation or modification of registry values used by the HIDDENDRIVER rootkit to configure its hiding and protection capabilities. This rootkit, a modified version of the open-source "Hidden" project, uses these registry entries to define which files, processes, and registry keys to conceal. This activity is associated with the REF3927 threat actor and the TOLLBOOTH malware campaign.
Detects changes to the ClickOnce trust prompt registry key to enable installations from various locations, such as the Internet. This modification can allow an attacker to bypass security prompts and execute untrusted code via ClickOnce applications.
Detects the setting of the "ImagePath" value of a service registry key to a path controlled by a non-administrator user such as "\AppData\" or "\ProgramData\". Attackers often use such directories for staging purposes. This rule might also trigger on badly written software, where if an attacker controls an auto starting service, they might achieve persistence or privilege escalation. Note that while ProgramData is a user controlled folder, software might apply strict ACLs which makes them only accessible to admin users. Remove such folders via filters if you experience a lot of noise.
Detects specific registry markers associated with the FlowCloud malware, which is known to be used by the threat group TA410. The rule identifies unique registry paths where FlowCloud stores its configuration and drivers for its keylogger components.
This rule detects remote procedure calls (RPC) to modify the Windows Registry, which can be indicative of lateral movement or persistence mechanisms. Specifically, it monitors for RPC Firewall events with EventID 3 and an InterfaceUuid corresponding to the Remote Registry Protocol (338cd001-2244-31f1-aaaa-900038001003), focusing on specific operation numbers (OpNum) that represent various registry modification functions. This activity could be used by attackers to establish persistence, evade defenses, or execute code remotely.
This rule detects attempts to downgrade NetNTLM security settings by monitoring modifications to specific registry keys related to LSA (Local Security Authority) configuration. Specifically, it looks for changes to 'LmCompatibilityLevel', 'NtlmMinClientSec', and 'RestrictSendingNTLMTraffic' within the 'SYSTEM\ControlSet\Control\Lsa' registry path. Such modifications can weaken NTLM authentication security, potentially enabling downgrade attacks where an attacker forces a less secure authentication protocol.
This rule detects the creation of registry keys associated with NetWire RAT. Specifically, it looks for the creation of a registry key containing '\software\NetWire' in its path, which is a known location where NetWire RAT stores its configuration information.
Detects when a user enables DNS-over-HTTPS (DoH) by modifying specific registry keys for Microsoft Edge, Google Chrome, or Mozilla Firefox. Enabling DoH can obscure internet activity, potentially aiding in data exfiltration or evading network monitoring, as it encrypts DNS queries and bypasses traditional DNS visibility.
This rule detects the creation of specific registry keys under 'Software\AppDataLow\Software\Microsoft\' that are known to be associated with Ursnif malware. The rule filters out common legitimate registry paths used by Internet Explorer, RepService, IME, and Edge to reduce false positives.
Detects an attacker trying to enable the Outlook security setting "EnableUnsafeClientMailRules" which allows Outlook to run applications or execute macros. This can be used for persistence or defense evasion.
This rule detects the creation or modification of specific registry keys that have been observed in attacks attributed to the OceanLotus (also known as APT32) threat group. The rule specifically looks for patterns in `TargetObject` paths related to CLSID entries and `AppX` entries within `HKCU\SOFTWARE\Classes` and `HKCU\SOFTWARE\App`.
Detects remote registry management attempts using the 'reg' utility originating from a workstation not designated as an administrator workstation. This could indicate an attacker attempting to query or modify the registry of a remote system from an unauthorized host.
Detects the deletion of registry entries within the `.*\shell\open\command` keys. This activity is often associated with COM hijacking, where an attacker modifies these keys to execute their malicious code instead of legitimate applications. The deletion of these keys could indicate an adversary attempting to remove traces of their COM hijacking activities.
This rule detects attempts to modify system services or WMI settings, which are behaviors associated with the Blue Mockingbird cryptominer. Specifically, it looks for 'sc config' commands that include 'wercplsupporte.dll' and 'wmic.exe' commands ending with 'COR_PROFILER'. These command-line patterns indicate potential persistence or defense evasion mechanisms used by the threat.
Detects specific Windows registry modifications made by BlackByte ransomware variants. BlackByte sets three different registry values to escalate privileges and begin setting the stage for lateral movement and encryption. This rule triggers when any of the specified registry keys are set to DWORD 1.
Detects file access requests to files ending with either the ".hive" or ".reg" extension, which are typically associated with Windows Registry backups. The rule specifically looks for these accesses by applications not located in common system directories (C:\Program Files (x86)\, C:\Program Files\, C:\Windows\System32\, C:\Windows\SysWOW64\), indicating potentially suspicious activity by uncommon or unauthorized applications.
Detects changes to the registry keys related to "Trusted Location" of Microsoft Office. Attackers might add additional trusted locations to avoid macro security restrictions.
This rule detects attempts to tamper with Sysmon's operational settings by monitoring changes to specific registry keys related to Sysmon's event publishers and channels. Specifically, it looks for modifications that disable Sysmon's 'Enabled' status (EventID 4657, NewValue 0) or attempts to delete the Sysmon operational channel (EventID 4663, AccessMask '0x10000'). This activity could indicate a threat actor trying to evade detection by disabling or muting Sysmon logging.
Detects registry value settings that would replace the user's desktop background. This is a common technique used by malware to change the desktop background to a ransom note or other image.
Detects registry persistence used by the OilRig APT group, specifically looking for modifications to the 'SOFTWARE\Microsoft\Windows\CurrentVersion\UMe' or 'SOFTWARE\Microsoft\Windows\CurrentVersion\UT' registry keys. This activity was reported by Nyotron in their March 2018 report.
Page 26 of 47