Skip to content
Back to search

HEARTH

A community-driven repository for threat hunting ideas, methodologies, and research that serves as a central gathering place for hunters to share knowledge, collaborate on techniques, and advance the field of threat hunting.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/THORCollective/HEARTH with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/THORCollective/HEARTH'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/thorcollective--hearth/badge.svg)](/listings/thorcollective--hearth)

HTML

<a href="/listings/thorcollective--hearth"><img src="/api/listings/thorcollective--hearth/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 227 lines
  1. <p align="center">
  2. <img src="https://github.com/THORCollective/HEARTH/blob/main/Assets/HEARTH-logo.png?raw=true" alt="HEARTH Logo" width="200"/>
  3. <h1 align="center">HEARTH: Hunting Exchange and Research Threat Hub</h1>
  4. <p align="center">
  5. An open-source community library of threat hunting hypotheses, powered by the PEAK framework and AI.
  6. <br />
  7. Built by <a href="https://github.com/THORCollective"><strong>THE THOR Collective</strong></a>
  8. </p>
  9. <p align="center">
  10. <a href="https://thorcollective.github.io/HEARTH/"><img src="https://img.shields.io/badge/Live_Database-Explore_Hunts-FF6B35?style=for-the-badge&logo=firefox-browser&logoColor=white" alt="Explore the Live Database" /></a>
  11. </p>
  12. <p align="center">
  13. <a href="https://github.com/THORCollective/HEARTH/blob/main/LICENSE"><img src="https://img.shields.io/github/license/THORCollective/HEARTH?style=flat-square" alt="License" /></a>
  14. <a href="/Keepers/Contributors.md"><img src="https://img.shields.io/badge/contributors-38+-blue?style=flat-square" alt="Contributors" /></a>
  15. <a href="https://github.com/THORCollective/HEARTH/issues"><img src="https://img.shields.io/github/issues/THORCollective/HEARTH?style=flat-square" alt="Issues" /></a>
  16. </p>
  17. <p align="center">
  18. <a href="https://thorcollective.github.io/HEARTH/">Explore the Database</a>
  19. &middot;
  20. <a href="https://github.com/THORCollective/HEARTH/issues/new/choose">Submit a Hunt</a>
  21. &middot;
  22. <a href="https://github.com/THORCollective/HEARTH/issues">Report a Bug</a>
  23. &middot;
  24. <a href="https://github.com/THORCollective/HEARTH/issues">Request a Feature</a>
  25. </p>
  26. </p>
  27. ---
  28. ## What is HEARTH?
  29. Generating effective, timely threat hunts is hard. You're staring at logs wondering where to start, or you're reading CTI reports and thinking _"someone should hunt for this"_ — but writing up the hypothesis takes time you don't have.
  30. **HEARTH is a community-curated library of 300+ threat hunting hypotheses** that security teams can use, adapt, and build on. Submit a CTI link and our AI pipeline drafts a complete hunt hypothesis for you. Or browse what others have shared, fork what works, and contribute back.
  31. Every hunt is categorized using the **[PEAK Threat Hunting Framework](https://www.splunk.com/en_us/blog/security/peak-threat-hunting-framework.html)**, giving you structured, actionable starting points — not vague ideas.
  32. ---
  33. ## The PEAK Framework
  34. HEARTH organizes hunts into three categories based on the PEAK framework. Each serves a different hunting approach:
  35. ### 🔥 Flames — Hypothesis-Driven Hunts (250+)
  36. Classic threat hunting. You have a specific theory about adversary behavior and you go looking for evidence. _"An adversary is using DLL side-loading to maintain persistence via a legitimate application."_
  37. ### 🪵 Embers — Baselining & Exploration (30+)
  38. Understand your environment before the bad stuff happens. Establish baselines, find anomalies, and discover what "normal" looks like so you can spot what isn't.
  39. ### 🔮 Alchemy — Model-Assisted Detection (25+)
  40. Algorithmic and ML-powered approaches. Statistical analysis, clustering, and other techniques that let the data surface threats you might not think to look for.
  41. > **[Browse all hunts in the live database &rarr;](https://thorcollective.github.io/HEARTH/)**
  42. ---
  43. ## Contribute a Hunt
  44. We've made contributing as frictionless as possible. Two paths:
  45. ### AI-Powered CTI Submission _(Recommended)_
  46. Have a great threat intel report? Paste the URL and let our AI pipeline do the work.
  47. 1. **[Open a CTI Submission &rarr;](https://github.com/THORCollective/HEARTH/issues/new?assignees=&labels=intel-submission%2C+needs-triage&template=cti_submission.yml&title=%5BCTI%5D+Brief+Description+of+Threat+Intel)**
  48. 2. Paste the URL and your name for attribution.
  49. 3. Our bot reads the report, drafts a hunt, checks for duplicates, and opens a PR for review.
  50. ### Manual Hunt Submission
  51. Already have a hypothesis? Submit it directly.
  52. 1. **[Open a Manual Submission &rarr;](https://github.com/THORCollective/HEARTH/issues/new?template=hunt_template.yaml&title=%5BHunt%5D+Brief+Description+of+Hunt+Idea)**
  53. 2. Fill out the template with your hypothesis, tactic, and references.
  54. 3. Maintainers review and merge.
  55. > All approved submissions are credited on the **[Contributors Leaderboard](/Keepers/Contributors.md)**.
  56. ### Templates
  57. Running a hunt in your own environment? `Kindling/` has the working templates:
  58. | Template | Use it for |
  59. | :------------------------------------------------- | :----------------------------------------------------- |
  60. | **[PEAK-Template.md](/Kindling/PEAK-Template.md)** | Planning, executing, and documenting a hunt end to end |
  61. | **[Hunt-Review.md](/Kindling/Hunt-Review.md)** | Writing up findings once the hunt is done |
  62. | **[Hunt-Template.md](/Kindling/Hunt-Template.md)** | The frontmatter format for submitting a hunt to HEARTH |
  63. | **[Resources.md](/Kindling/Resources.md)** | Reference material and further reading |
  64. Maintainers reviewing submissions: see **[Review-Process.md](/Keepers/Review-Process.md)**.
  65. ---
  66. ## Key Features
  67. | Feature | Description |
  68. | :--------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
  69. | **Interactive Database** | [Searchable, filterable, sortable](https://thorcollective.github.io/HEARTH/) interface for all hunts. Find what you need fast. |
  70. | **Coverage Heatmap** | [/coverage-heatmap.html](https://hearth.thorcollective.com/coverage-heatmap.html) — the full MITRE ATT&CK matrix, colored by how many community hunts cover each technique. Click a cell to see the hunts (or the gap). Lives alongside the [Coverage Map](https://hearth.thorcollective.com/graph.html) under the [Coverage hub](https://hearth.thorcollective.com/coverage.html). |
  71. | **AI-Powered CTI Analysis** | Submit a CTI link — **Claude** reads, analyzes, and drafts a complete hunt hypothesis automatically. |
  72. | **MITRE ATT&CK Integration** | Validates technique IDs against the full Enterprise framework (691 techniques, 99% accuracy). |
  73. | **Duplicate Detection** | AI-powered similarity analysis flags potential duplicates before they're merged, ranked by closeness with an explanation for each. |
  74. | **Automated Workflows** | GitHub Actions manage the full submission lifecycle — from draft to PR to merge. |
  75. | **Review & Regeneration** | Maintainers can re-roll AI-generated hunts by adding a `regenerate` label — iterate until it's right. |
  76. | **Contributor Leaderboard** | [Automated tracking](/Keepers/Contributors.md) of submissions. We celebrate our community. |
  77. ---
  78. <details>
  79. <summary><strong>Architecture</strong></summary>
  80. ### Hunt Storage
  81. - **Markdown files** in `Flames/`, `Embers/`, and `Alchemy/` are the **source of truth**
  82. - Human-readable, version-controlled, and easy to contribute via standard Git workflows
  83. - **Hunt schema:** Every hunt file uses YAML frontmatter — see [docs/HUNT-SCHEMA.md](docs/HUNT-SCHEMA.md).
  84. ### Database Index
  85. - **SQLite database** (`database/hunts.db`) provides a queryable index of every hunt
  86. - Automatically rebuilt when hunt files change
  87. - Used for reporting and ad-hoc queries. Duplicate detection reads the hunt files directly rather than this index
  88. - See [database/README.md](database/README.md) for details
  89. ### CTI Extraction
  90. - **Compression**: Brotli, Zstandard, and Gzip
  91. - **JS Rendering**: Falls back to readability-lxml for JS-heavy sites
  92. - **Formats**: HTML, PDF, and DOCX
  93. - **Smart Parsing**: Extracts article content from common blog/report structures
  94. ### MITRE ATT&CK Integration
  95. - **691 Techniques**: Complete Enterprise ATT&CK framework indexed
  96. - **Real-time Validation**: Technique IDs validated against MITRE data
  97. - **Confidence Scoring**: Multi-tier fallback (MITRE → table → keywords)
  98. ### Automation Workflows
  99. - Duplicate detection via vector embeddings
  100. - AI-powered hunt generation from CTI sources
  101. - Automatic database maintenance on file changes
  102. - TTP diversity analysis and content validation
  103. **Further reading:**
  104. [Database Architecture](database/README.md) · [Optimization Guide](docs/OPTIMIZATION_GUIDE.md) · [Testing Guide](docs/TESTING_GUIDE.md) · [Scripts](scripts/) · [Workflows](.github/workflows/)
  105. </details>
  106. <details>
  107. <summary><strong>Built With</strong></summary>
  108. - **Frontend**: HTML5, CSS3, Vanilla JavaScript
  109. - **Backend & Automation**: GitHub Actions, Python, Claude (Anthropic) API, OpenAI API, SQLite
  110. - **Hosting**: GitHub Pages
  111. </details>
  112. <details>
  113. <summary><strong>Configuration</strong></summary>
  114. For maintainers and self-hosted instances, HEARTH is configured via environment variables.
  115. | Variable | Description | Default | Required |
  116. | :------------------ | :--------------------------------- | :---------------- | :--------------- |
  117. | `AI_PROVIDER` | AI provider (`claude` or `openai`) | `claude` | No |
  118. | `ANTHROPIC_API_KEY` | API key for Claude | - | Yes (for Claude) |
  119. | `OPENAI_API_KEY` | API key for OpenAI | - | Yes (for OpenAI) |
  120. | `CLAUDE_MODEL` | Claude model version | `claude-sonnet-5` | No |
  121. **GitHub Actions setup:** Set `ANTHROPIC_API_KEY`, `OPENAI_API_KEY`, and `HEARTH_TOKEN` as **Repository Secrets**. Optionally set `AI_PROVIDER` and `CLAUDE_MODEL` as **Repository Variables**.
  122. </details>
  123. <details>
  124. <summary><strong>Troubleshooting</strong></summary>
  125. **"Failed to retrieve or process content from the URL"**
  126. - Verify the URL is correct and publicly accessible
  127. - Check if the article requires authentication or is behind a paywall
  128. - Try submitting content manually instead
  129. **Content appears garbled or incomplete**
  130. - The system now supports Brotli and Zstandard compression
  131. - If issues persist, try the manual submission workflow
  132. **Duplicate detection is slow or failing**
  133. - Database auto-rebuilds on file changes
  134. - Maintainers can manually rebuild: `python scripts/build_hunt_database.py --rebuild`
  135. - See [database/README.md](database/README.md)
  136. **Database appears out of sync**
  137. - Auto-updates via GitHub Actions on every merge to main
  138. - For local testing: `python scripts/build_hunt_database.py`
  139. For other issues, check [existing issues](https://github.com/THORCollective/HEARTH/issues) or [open a new one](https://github.com/THORCollective/HEARTH/issues/new).
  140. </details>
  141. ---
  142. ## License
  143. Distributed under the MIT License. See [`LICENSE`](LICENSE) for details.
  144. ---
  145. ## Acknowledgements
  146. HEARTH is a project of **THE THOR Collective**, co-founded and maintained by:
  147. - **Lauren Proehl** ([@jotunvillur](https://x.com/jotunvillur))
  148. - **Sydney Marrone** ([@letswastetime](https://x.com/letswastetime))
  149. - **John Grageda** ([@AngryInfoSecGuy](https://x.com/AngryInfoSecGuy))
  150. Built by the security community. See the full **[Contributors Leaderboard](/Keepers/Contributors.md)** for everyone who has contributed hunts.
  151. <p align="center">
  152. <strong>Keep the HEARTH burning.</strong>
  153. </p>

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.