DETECT hunt Library

Sources and licenses

The library indexes 62,921 detections from 56 repositories. Each detection stays under its own license and links to the file it came from. The site keeps a copy of the rule text where the license allows, so the tools can read it, and the linked file stays the reference. One source states no license, and its note below says why the library carries it.

Framework v0.136.0, updated November 17, 2026.

62,921detections
30,957tagged with an ATT&CK technique
12,625translated into 10 or more languages
14,850with a robustness draft
On this page

Sources

SourceLicenseDetectionsWhat this site storesCommit read
SigmaHQDetection Rule License 1.13,766Query and metadataca24243a6e
Splunk Security ContentApache License 2.02,090Query and metadata502a59a8bb
Elastic detection rulesElastic License 2.02,216Query and metadata0aacc5e192
Elastic hunting queriesElastic License 2.0143Query and metadata0aacc5e192
Elastic protectionsElastic License 2.01,332Query and metadataccefbba2b6
Elastic protections YARAElastic License 2.03,069Query and metadataccefbba2b6
Microsoft Defender huntingMIT License266Query and metadataefa17a600b
Microsoft SentinelMIT License4,984Query and metadata4db27c9820
Panther analysisApache License 2.0866Query and metadatad155b5922e
Google SecOps (Chronicle)Apache License 2.0379Query and metadata234e9223c3
Sublime SecurityMIT License1,291Query and metadatafd25119a07
Falco rulesApache License 2.095Query and metadata21ef6d5f5f
MITRE CARApache License 2.099Query and metadata1b922fe152
LOLRMMApache License 2.0716Query and metadata33941c32b5
Okta customer detectionsApache License 2.034Query and metadataf7c7bceecc
Tracee detectorsApache License 2.033Query and metadata2f9dc40c20
osquery packsApache License 2.0196Query and metadataf0af4d8426
signature-base YARADetection Rule License 1.15,852Query and metadata94a1c48d7a
Emerging Threats OpenBSD license (ET Open)10,313Query and metadatasha256:f14
Hayabusa rulesDetection Rule License 1.1191Query and metadata3d81fa7977
ESET malware IOCs (YARA)BSD 2-Clause License117Query and metadata17baf44964
ReversingLabs YARAMIT License309Query and metadatae0a0be54aa
Mandiant red team tool countermeasuresBSD 2-Clause License172Query and metadata3561b71724
Volexity threat intel (YARA)BSD 2-Clause License149Query and metadatad8bb51c3e4
Bert-JanP hunting queriesBSD 3-Clause License302Query and metadata1c92e563cc
reprise99 Sentinel queriesMIT License462Query and metadata660895f644
FalconForce FalconFridayBSD 3-Clause License48Query and metadatac662a6a0dc
CrowdStrike LogScale communityThe Unlicense (public domain)136Query and metadata0152b8a763
Falco plugin rulesApache License 2.0134Query and metadata33cbeb9048
mdecrevoisier Sigma rulesCC0 1.0 (public domain)337Query and metadatad61408af87
cyb3rmik3 KQL hunting queriesMIT License87Query and metadata1fb575b0bb
benscha KQL advanced huntingNo license stated51Query and metadata447e70fefe
OTRF ThreatHunter-PlaybookMIT License26Query and metadatad310f3882e
AI DFIR toolkitApache License 2.0136Query and metadata1a5963d922
Anvilogic Forge armoryGNU General Public License 3.01,898Query and metadata6677454cad
vector-sec Sublime rulesGNU General Public License 3.07Query and metadata4a01e8c3b0
Joe Security Sigma rulesGNU General Public License 3.0112Query and metadatacb91be06c8
Google Cloud security analyticsApache License 2.0102Query and metadata2dd8565557
CTID cloud analyticsApache License 2.016Query and metadata6106cc1db4
Exabeam content libraryApache License 2.01,424Metadata and link only2896c831c3
Auth0 customer detectionsApache License 2.026Query and metadata5b3940da41
AIPT detection packDetection Rule License 1.1155Query and metadata9e4653db4d
Malicious infrastructure hunting queriesMIT License864Query and metadata1fa5ad6214
Awesome Censys queriesCC0 1.0 (public domain)84Query and metadata56ae5ce0bc
Awesome Shodan queriesCC0 1.0 (public domain)54Query and metadatab3439d187b
ProjectDiscovery search queriesMIT License7,777Query and metadatacc66f42ebd
Snort 3 community rulesGNU General Public License 2.04,024Query and metadatasha256:969
Wazuh rulesetGNU General Public License 2.03,840Query and metadatabed556db3f
Agent Threat RulesMIT License844Query and metadata0793de94ca
ep3p Sentinel KQLMIT License354Query and metadata8dc8925fb7
Alex Verboon hunting queriesBSD 3-Clause License198Query and metadatab6a846e433
JPCERT/CC YARABSD 3-Clause License239Query and metadata7837438e7b
bartblaze YARAMIT License142Query and metadata5cc871d823
Micah Babinski Sigma rulesGNU General Public License 3.0223Query and metadata9dea7a5c15
Jamf Protect custom analyticsMIT License80Query and metadata34e1c6c6e1
GitLab threat detections (TLDR)MIT License61Query and metadatafa9039504f

