Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
1,748 detections
Filters
Last updated
All Time
Detection languages
1,333
86
83
79
79
Contributors
515
305
271
90
67
Categories
20,440
11,814
5,871
5,145
4,864
1,748
Platforms
1,485
337
160
7
7
Products / Services
937
169
119
81
56
MITRE Techniques
759
440
326
250
242
CVEs
5
5
5
5
5
IDS Classtypes
1
This rule detects instances where specific processes (CefSharp.BrowsersSubprocess or SCef.WindowsAdapter) modify the clipboard content with strings matching common cryptocurrency wallet address patterns. This behavior is indicative of clipboard hijacking, where an adversary replaces a user's copied wallet address with their own to facilitate fraudulent transactions.
Detects process command lines containing keywords associated with resource extraction, decryption, or decompression, specifically when initiated by 'GST*.com' or involving 'Optimax.dll'. This behavior is indicative of a Remcos RAT loader attempting to unpack or prepare its payload.
This rule monitors for network connections from common developer-related processes (e.g., node, python, npm) to known blockchain RPC endpoints, followed by a subsequent network connection within 5 minutes that is not directed at those RPC endpoints or common developer infrastructure (e.g., GitHub, NPM, PyPI). This pattern is often indicative of potential malicious activity, such as a compromised development environment performing beaconing or staging data after interacting with blockchain services.
Detects attempts by the Remcos RAT loader to perform WebRTC IP leakage by monitoring process command lines for keywords like 'webrtc', 'stun', 'turn', or 'ice' when initiated by common browsers (chrome.exe, firefox.exe, opera.exe) and having a parent process related to 'Remcos'. This indicates an attempt to gather victim IP addresses.
Detects processes using prctl with PR_SET_NAME to rename themselves to systemd-userdbd, a technique used by the MYRA RAT (Operation Friday Harvest) to masquerade as a legitimate system daemon and evade process-tree inspection. The rule looks for processes with 'systemd-userdbd' in their product name or in specific suspicious folders, or processes named 'systemd-userdbd' initiated by 'node' or 'npm'. It also identifies process name changes or modifications to process primary tokens that include 'systemd-userdbd'.
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.
Identifies unauthorized attempts to leverage ssh-add or access the SSH agent socket to dump or forward local developer identities.
Detects the execution of known ransomware-related executables ('servertool.exe', 'encrypt.exe') when their command line arguments indicate interaction with cloud storage services such as OneDrive, SharePoint, GoogleDrive, Dropbox, or iCloud. This behavior is indicative of ransomware attempting to encrypt or exfiltrate data from cloud environments.
This rule detects the creation or manipulation of mutexes by processes that contain keywords associated with the Remcos RAT (Remote Access Trojan). Specifically, it looks for command-line arguments containing "Remcos_Mutex_Inj", "Remcos_Mutex", "mutex", or "CreateMutex". This activity can indicate the presence or execution of Remcos RAT on a system, as mutexes are often used by malware for single-instance enforcement or inter-process communication.
This rule detects the creation or manipulation of mutexes by processes that contain keywords associated with the Remcos RAT (Remote Access Trojan). Specifically, it looks for command-line arguments containing "Remcos_Mutex_Inj", "Remcos_Mutex", "mutex", or "CreateMutex". This activity can indicate the presence or execution of Remcos RAT on a system, as mutexes are often used by malware for single-instance enforcement or inter-process communication.
Detects command-line activity containing keywords associated with process injection or hollowing techniques (e.g., shellcode, inject, hollow, replace) when executed by common script interpreters targeting critical system processes.
This rule detects suspicious inter-process communication (IPC) attempts using WM_COPYDATA messaging, where processes (often script interpreters or unsigned binaries) interact with high-value GUI-based applications (like browsers or shell environments). This pattern is a common indicator of process injection techniques, such as hijacking existing Windows callbacks to execute code within the context of a target process.
Detects processes exhibiting behaviors indicative of process injection, such as suspicious binary names, command-line arguments related to spawning sleep processes, or ptrace system calls. This rule identifies potential attempts to inject malicious code into other processes to evade defenses or elevate privileges.
Detects the execution of ffmpeg with the '-decoders' flag to enumerate available decoders, specifically looking for the vulnerable MagicYUV decoder. It also identifies 'grep' commands searching for 'magicyuv' in process command lines, which could indicate reconnaissance or triage activity related to CVE-2026-8461.
Identifies the GhostSocks tunneling binary (or Go/Python equivalent) executing and establishing a SOCKS5 relay to an external node. This rule correlates process command line arguments indicative of GhostSocks or SOCKS5 server/relay/listen functionality with network connections on common SOCKS proxy ports (1080, 1081, 9050).
This rule monitors for processes named 'setup.exe' executing from user-writable directories (e.g., AppData, Downloads, Temp) that load unsigned or non-Microsoft DLLs from the same suspicious directories. This pattern is commonly associated with DLL side-loading or malicious installation attempts where a process attempts to load illegitimate code from local user space.
Detects SystemSettings.exe running from user-writable AppData or ProgramData directories, or SystemSettings.dll being loaded by SystemSettings.exe from these locations. This behavior is indicative of SharkLoader DLL sideloading, often used as a first stage in attacks.
Detects the execution of 'docker pull' or 'docker run' commands, excluding common base images like Microsoft, Ubuntu, Debian, and Alpine. This rule aims to identify potentially unauthorized container deployments or image pulls that could indicate malicious activity within a containerized environment.
Detects attempts to exploit the Squidbleed vulnerability (C11 strchr() Null Terminator Behavior Exploitation) by monitoring 'squid.exe' process command lines for the presence of null terminator characters or their string representations. This indicates an attempt to manipulate string handling functions.
Detects potential exploitation attempts related to the Squidbleed vulnerability by monitoring 'squid.exe' or processes with 'squid' in their command line for AddressSanitizer related keywords indicating memory safety issues like overflow, underflow, or use-after-free.
Detects potential exploitation attempts related to the Squidbleed vulnerability by monitoring 'squid.exe' process command lines for indicators of ASAN (AddressSanitizer) heap overflow reports. This includes keywords like '==', 'ERROR', 'ERROR SUMMARY', and 'SUMMARY', which are often present in ASAN crash reports.
Page 41 of 84