Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
2,294 detections
Filters
Last updated
All Time
Detection languages
1,284
250
199
142
138
Contributors
660
544
375
96
95
Categories
20,456
11,839
5,876
5,155
4,865
2,294
Platforms
1,505
929
381
70
51
Products / Services
743
407
225
164
140
MITRE Techniques
856
683
604
437
302
CVEs
12
10
9
9
8
IDS Classtypes
24
4
3
1
1
IDS Protocols
20
6
6
1
Detects the creation, modification, or renaming of files with the '.prinzeugen' extension, which is commonly associated with ransomware activity. The rule aggregates these events by device and time, alerting if 10 or more such files are observed within an hour, indicating potential widespread encryption.
This rule detects potential ransomware activity by identifying rapid bulk file modifications or renames that result in files adopting extensions commonly associated with ransomware encryption. It looks for a high volume of file events (creation, modification, rename) within a short timeframe (1 hour) where the new file extensions match a predefined list of ransomware-specific extensions.
This rule detects the execution of a specific command-line sequence involving 'cmd.exe' that is characteristic of the ClickFix attack. The sequence includes moving an 'update.zip' file from the user's downloads, extracting a 'u.zip' file in the temporary directory, and then executing 'update.bat'. This pattern is often associated with malicious copy-paste techniques.
Detects when a browser desktop shortcut (.lnk file) is modified by a setup or update executable, which could indicate a Potentially Unwanted Program (PUP) injecting malicious arguments or redirecting the browser to an attacker-controlled gateway upon launch.
This rule detects the execution of SharkLoader components, specifically identifying unauthorized SystemSettings.exe processes attempting to load malicious DLLs (e.g., SystemSettings.dll, DscCoreR.mui, SyncRes.dat) from locations outside of the legitimate C:\Windows\ImmersiveControlPanel\ directory. It also tracks the creation or modification of these payload files in common persistence directories like AppData or ProgramData.
Detects file creation and execution patterns associated with SharkLoader malware. The rule monitors for the staging of malicious DLLs, encrypted beacon payloads, and API hooks in specific AppData subdirectories ('xwreg' and 'xgdf'), as well as the execution of 'SystemSettings.exe' from non-standard locations, which mimics legitimate Windows system processes to achieve persistence and evasion.
Detects unauthorized privilege escalation attempts within the MyBB Admin Control Panel (ACP) by monitoring limited-privilege accounts accessing restricted modules (e.g., plugins, templates, user groups). It correlates these web requests with file system changes in the plugin directory by the web server process and monitors application logs for suspicious administrative activity.
Detects Pay2Key ransomware activity involving the extraction of suspicious DLLs into the Avast installation directory and the subsequent loading of these unsigned/unauthorized DLLs by legitimate Avast processes. This rule covers the file creation of known malicious DLL names, the use of 7za.exe for extraction into the directory, and the process module load events for unsigned DLLs within the Avast scope.
Detects activity associated with VILE ransomware where it modifies files within the Chrome extension locale directory (specifically for the extension nmmhkkegccagdldgiimedpiccmgmieda) by appending the .vile extension, indicating potential file encryption or tampering for impact.
Detects evidence of TrymeLocker or similar ransomware behavior by identifying the simultaneous use of Windows utilities (icacls, cacls, takeown, attrib) to modify permissions on critical system directories or obscure executables, correlated with the deletion of volume shadow copies or disabling of system recovery features.
Detects suspicious unsigned processes that load user32.dll (often for API hooking) while concurrently writing data to files in temporary or application data directories (consistent with keylogging dump patterns). This rule targets non-system binaries originating from user-writable paths that exhibit combined module loading and file output behaviors typical of keylogger malware like TrymeLocker.
Detects behavior indicative of Pay2Key ransomware, specifically the renaming of files with a '.3396bw_p2k' extension, the creation of 'HowToRestoreFiles.txt' ransom notes by Everything.exe, or file rename activity initiated by Everything.exe from a 7Zip SFX temporary directory.
Detects attempts to perform a container escape via the docker cp command by abusing path traversal vulnerabilities or suspicious file write operations performed by the Docker daemon to the host filesystem outside of standard container paths, often associated with symbolic link extraction exploits.
Detects when a non-Discord process creates or modifies both 'index.js' and 'package.json' within a Discord desktop core module directory. This file pair is critical for Electron module loading and is often targeted by malware like VVS Stealer to establish persistent session interception.
Detects LCRYX ransomware activity where PowerShell is used to write data from a specified file (gcrybground.png) directly to the physical disk (PhysicalDrive), intending to overwrite the Master Boot Record (MBR) and render the system unbootable. It also monitors for subsequent attempts to disable Windows system recovery via bcdedit.
Detects LCRYX ransomware behavior characterized by the disabling of Windows Defender real-time monitoring followed by an attempt to overwrite the Master Boot Record (MBR) on PhysicalDrive0 using PowerShell. The rule monitors for PowerShell processes spawned by wscript.exe or cscript.exe that reference disk drive objects or specific LCRYX image files, and correlates them with Defender tampering activities.
Detects the creation or modification of a web shell named 'help.php' within REDCap application directories, a known persistence mechanism used by UNC6508. This rule specifically looks for file creation, modification, or renaming events for 'help.php' in paths containing 'redcap'.
Detects GitHub Actions workflow files that include 'id-token: write' permissions in conjunction with 'npm publish' or 'yarn publish' commands. This pattern is indicative of the Miasma worm (also known as the wshu.net campaign) which abuses OIDC trusted publishing to facilitate unauthorized npm package propagation. The rule also identifies workflows that attempt to fallback on legacy NPM_TOKEN secrets.
Detects command-line activity indicative of timestomping, specifically when 'cmd.exe' is used with file copy/move commands ('copy', 'xcopy', 'robocopy', 'move') and the target path is not within 'Program Files' or 'Windows' directories. This behavior is often associated with ransomware like Prinz Eugen attempting to hide its activities.
Detects file encryption activity associated with Prinz Eugen ransomware by monitoring for newly created files with the '.prinzeugen' extension and a significant total file size increase within a short period.
This rule detects the creation or modification of at least 10 files within an hour that have the '.prinzeugen' extension, which is indicative of the Prinz Eugen ransomware encrypting files using ChaCha20.
Page 86 of 110