Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
2,918 detections
Filters
Last updated
All Time
Detection languages
1,568
780
216
110
94
Contributors
703
507
419
236
211
Categories
20,456
11,839
5,876
5,155
4,865
2,918
Platforms
2,584
507
385
83
17
Products / Services
1,265
605
83
82
72
MITRE Techniques
841
797
582
344
307
CVEs
24
8
8
5
5
Rust-based ransomware family targeting enterprise environments
Credential and browser data stealer distributed via OXLOADER campaigns
This rule detects the creation of NTFS reparse points or junctions within temporary directory paths, often used by adversaries to bypass directory access controls or redirect file system operations. The rule identifies file creation activities occurring under paths matching a specific temporary folder pattern (RP_ followed by a hex string) and excludes legitimate system operations like wermgr.exe executions.
Detects instances where an unusual process (not a standard image viewer or web browser) reads a .png file and subsequently triggers a new process within a 5-minute window. This behavior is indicative of potential steganographic exploitation or hiding malicious code within image files, where a hidden payload is read and then executed.
Detects high-volume file modifications or renames performed by a single process over a short window, affecting many unique file paths. This behavioral pattern is highly indicative of ransomware activity attempting to encrypt data for impact.
Detects suspicious access to wermgr.exe involving Alternate Data Streams (ADS) using the WDFOO tag, or access via Volume Shadow Copy (VSS) paths, often indicative of exploitation attempts related to CVE-2026-50656 where an adversary uses oplocks for race conditions against Windows Defender.
Detects DLL sideloading activity linked to Obsidian Sandstorm campaigns. It identifies legitimate, signed processes loading unsigned DLLs from non-standard, user-writable directories (such as Temp, Downloads, or Desktop) or the same directory as the executing process, specifically monitoring for indicators associated with malware families like ThrottleDrift and SilverGorilla.
Detects potential malicious activity including unsigned processes performing cross-process injection into common system processes, suspicious sideloading of 'vulkan-1.dll' from non-standard locations, and execution of unsigned binaries from user-writable directories like Temp, AppData, or ProgramData.
Detects the execution of QEMU binaries or the utilization of .qcow2 disk files. The rule flags these activities as higher risk when they occur within common user-writable or temporary directories, which is a common indicator of unauthorized virtualization usage, staging for side-loading, or attempts to hide malicious artifacts within virtual disks.
This rule detects the execution of suspicious file types (exe, dll, bat, cmd, vbs, js, ps1) originating from common extraction or user-writable locations like Downloads, Temp, or Roaming AppData directories. The rule specifically flags processes spawned by common archive utilities (winrar.exe, 7zFM.exe, 7zG.exe) or Windows Explorer, with an additional risk assessment if the command line arguments suggest recruitment or financial lure themes.
Detects the deployment of the IronWorm eBPF kernel rootkit by monitoring for unauthorized bpf() syscalls, specifically when invoked by suspicious parent processes such as npm or shells. The rule tracks the loading of eBPF programs, the usage of tools like bpftool, tc, and ip, and the presence of specific file artifacts and indicators associated with rootkit behavior like hiding PIDs or network sockets.
Commodity .NET keylogger and remote access trojan
Commodity .NET keylogger and remote access trojan
Detects node.exe copying browser history files to temporary directories, associated with the protocal.cjs backdoor.
Detects BQTLock ransomware activity by monitoring for mass file encryption events (file extensions .bqtlock or .baqiyatlock) and the creation of associated ransom note files (README.bqtlock or HOW_TO_DECRYPT.txt) using Sysmon and Windows Security Event logs.
This rule monitors for inbound email messages containing SVG file attachments. SVG files can contain embedded scripts that may be leveraged for malicious purposes, such as SVG smuggling to deliver secondary payloads or perform credential harvesting.
Detects LCRYX ransomware activity orchestrated by VBScript using wscript.exe or cscript.exe. The rule monitors for the mass encryption of files identified by the .lcryx extension and the creation of PLEASEREADME.txt ransom notes, typical behaviors of this ransomware variant.
Detects instances where a Node.js process accesses, modifies, or creates files within web browser extension directories. This behavior is indicative of unauthorized access to sensitive browser data, such as extension configurations, authentication tokens, or stored secrets.
Detects Node.js processes accessing common shell history files or PowerShell history logs. This behavior is indicative of infostealer malware, such as those targeting developers, attempting to extract credentials or command history from the local filesystem.
Detects instances where a node.exe process accesses files located within directories associated with popular browser-based cryptocurrency wallets. This pattern is commonly observed in infostealer malware campaigns that target wallet seeds, keys, and browser credentials stored in extension local storage or browser profile paths.
This rule detects the presence of known ShadowAgent malware files on devices by matching their SHA256 hashes. It queries 'DeviceFileEvents' to identify any files with SHA256 hashes that are part of a predefined list associated with ShadowAgent.
Page 80 of 139