Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
18,128 detections
Filters
Last updated
All Time
Detection languages
6,549
6,208
1,473
1,005
661
Contributors
3,555
2,652
2,153
2,087
1,515
Categories
7,572
3,901
1,465
1,393
1,330
Platforms
13,733
1,392
1,319
824
738
Products / Services
3,828
3,137
2,448
912
908
MITRE Techniques
18,128
15,653
12,600
8,411
6,235
CVEs
19
18
17
16
14
IDS Classtypes
305
51
24
23
22
IDS Protocols
308
136
13
10
10
This rule detects anomalous access to cloud services, specifically Salesforce, Drift, Salesloft, HubSpot, and Marketo, that may indicate OAuth token abuse. It identifies scenarios where a high volume of actions (8 or more) occur within a short timeframe (3 hours or less) from a single IP address but with multiple unique user agents (2 or more). The detection is further refined by looking for actions related to 'Add delegated permission grant' or 'Create service principal', which are indicative of an attacker attempting to establish persistence or escalate privileges after gaining access through a compromised OAuth token.
Detects installation of rootkit kernel modules for deep system hiding
Detects addition of AV exclusion paths to hide malicious files from scanning
Detects ListPlanting injection using LVM_SORTITEMS and SendMessage API
Detects process hollowing technique for code injection
Detects malware checking for user activity to detect sandbox environments
Detects suspicious chmod commands used to hide or protect malware
Identifies emails where the sender claims to be internal, but the X-MS-Exchange-Organization-AuthAs header is not set to 'Internal', indicating a potential Ghost-Sender exploit. This rule focuses on delivered emails to reduce noise and filters out expected external mail gateways and trusted automated senders.
Detects the specific Seedworm MSI dropper 'update_ms.msi' executed via msiexec. This rule identifies process execution where 'msiexec.exe' is the process and its command line contains 'update_ms.msi', indicating the execution of a known malicious MSI file associated with the Seedworm APT group.
Detects a compiled Python extension writing .py or .pyc files into a temporary or profile directory for later execution. This behavior is often associated with malware that uses Python for its runtime logic, where the compiled Python code (e.g., from Cython) extracts and drops the actual Python scripts for execution.
Detects registry or PowerShell changes that disable script block logging, module logging, or transcription before payload execution. This rule specifically looks for modifications to the PowerShell ScriptBlockLogging registry key where the EnableScriptBlockLogging or EnableScriptBlockInvocationLogging values are set to 0, indicating a disablement of these logging features.
Detects PowerShell launched with hidden or non-interactive options and encoded, compressed, or character-reassembled content. This behavior is often indicative of malicious activity, as adversaries use these techniques to evade detection and obscure their commands.
This rule detects attempts by a process, potentially a Remcos RAT loader identified by 'GST*.com' or 'GST' in its command line, to evade sandbox or virtual machine environments. It looks for the presence of common sandbox/VM indicators in the command line.
Detects potential Remcos RAT loader activity involving process hollowing or injection into browser processes. This rule specifically looks for common browser executables (iexplore.exe, chrome.exe, firefox.exe) where the initiating parent process is 'Optimax.dll' or contains 'SystemOptimizer', which are indicators associated with the Remcos RAT loader.
This rule detects suspicious process command lines that indicate the extraction of steganographically hidden payloads, potentially associated with the Remcos RAT. It specifically looks for processes with 'GST' in their name or initiating process file name, combined with keywords related to bitmap or image resource manipulation in the command line.
Detects the use of .NET Reflection methods (System.Reflection, Activator.CreateInstance, InvokeMember, MethodInfo) by processes named 'GST*.com' or 'Optimax.dll'. This behavior is indicative of obfuscation techniques often employed by malware, specifically associated with the Remcos RAT loader in this context.
Detects the execution of 'update.py' from a hidden local share, specifically '.local/share/updater/update.py'. This path is a known persistence mechanism utilized by the Miasma toolkit.
Detects unexpected processes requesting AWS IMDSv2 tokens from the link-local address 169.254.169.254. This activity can indicate an attempt to steal temporary cloud credentials from compromised EC2 instances, as seen with malware like Miasma.
Detects the creation of hidden configuration files (e.g., .sv_config.json) in hidden directories, indicating the installation or configuration phase of the SPECTRALVIPER backdoor. The rule specifically looks for files created in a directory matching the pattern `/.config/spectralviper/` or files named `.sv_config.json`.
Detects attempts to stop or disable endpoint security tools, firewalls, or mandatory access control systems (like SELinux/AppArmor) to clear the path for Miasma components. This rule specifically looks for command-line executions using 'systemctl stop' or 'service stop' in conjunction with common security tool names like 'ufw', 'iptables', 'falcon', 'sentinelone', 'apparmor', or 'selinux'.
Detects modifications to /etc/ld.so.preload or the dropping of .so files by scripting languages, a technique SPECTRALVIPER uses to hook system calls and hide its activity.
Page 427 of 864