Detections
Explore public detection logic contributed by the community across SIEM and rule languages.
2,285 detections
Filters
Last updated
All Time
Detection languages
1,276
250
199
141
138
Contributors
660
539
375
96
95
Categories
20,440
11,814
5,871
5,145
4,864
2,285
Platforms
1,502
922
374
70
51
Products / Services
740
407
225
164
140
MITRE Techniques
847
682
602
428
302
CVEs
12
10
9
9
8
IDS Classtypes
24
4
3
1
1
IDS Protocols
20
6
6
1
Detects instances where the Windows command shell (cmd.exe) creates, modifies, or renames specific suspicious files ('My_Resume.pdf', 'Documents_Details.pdf') within the 'ProgramData' directory, often associated with execution of batch files or file copy operations that may indicate staging of malicious payloads.
Detects the creation of specific file paths and files associated with the PSNATCH file stealer tool, specifically monitoring for the presence of SmartUploader application directories and its associated upload index files. This behavior is indicative of an adversary staging collected data on a local system for subsequent exfiltration.
Detects suspicious file create or write operations within the domain SYSVOL Policies directory. This pattern is commonly associated with attackers attempting to deploy malicious payloads, such as ransom notes or configuration changes, via Group Policy Objects (GPO). The rule monitors Windows Event ID 4663 to identify unauthorized modification attempts by non-system accounts.
Detects browser extension manifest.json files requesting declarativeNetRequest and content_scripts/host_permissions covering AI assistant vendor domains (BragJack attack class)
Detects unauthorized access, modification, or creation of the FileZilla 'sitemanager.xml' configuration file by a process other than the legitimate 'filezilla.exe'. This is a common indicator of an adversary attempting to steal stored FTP credentials or modify connection configurations.
This rule detects suspicious directory creation or file attribute modifications within the 'naverwhale' roaming AppData directory. Adversaries may use this path to stage malicious payloads, persistence mechanisms, or to impersonate legitimate browser files.
Detects high-volume filesystem activity (exceeding 300 operations in 5 minutes) initiated by 'claude-code' or 'claude' processes. This behavior may indicate an autonomous, patched, or jailbroken AI coding assistant performing mass file operations or reconnaissance without user confirmation.
Detects unauthorized processes (non-browser applications) creating, modifying, or renaming sensitive browser data files such as Login Data, Cookies, or local state files within standard browser profile directories. This activity is indicative of credential harvesting or session hijacking attempts by malicious software.
This rule detects forced pushes to the main branch of a GitHub repository where a specific file named 'indexe.cjs' is added or a specific commit ID (d1d55e13) is pushed. This behavior is indicative of a supply chain compromise where an attacker rewrites git history to inject malicious loaders or backdoors into the source code.
Monitors GitHub Audit Logs for git pushes or workflow changes occurring after the September 16, 2026, reactivation window that reference the actions-cool/issues-helper or actions-cool/maintain-one-comment repositories. The rule excludes routine automated maintenance activity from trusted bots and common maintenance commit messages, aiming to identify unauthorized attempts to utilize or modify potentially compromised GitHub actions.
Monitors GitHub Audit Logs for git pushes or workflow changes occurring after the September 16, 2026, reactivation window that reference the actions-cool/issues-helper or actions-cool/maintain-one-comment repositories. The rule excludes routine automated maintenance activity from trusted bots and common maintenance commit messages, aiming to identify unauthorized attempts to utilize or modify potentially compromised GitHub actions.
Monitors GitHub Audit Logs for git pushes or workflow changes occurring after the September 16, 2026, reactivation window that reference the actions-cool/issues-helper or actions-cool/maintain-one-comment repositories. The rule excludes routine automated maintenance activity from trusted bots and common maintenance commit messages, aiming to identify unauthorized attempts to utilize or modify potentially compromised GitHub actions.
Monitors GitHub Audit Logs for git pushes or workflow changes occurring after the September 16, 2026, reactivation window that reference the actions-cool/issues-helper or actions-cool/maintain-one-comment repositories. The rule excludes routine automated maintenance activity from trusted bots and common maintenance commit messages, aiming to identify unauthorized attempts to utilize or modify potentially compromised GitHub actions.
Monitors GitHub Audit Logs for git pushes or workflow changes occurring after the September 16, 2026, reactivation window that reference the actions-cool/issues-helper or actions-cool/maintain-one-comment repositories. The rule excludes routine automated maintenance activity from trusted bots and common maintenance commit messages, aiming to identify unauthorized attempts to utilize or modify potentially compromised GitHub actions.
This rule detects GitHub Actions workflows that explicitly reference specific 'actions-cool' GitHub actions using a known-bad mutable version tag ('@v2.2.1'). This tag corresponds to malicious code introduced into these repositories, allowing for potential CI/CD pipeline poisoning and supply chain compromise.
This rule detects GitHub Actions workflows that explicitly reference specific 'actions-cool' GitHub actions using a known-bad mutable version tag ('@v2.2.1'). This tag corresponds to malicious code introduced into these repositories, allowing for potential CI/CD pipeline poisoning and supply chain compromise.
This rule detects GitHub Actions workflows that explicitly reference specific 'actions-cool' GitHub actions using a known-bad mutable version tag ('@v2.2.1'). This tag corresponds to malicious code introduced into these repositories, allowing for potential CI/CD pipeline poisoning and supply chain compromise.
This rule detects GitHub Actions workflows that explicitly reference specific 'actions-cool' GitHub actions using a known-bad mutable version tag ('@v2.2.1'). This tag corresponds to malicious code introduced into these repositories, allowing for potential CI/CD pipeline poisoning and supply chain compromise.
This rule detects a correlation between the creation or modification of a specific file name ('nloemfbihmhm') and the subsequent execution of processes from the 'Temp' directory involving related filenames ('kojuyn.ini', 'ogftogcyiblzjccmcbnw.exe', or 'nloemfbihmhm') within a 5-minute window. This behavior is indicative of a multi-stage execution chain, often used by malware to drop and execute secondary payloads.
This rule detects the installation or presence of ten identified malicious npm packages associated with the indexed-btree/sorted-btree typosquatting campaign. It monitors command-line activity for 'npm install' commands, package name resolution, and entries within 'package.json' files.
This rule detects potential credential theft by monitoring for file access (creation, modification, or renaming) to common web browser sensitive files (Login Data or Cookies) followed by an outbound network connection from the same process within a 10-minute window. This behavior often indicates an adversary attempting to exfiltrate browser-stored credentials or session cookies.
Page 19 of 109