Index of every page on this site: llms.txt
All skills
Run it yourself

Proactive threat hunt over web/application logs — no alert in hand. Profiles the corpus, runs a hypothesis-driven hunt loop with a mandatory written ledger, confirms suspects in source, detonates a local PoC, and writes INCIDENTS.json + INCIDENT_REPORT.md. Use when asked to "hunt the logs", "find the campaign", "look for signs of compromise", or "run dnr-hunt". The no-alert entry to the detection & response track; /dnr-respond is the lead-in-hand entry.

Requires /dnr-respond
Use this Skill: https://skilld.dev/gh/anthropics/defending-code-reference-harness/dnr-hunt

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

README.md

≈827 tokens on demand. Your agent reads this file only when SKILL.md points to it.

dnr-hunt

A Claude Code skill for proactive threat hunting over web/application logs: profiles the corpus, runs a hypothesis-driven hunt loop with a written ledger, confirms suspects in source, fires a local PoC, and writes INCIDENTS.json + INCIDENT_REPORT.md. The no-alert entry to the detection & response track — pairs with /dnr-respond (lead-in-hand workup) and feeds /triage → /patch; demo target: targets/dnrcanary. For how the track fits together, see docs/detection-response.md.

Requirements

  • Claude Code CLI installed and authenticated

  • A directory of logs. For the demo target they must be generated first (~82 MB, gitignored, byte-deterministic per seed on the same machine):

    pip install flask pyyaml               # flask runs the app; pyyaml runs the grader
    python3 targets/dnrcanary/generate_logs.py --seed 42

    The scenario briefing is in targets/dnrcanary/README.md.

  • Optionally the application source (--repo) — without it, findings cannot rise above suspected

Usage

/dnr-hunt                                  # defaults to targets/dnrcanary
/dnr-hunt targets/dnrcanary                # explicit dnr target
/dnr-hunt /var/log/myapp --repo ~/src/app  # your own logs + source
/dnr-hunt targets/dnrcanary --fresh        # ignore checkpoint, restart

Output

Outputs land in a per-run directory, results/<target>/<timestamp>/ — the same layout the other runbook skills use, so a new hunt never clobbers a previous one. /dnr-respond adopts the run dir automatically; /triage and /patch write to the directory they're invoked from, so run them from inside the run dir to keep their outputs beside the incidents.

  • <run>/INCIDENTS.json — incidents with verdicts (confirmed_exploited / suspected), attacker entities, timeline, quantified impact, evidence pipelines, and PoC; plus ruled_out for everything verdicted attempted_not_vulnerable or benign.
  • <run>/INCIDENT_REPORT.md — executive summary, campaign timeline, evidence per incident, and the full hypothesis ledger as the audit trail.

Example output: targets/dnrcanary/example_skill_runs/

On the demo target, score the result yourself afterwards: python3 targets/dnrcanary/grade.py <run>/INCIDENTS.json. The target README marks its answer-key files (ground truth, grader, log-generator source) as spoilers — keep them out of the hunt; grading is your move after the write-up. The autonomous harness enforces this structurally by excluding those files from the hunt container.

What it does and doesn't do

  • Does: query logs (grep/awk/DuckDB), maintain a hypothesis ledger, read source, start the demo app on 127.0.0.1 and fire minimal PoCs at it.
  • Does not: confirm anything from logs alone; execute response actions; send traffic to remote hosts. Blocking, rotation, and the like appear only as /dnr-respond proposals.

Installation and support are the same for all skills in this repo: see the repo README. Both DNR skills checkpoint their phase state under the run directory, so an interrupted session resumes where it left off.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning4mo3 checks · Risk SAFE
  • Gen Agent Trust Hub4mo

    The `dnr-hunt` skill is a threat hunting tool designed to analyze application logs, identify potential compromises, and verify vulnerabilities via local proof-of-concept (PoC) tests. It includes robust security guardrails such as strict local-only network constraints, detailed checkpointing for process auditing, and a requirement for source code verification before confirming incidents. While the skill interacts with the local system and executes commands, these actions are scoped to a controlled environment and follow security best practices.

  • Socket4mo

    1 alert: gptSecurity

  • Snyk4mo

    Risk: LOW · No issues

Signed by skilld at d3bea6b. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 4 weeks ago.

Steadyupdated 4 months ago
What it can do
Reads files Edits files Runs commands
argument-hint
[target-or-logs-dir] [--repo path] [--fresh]
All 21 allowed tools
ReadGlobGrepWriteBash(rg:*)Bash(grep:*)Bash(awk:*)Bash(sed:*)Bash(sort:*)Bash(uniq:*)Bash(cut:*)Bash(head:*)Bash(tail:*)Bash(wc:*)Bash(ls:*)Bash(du:*)Bash(file:*)Bash(jq:*)Bash(python3:*)Bash(curl:*)Bash(kill:*)

README badge

README badge for anthropics/defending-code-reference-harness/dnr-hunt