Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
2,087 detections
Filters
Last updated
All Time
Detection languages
937
671
245
95
67
Contributors
798
791
99
59
31
Categories
1,168
1,065
225
210
171
Platforms
1,856
493
300
26
12
Products / Services
10,670
9,758
6,693
4,421
3,749
2,087
MITRE Techniques
760
704
336
308
240
CVEs
8
7
6
6
6
IDS Protocols
1
Detects unauthorized processes reading AI assistant configuration files (e.g., Claude, Cursor, Gemini, VS Code) followed by an outbound network connection from a common scripting or runtime environment (node, python, bun) within 60 seconds, potentially indicating credential or configuration exfiltration.
Detects execution of AWS STS commands to identify the caller's identity in conjunction with suspicious outbound POST requests. This pattern is commonly used by adversaries to verify compromised cloud credentials or enumerate permissions within an AWS environment.
This rule detects processes that load 'amsi.dll' followed by a call to 'VirtualProtectApiCall' with 'PAGE_EXECUTE_READWRITE' memory protection flags within a 30-second window. This behavioral pattern is frequently used in fileless execution techniques to disable Antimalware Scan Interface (AMSI) or to facilitate the execution of shellcode by modifying memory permissions.
Detects the creation of a Windows scheduled task using 'schtasks.exe' that triggers on system startup or login, while simultaneously referencing specific keywords ('RageGuard', 'win_guard_', 'RageCore_') in the command line, suggesting the persistence of a specific malicious utility.
This rule detects a sequence of Windows API calls indicative of process injection behavior associated with the VSHELL RAT (UNC5221). The detection monitors for the combination of VirtualAllocEx (with page permissions allowing execution), WriteProcessMemory, and QueueUserAPC or NtQueueApcThread targeting common Windows system processes (svchost.exe, explorer.exe, notepad.exe) from the same source process within a one-minute window.
Detects the execution of cmd.exe with arguments that combine 'fsutil volume setZeroData' (often used to corrupt or delete data) and 'del /f' (forced file deletion) in a single command line, likely indicating malicious file cleanup or anti-forensics activity.
This rule detects activities associated with the VILE ransomware, specifically the creation of file staging artifacts (vile_user_files.zip), execution of associated binaries, and network communication with Gofile.io infrastructure used for exfiltration.
Detects processes running at High or System integrity levels that correlate with the creation of specific file artifacts known to be associated with VILE ransomware. The rule monitors for potential privilege escalation or token manipulation indicative of the ransomware's attempt to gain necessary permissions for encryption operations.
Detects the execution of a malicious file disguised as 'wusvc.exe' originating from the user Downloads folder. The rule also monitors for suspicious network connections from this process to a known C2 IP address and detects potential defensive evasion techniques such as memory protection changes (PAGE_EXECUTE_READWRITE) used for syscall stub patching or AMSI bypass in non-Microsoft signed versions of this process.
Detects the execution of notepad.exe where the command line arguments reference a file path located in 'C:\temp\' and include a filename typical of ransomware notes, such as 'HowToRestoreFiles.txt'. This behavior is characteristic of ransomware displaying instructions to the victim after file encryption.
Detects the execution of known command-line utilities, script interpreters, or installers spawned by web browsers from high-risk directories such as the User Downloads, Temp, or TMP folders. This behavior is indicative of a user downloading and executing malicious files or scripts directly from a web browser.
Detects coordinated security defense evasion activities by the Lambsys cryptominer campaign. The rule triggers when a shell process (bash, sh, or dash) is used to stop or disable security services (auditd, ClamAV, osquery, Falco, CrowdStrike Falcon), forcibly terminate their processes using pkill or kill -9, and delete or shred critical system security and audit logs (auth.log, syslog, audit).
Detects unauthorized attempts to terminate, stop, or access Endpoint Detection and Response (EDR) or Antivirus agent processes. This is identified by monitoring command-line utilities like taskkill, net, and sc targeting known security service names, as well as detecting suspicious cross-process access (e.g., OpenProcess) by unauthorized processes targeting security agent PIDs.
Detects the execution of consent.exe from a temporary directory path, which is often used in UAC bypass attacks to masquerade as the legitimate Windows UAC prompt process.
This rule detects the execution of common network share enumeration tools or scripts, specifically looking for the execution of netscan.exe (or similar) or PowerShell commands utilizing common share finding utilities like Invoke-ShareFinder, CheckShareAccess, or commands exporting share information to files.
Detects attempts to dump the memory of the Local Security Authority Subsystem Service (LSASS) process using the built-in Windows comsvcs.dll via rundll32.exe or tasklist commands, a common technique used for credential harvesting.
This rule monitors for suspicious activities related to System Informer (formerly Process Hacker) and its associated service (phsvc.exe). It detects unauthorized or unusual execution patterns, such as unsigned client binaries, shell spawning, or the use of specific proof-of-concept (PoC) command-line arguments that indicate attempts to abuse the service's privileged capabilities for process management or evasion.
This rule monitors for the creation of the 'adprinterpipe' named pipe by the AnyDesk remote support application. This behavior can be indicative of remote session activity or misuse of the AnyDesk software, often used as a vector for remote command and control.
Detects instances where the 'splunkd' process acts as a parent to common command-line interpreters (e.g., bash, powershell, python) or network utilities (e.g., curl, wget, netcat, nmap). This behavior is highly suspicious as the Splunk daemon should not typically invoke shells or network tools, and may indicate exploitation of the Splunk environment, lateral movement, or unauthorized task execution.
Detects the execution of known Impacket framework scripts such as psexec.py, wmiexec.py, and secretsdump.py, or command lines containing common indicators associated with these tools. The rule monitors process start events and filters for indicators of lateral movement and credential harvesting including administrative share access and lsass or ntds.dit interaction.
This rule detects the execution of the BloodHound or SharpHound Active Directory enumeration tools by monitoring for specific process names, command-line arguments associated with the tool's common flags (e.g., --CollectionMethod, --ZipFileName), and file paths containing these tool names.
Page 43 of 100