Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
1,050 detections
Filters
Last updated
All Time
Detection languages
448
250
202
51
27
Contributors
410
155
118
94
48
Categories
628
580
246
179
128
Platforms
988
67
34
20
13
Products / Services
192
142
69
46
28
MITRE Techniques
18,123
15,639
12,581
8,394
6,215
1,050
CVEs
1
IDS Classtypes
7
IDS Protocols
3
2
1
Detects the execution of the 'encrypter-linux-x86' binary on Linux systems, specifically looking for command-line arguments indicative of file encryption activity (-e or --esxi). This binary name is frequently associated with ransomware targeting virtualized environments.
Detects execution/staging of the GodDamn ransomware encrypter binary encrypter-windows-gui-x86.exe from user profile Downloads or Music folders, or matching the known encrypter hash
This YARA rule detects files associated with the Agenda (Qilin) ransomware by searching for specific string patterns within the binary, such as hardcoded ransom note contents, Rust language artifacts, and an onion domain used for command-and-control or negotiation. It also validates the file as a Windows executable.
This rule detects potential ransomware activity by monitoring for high-frequency file rename events (more than 50 in a single dataset aggregation) or file renames resulting in the specific extension '.God8Damn'. Such patterns are highly characteristic of ransomware encrypting local or network files.
Detects a process creating files named 'README.TXT' or 'README.txt' across three or more distinct directories. This behavior is a common indicator of ransomware activity, where an adversary drops ransom notes in multiple folders to maximize visibility after encrypting files.
Detects the presence of known ransomware extortion note file names on endpoints or communication attempts with associated extortion contact email addresses in email logs.
This rule detects activities characteristic of the 'Gentleman' ransomware, including the creation of a specific ransom note file ('README-GENTLEMAN.txt'), attempts to tamper with Windows Defender security preferences, and the destruction of system recovery artifacts such as Volume Shadow Copies and various system logs/prefetch files.
This rule detects potential ransomware activity by monitoring for high-frequency file renaming operations combined with the presence of specific file extensions often associated with encryption and the concurrent creation of ransom note files (e.g., 'README.TXT').
Detects the execution of a potential file encryption utility that uses command-line flags ('enc'/'dec', '-k'/'-i'/'--keyfile') in conjunction with a 'key.txt' file. This pattern is characteristic of custom encryption tools used by threat actors to encrypt files on a system.
Detects the execution of a potential file encryption utility that uses command-line flags ('enc'/'dec', '-k'/'-i'/'--keyfile') in conjunction with a 'key.txt' file. This pattern is characteristic of custom encryption tools used by threat actors to encrypt files on a system.
Detects file creation events with the .candy extension, consistent with the GigaWiper/Crucio-derived BigBang extortion module (BigBangExtortMain, bigBangSingleFileExtortion, bigBangHybridEncryption) which AES-CBC encrypts files using randomly generated, unsaved key/IV pairs across enumerated Windows logical drives before deleting the original file with os.Remove.
Detects the execution of a potential file encryption utility that uses command-line flags ('enc'/'dec', '-k'/'-i'/'--keyfile') in conjunction with a 'key.txt' file. This pattern is characteristic of custom encryption tools used by threat actors to encrypt files on a system.
INFO 3AM ransom
YARA
This YARA rule detects files containing specific strings and patterns associated with the 3AM ransomware, such as the group's name, their onion URL format, and common ransomware-related terminology. It is designed to identify ransom notes left behind on compromised systems.
Detects dropped builder/README/config files from underground Ransomware-as-a-Service kits bundling FUD AES-256 crypters, private stubs, decrypters, and key generators for Windows 10/11 ransomware payloads
This rule detects the presence of the GodDamn ransomware encryptor on a host by identifying the specific binary filename (encrypter-windows-gui-x86.exe), its known SHA256 hash, or the presence of the .God8Damn file extension commonly associated with files encrypted by this malware.
This rule detects potential ransomware activity or bulk file manipulation by monitoring for a high volume of file write, rename, or creation events performed by a single process within a one-minute window. It calculates the frequency and variety of unique files touched to identify potentially malicious automated encryption or data destruction behavior.
Detects mass file renaming activities involving the '.Liushen' extension, commonly associated with the LIUSHEN ransomware behavior where files are appended with this extension after being encrypted.
Detects self-narrating LLM-generated ransomware payload artifacts referencing ransom infrastructure and encryption routines (JadePuffer)
Detects high-volume file creation events (more than 50 within 5 minutes) on an endpoint using specific file extensions associated with known ransomware families such as INC Ransom (.inc) and Lynx (.lynx).
This rule monitors process command lines and file operations for specific strings associated with ransomware, including known ransom note naming conventions ('readme_ransom'), a specific Bitcoin wallet address, a contact email, and SQL commands commonly used to drop database tables for ransom purposes.
This rule monitors for the creation of files containing the string 'readme_ransom' or the execution of processes that reference 'readme_ransom', specific known ransomware wallet addresses, or associated contact email addresses, which are indicative of post-encryption ransomware activity.
Page 8 of 50