Storage and license notes

Elastic detection rules
Shown under the Elastic License 2.0 with the license and notices kept.
Elastic hunting queries
Hunting queries from the hunting folder of Elastic's detection-rules repository, shown under the Elastic License 2.0 with the license and notices kept. They find activity for an analyst to review and are not tuned to alert. Where a hunt has several queries, all are shown in order.
Elastic protections
Endpoint behavior rules, shown under the Elastic License 2.0 with the license and notices kept.
Elastic protections YARA
YARA rules Elastic ships in its endpoint to find malware families in files and memory, shown under the Elastic License 2.0 with the license and notices kept. Each rule names its operating system, which sets the platform, and the score shown is the rule's own severity field, 0 to 100.
Microsoft Defender hunting
Hunting queries that find suspicious activity for an analyst to read. They are not tuned to alert.
Sublime Security
Sublime maps its email rules to its own attack types and has no ATT&CK mapping, so these entries carry no technique or tactic.
Tracee detectors
Linux runtime detectors for eBPF events, written in Go. Copyright 2019 Aqua Security Software Ltd., Apache License 2.0. Each entry shows the detector's event requirements and event handler.
osquery packs
Endpoint SQL queries from the security packs (incident response, macOS and Windows attack artifacts, rootkit checks, unwanted browser extensions). The osquery project offers Apache 2.0 or GPL 2.0 at the user's choice, and these are shown under Apache 2.0. The packs carry no ATT&CK mapping, so these entries have no technique or tactic. The compliance, hardware, and vulnerability packs are left out because they inventory settings and do not detect activity.
signature-base YARA
YARA rules by Florian Roth and contributors, which match files and process memory. The license asks that each rule keep its author and a link to it, and both are shown. Rules whose own metadata names another license are left out, as are private helper rules and the repository's IOC lists. The score is the author's confidence from 0 to 100.
Emerging Threats Open
Suricata network rules. Only enabled rules that carry an ATT&CK technique are included. Left out: rules that match only a domain name (DNS query, TLS server name, or HTTP host), which are indicators like the IP reputation lists, also left out; the policy, info, hunting, and retired categories; and anything outside SIDs 2000000 to 2799999, which the license shipped with the ruleset gives to Emerging Threats under the BSD license. Rules 2100000 to 2103999, forks of the original Snort GPL rules, are left out too. Severity follows the signature_severity field: Critical is critical, Major is high, Minor is low, and Informational is informational.
Hayabusa rules
Yamato Security's own Windows event log rules, written in Sigma format for the Hayabusa timeline tool. The repository also carries converted copies of SigmaHQ rules, which are left out because SigmaHQ is read directly.
ESET malware IOCs (YARA)
YARA rules ESET published with its malware research. They match malware families by strings and structure. The two-clause BSD license asks that the copyright notice and license travel with the rules, so both are published beside them.
ReversingLabs YARA
YARA rules ReversingLabs published for malware families, ransomware, and exploits. The certificate folder, 931 rules that match the serial numbers of signing certificates, is left out as a list of indicators. The MIT license asks that its copyright and permission notice travel with the rules, so both are published beside them.
Mandiant red team tool countermeasures
YARA rules Mandiant released in December 2020 to detect the red team tools stolen from FireEye. The repository also carries Snort, ClamAV, and HXIOC versions, which are left out. The BSD license text is published beside the rules.
Volexity threat intel (YARA)
YARA rules Volexity published alongside its threat research, one folder per year. The BSD license text is published beside the rules.
Bert-JanP hunting queries
KQL hunting queries and detection rules for Defender XDR and Sentinel by Bert-Jan Pals. Where a page gives both a Defender XDR and a Sentinel version, both are shown. The learning, fun, and function folders are left out. The BSD license text is published beside the queries.
reprise99 Sentinel queries
KQL queries for Microsoft Sentinel by Matt Zorich, mostly for hunting and investigation across Entra ID, Azure, Office 365, and Defender. The MIT license notice is published beside them.
FalconForce FalconFriday
Detections FalconForce published in its FalconFriday series, each with an ATT&CK mapping, blind spots, and response steps. The BSD license text is published beside them.
CrowdStrike LogScale community
LogScale (CQL) queries from CrowdStrike's community content repository, released into the public domain. Only the Queries-Only folder is read; its ATT&CK folder names the technique of each query.
Falco plugin rules
Falco rules for the event sources Falco reads through plugins: AWS CloudTrail, GCP audit logs, Okta, GitHub, and Kubernetes audit. Rules shipped disabled are left out, as are example, test, and dummy rules, and the GKE plugin's copy of the Kubernetes audit rules.
mdecrevoisier Sigma rules
Sigma rules by Michel de Crevoisier for Windows, Active Directory, Azure, SQL Server, and BITS, released into the public domain. Most carry no Sigma id, so the library derives a stable one from the file path.
cyb3rmik3 KQL hunting queries
KQL hunting and detection queries for Defender XDR and Sentinel by Michail Michalos. The learning folder and the template are left out. The MIT license notice is published beside them.
benscha KQL advanced hunting
KQL hunts for Defender XDR and Sentinel by Benjamin Zulliger, from the repository's ThreatHunting folder, many of them for Kubernetes and containers. The repository states no license, so the queries remain the author's. Its README lists community platforms that index and feature them. The library does the same, crediting the author and linking each original file.
OTRF ThreatHunter-Playbook
Documented hunts from the Open Threat Research Forge, each with a hypothesis, an ATT&CK mapping, and analytics written as Spark SQL over a recorded dataset. Each hunt's analytics appear together in their original order. The MIT license notice is published beside them.
AI DFIR toolkit
Sigma, YARA, and Suricata rules for attacks on LLM applications, MCP servers, model supply chains, AI infrastructure, coding assistants, RAG pipelines, and AI agents, by Raymond DePalma. The rules map to MITRE ATLAS and the OWASP LLM Top 10 as often as to ATT&CK; those ids are kept in each description, and the ATT&CK ids in the technique field. The Sigma rules come from the nine category folders and the agent artifact catalog's detections folder. The project is unrelated to The DFIR Report, whose GPLv3 rules stay out. ATT&CK 20.0 adds Direct and Indirect Prompt Injection, T1699 and T1698. MITRE's data cites no ATLAS id for either, so the library leaves each rule's ATT&CK ids as its author published them.
Anvilogic Forge armory
The public slice of Anvilogic's detection armory, written as SPL for Splunk or as SQL for Snowflake. Anvilogic calls them threat identifiers, meant to be chained into a longer scenario in its platform. Each query calls macros such as get_endpoint_data in place of your own data, so replace them before running one. Shown under the GNU General Public License 3.0, with the license text published beside them. This site's CC BY-NC license does not cover them, and anyone may copy, change, and share them on the GPL's terms.
vector-sec Sublime rules
Email detections in Sublime's MQL from an independent author, apart from Sublime's own rules. Shown under the GNU General Public License 3.0, with the license text published beside them. This site's CC BY-NC license does not cover them, and anyone may copy, change, and share them on the GPL's terms.
Joe Security Sigma rules
Windows Sigma rules Joe Security wrote for hunting in its malware sandbox. Most name no ATT&CK technique; where a rule names one in its own mitreattack field, the library reads it from there. Seven files are not valid YAML and are left out. Shown under the GNU General Public License 3.0, with the license text published beside them. This site's CC BY-NC license does not cover them, and anyone may copy, change, and share them on the GPL's terms.
Google Cloud security analytics
Community use cases for Google Cloud and Workspace audit logs, each with up to three queries: BigQuery SQL, Log Analytics SQL, and YARA-L for Google SecOps. Each query is its own entry. Three use cases with no query in any of the three are left out.
CTID cloud analytics
Sigma analytics for Azure, Google Cloud, and Workspace from MITRE's Center for Threat-Informed Defense, published in 2022 with emulation plans for each. Several chain rules together in the correlation format Sigma used before its correlation specification, so a current pySigma reads the single rules and not the chains. One file, the GCP service account permissions rule, nests its detection inside its log source, so it is not a valid Sigma rule and is left out.
Exabeam content library
The rules of Exabeam's behavioral analytics, as its documentation lists them for each log source it parses: a rule id, what the rule flags, and its ATT&CK technique. The documentation carries no rule logic, so these entries have no query. Each entry counts the log sources and event types Exabeam lists for the rule, and links the page of the first log source.
AIPT detection pack
Detections by Xint for LLM-driven autonomous penetration testing tools: ARTEX and nine like it, CyberStrikeAI, HexStrike-AI, PentAGI, Strix, Shannon, MetasploitMCP, PentestGPT, Decepticon, and Villager. Sigma, Suricata, and YARA rules are read; the ModSecurity plugin and the correlation queries are left out. Every rule matches a tool's fingerprint, such as a user agent, URL path, port, TLS field, or process name, so a match names the tool but not whether its use was authorized. Rules whose name ends in _base are inputs to the pack's correlations and are not meant to alert alone. The Detection Rule License asks that each rule keep its author and a link to it, and both are shown.
Malicious infrastructure hunting queries
Shodan, Censys, and Netlas searches for attacker infrastructure, collected by frknaykc: C2 framework servers, RAT and stealer panels, phishing kits, open directories serving payloads, and hosts exposing a known CVE. They run in the search engine and find servers on the internet, so the baseline builder leaves them out. Each is a starting point for hunting and blocking, and a server that matches may be a researcher's or a red team's. The Turkish copy of the files and the ClickFix case study are left out. Where the collection lists several searches in one block, each is its own entry. The MIT license notice is published beside them.
Awesome Censys queries
Censys searches collected by Aidan Holland, for C2 frameworks and other attacker tooling as well as exposed industrial controls, cameras, and other devices. They run in Censys, so the baseline builder leaves them out. Released into the public domain.
Awesome Shodan queries
Shodan searches collected by Jake Jarvis for exposed industrial controls, network devices, remote desktops, databases, cameras, and other services that should not face the internet. They run in Shodan, so the baseline builder leaves them out. Released into the public domain.
ProjectDiscovery search queries
Shodan, FOFA, ZoomEye, and Censys searches that find a named product on the internet, collected by ProjectDiscovery from the metadata of its Nuclei templates: web applications, admin panels, network devices, and servers. A match says where a product is exposed, which is the first question when a vulnerability in it is announced. They run in the search engine, so the baseline builder leaves them out.
Snort 3 community rules
The free community ruleset for Snort 3, written by Cisco Talos and the contributors its AUTHORS file names, downloaded as a tarball from snort.org. Every enabled rule is included; most are malware command and control, web application attacks, and exploit attempts. A rule's severity follows the priority Snort's classification file gives its classtype. Each entry links the rule's page on snort.org. Shown under the GNU General Public License 2.0 that ships in the tarball, with the license text published beside them. This site's CC BY-NC license does not cover them, and anyone may copy, change, and share them on the GPL's terms.
Wazuh ruleset
The rules Wazuh ships with its manager, read from the ruleset folder of the 4.14.9 release. They match decoded log fields for Windows, Linux, firewalls, web servers, cloud audit logs, and the agent's own file integrity and rootkit checks. Rules at level 0, which exist to group or silence other rules, are left out. Severity follows the level: 1 to 4 is informational, 5 to 7 low, 8 to 11 medium, 12 to 14 high, and 15 critical. Shown under the GNU General Public License 2.0, with the license text published beside them. This site's CC BY-NC license does not cover them, and anyone may copy, change, and share them on the GPL's terms.
Agent Threat Rules
Rules in the ATR format for attacks on AI agents: prompt injection, tool and skill poisoning, context exfiltration, and agents acting past their mandate, matched against prompts, tool calls, MCP messages, and agent output. Only the rules folder is read; the repository's generated proposals are left out. The stored copy of each rule leaves out its test cases, evasion tests, and compliance mappings, which the linked file keeps. The rules map to MITRE ATLAS and the OWASP lists for LLMs and agents as often as to ATT&CK. Those ids stay in each description, and the ATT&CK ids go in the technique field. The MIT license notice is published beside them.
ep3p Sentinel KQL
KQL queries for Microsoft Sentinel from the Queries folder, one file per query, organized by the Microsoft product whose logs they read. Many take their allowlists from Sentinel watchlists, which the repository's Watchlists folder defines. The Learn folder is left out. The MIT license notice is published beside them.
Alex Verboon hunting queries
KQL hunting queries and detection rules for Defender XDR and Sentinel by Alex Verboon, one page per query, in folders named for the Microsoft product they read. Where a page gives both a Defender XDR and a Sentinel version, both are shown. The BSD license text is published beside them.
JPCERT/CC YARA
YARA rules JPCERT/CC published for the malware of the groups it tracks, one folder per group. The BSD license text is published beside them.
bartblaze YARA
YARA rules by Bart Parys for malware families, webshells, and attacker tooling, each with a description and a reference. The MIT license notice is published beside them.
Micah Babinski Sigma rules
Windows Sigma rules Micah Babinski wrote from public incident reports, one folder per campaign or report, from Gootloader and QakBot to the Red Canary threat detection report. Shown under the GNU General Public License 3.0, with the license text published beside them. This site's CC BY-NC license does not cover them, and anyone may copy, change, and share them on the GPL's terms.
Jamf Protect custom analytics
Custom analytics for Jamf Protect from Jamf's open source repository: a predicate over a macOS endpoint event, the event type it needs, and the severity Jamf recommends. Tactics come from each analytic's ATT&CK categories; most name Visibility or living off the land instead of a tactic, so few carry one. The agentic folder, detections for AI agent tooling on a Mac, is included. Jamf says the repository is provided as is and is not supported by Jamf Support. The MIT license notice is published beside them.
GitLab threat detections (TLDR)
Sigma rules for a self-managed GitLab instance's own logs, from GitLab's security team, each inside a page that explains the threat, the log fields, sample events, and the response. Threat detections cover administrator and token abuse; vulnerability detections match the probing of named CVEs. The rules name a team mailbox as their author, and the library shows the team's name in its place. The MIT license notice is published beside them.
Elastic License 2.0
A copy of the license text accompanies the Elastic rules. It allows copying and making the rules available with the license and notices kept, and it bars offering the software itself as a hosted service.
ET Open
The license text and copyright notice shipped with the ruleset accompany the Suricata rules. That license puts SIDs 2000000 to 2799999 under the BSD license, and the catalog publishes only that range. The GPLv2 and ETPRO ranges it names are left out, as are rules 2100000 to 2103999, forks of the original Snort GPL rules.
GPL sources
Anvilogic's armory, vector-sec's Sublime rules, and Joe Security's Sigma rules are under the GNU GPL 3.0. Their rules stay under it, with the license text published beside them, and this site's CC BY-NC license does not cover them. The DFIR Report's own Sigma repository is empty now, because its public rules go to SigmaHQ, and the library carries the 17 SigmaHQ rules that credit it.
No license file
benscha's KQL advanced hunting has no license file, and the library carries it because its README welcomes indexing by community platforms.
Skipped on purpose
PyPanther repeats rules already read from Panther analysis, and hayabusa-rules' converted SigmaHQ copies repeat SigmaHQ.
Attribution
Sigma rules keep their author line and rule id. Splunk, Panther, and Microsoft rules keep their license notice in the source repository each entry links to.
Test corpus
OTRF's Security-Datasets (MIT License) are not a source of detections. The library runs its Windows Sigma rules against these recorded attacks and records which fired; the outside checks page explains the test. No event from them is published.

Catalog build

A script reads each repository and writes one catalog: name, description, ATT&CK techniques and tactics, platform, query language, severity, and the source link. Tactics come from the source when it names them, and otherwise from the tactics of each technique in ATT&CK 20.1. A technique ATT&CK has revoked since the rule was written is shown as the technique that replaced it. ATT&CK has also split Defense Evasion into Stealth and Defense Impairment. A rule tagged Defense Evasion goes under whichever of the two its techniques belong to, and under Stealth when they point to neither. Platform is read from each source's log source or tags, so a few detections land under Other. A weekly job refreshes it; this build read it on 2026-10-05.

Drafts

The translator column counts detections the query translator can read. The score draft is a robustness level of 1 to 3, scored the way Summiting the Pyramid scores an analytic: each observable a rule matches gets a level, from the field and what the value names, and the rule's condition combines them. Observables joined by AND take the lowest level, and observables joined by OR take the highest. Levels 4 and 5 need a person who knows the technique, so the draft never claims them. Checked against CTID's hand scores. Build effort is set to 1, the anchor for adapting a public detection. Threat relevance, impact, telemetry readiness, and run cost depend on your environment, so the sample backlogs set them to 3 until you replace them.