Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
meltedinhex/building-a-threat-hunt-hypothesisDFIR and threat hunting

building-a-threat-hunt-hypothesis

⁨Frames a structured, testable threat-hunting hypothesis: grounding it in adversary⁩

v1.0.03 installs+3 in 7 days24 StarsApache-2.0synced 11 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install meltedinhex/building-a-threat-hunt-hypothesis

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
gr/6/Qw7tr…8pRzsOCg==The CLI checks the SHA-256 and the signature before it writes a file.
Package3c12b2a5…ec2abb13
3c12b2a5e082…d91aec2abb134 files · ⁦3.0 KB⁩
ScanMedium2 findings
  • Executable script shipped with the skillscripts/analyst.py
  • Links to outside domains
See the full scan
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/building-a-threat-hunt-hypothesis@da7600a

When to Use

  • You are starting a proactive, hypothesis-driven hunt rather than responding to an alert.
  • You need to turn a vague concern ("are we seeing living-off-the-land abuse?") into a testable, scoped statement with clear data requirements.
  • You want a repeatable plan that produces either a detection, a gap, or a confident negative.

Do not use this as an incident-response trigger — if you already have a confirmed alert, pivot to investigation/IR, not hypothesis generation.

Prerequisites

  • Knowledge of your environment's telemetry (EDR, Sysmon, proxy, DNS, auth logs) and retention.
  • Familiarity with ATT&CK to anchor the behavior you intend to hunt.

Workflow

Step 1: Pick a behavior, not a tool

Anchor on an adversary behavior (an ATT&CK technique/sub-technique) you have reason to expect given your threat model, not a specific product alert.

Step 2: Write a testable hypothesis

Use the form: "If [actor behavior], then I expect to observe [evidence] in [data source]."

text
If an adversary uses WMI for lateral movement (T1047), then I expect to observe
wmiprvse.exe spawning command interpreters on hosts that do not normally do so,
in Sysmon process-creation (Event ID 1).

Step 3: Map to data and logic

Confirm the data source exists and is retained, then define the concrete query/detection logic and what "normal" looks like (baseline) so anomalies stand out.

bash
python scripts/analyst.py plan --technique T1047 --datasource "Sysmon EID1" --window 14d

Step 4: Set scope and success criteria

Define the host/time scope, the threshold for "interesting," and the three possible outcomes: finding (→ IR), detection gap (→ engineering), or confident negative (documented).

Step 5: Record and hand off

Capture the hypothesis, queries, and outcome so it becomes a repeatable, version-controlled hunt — successful logic becomes a detection rule.

Validation

  • The hypothesis is falsifiable and names a specific data source that actually exists.
  • A baseline of "normal" is defined so results are interpretable.
  • Each outcome has a defined next action (IR, detection engineering, or documented negative).

Pitfalls

  • Hunting for a tool name instead of a behavior, missing variants.
  • Writing a hypothesis you cannot test with available telemetry.
  • No baseline, so every result looks suspicious (or nothing does).

References

  • See references/api-reference.md for the hunt-plan generator.
  • MITRE ATT&CK and the PEAK framework (linked in frontmatter).

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumFile · Executable script shipped with the skillscripts/analyst.py
  2. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v1.0.0Nov 13, 2026da7600a3c12b2a5Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login