Saltar al contenido
Nuevo

DeepSeek V4.1 Flash gratis por 7 días: 10M tokens al día tras una recarga de $10 o más. Hasta el 30/11.

Cómo funciona
meltedinhex/building-a-threat-hunt-hypothesisDFIR y threat hunting

building-a-threat-hunt-hypothesis

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

v1.0.03 instalaciones+3 en 7 días24 EstrellasApache-2.0sincronizado hace 10 horas

Instalar

¿Aún no tienes la CLI de NotHoly? Instálala primero.

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

Escribe en ⁦~/.notholy/skills⁩ después de comprobar la firma y el SHA-256.

FirmaFirmado, ed25519
gr/6/Qw7tr…8pRzsOCg==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquete3c12b2a5…ec2abb13
3c12b2a5e082…d91aec2abb134 archivos · ⁦3.0 KB⁩
EscaneoMedio2 hallazgos
  • Script ejecutable incluido con la skillscripts/analyst.py
  • Enlaces a dominios externos
Ver el escaneo completo
Fuentegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/building-a-threat-hunt-hypothesis@da7600a

Esta entrada todavía no está escrita en tu idioma, así que aparece en English.

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).

Archivos de esta versión

Permisos

PermisoDeclaradoHallado en el escaneo
Lee archivosNoNo
Escribe archivosNoNo
Ejecuta comandos de shellSíSí
Usa la redSíSí
Usa conectoresNoNo
Controla un navegadorNoNo

Hallazgos del escaneo

Revisado el 13 nov 2026

  1. MediaArchivo · Script ejecutable incluido con la skillscripts/analyst.py
  2. InfoEnlace · Enlaces a dominios externos

Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.

VersiónPublicadaCommitSHA-256FirmaCambio de permisos
v1.0.013 nov 2026da7600a3c12b2a5Firmada–

Pregunta todo lo que tu alcance permite.

Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.

  1. 1/3

    Crea la cuenta

    Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.

    IndividualEmpresa
  2. 2/3

    Añade créditos

    Con tarjeta. Pagas por token, sin suscripción.

    $5.00recarga mínima
  3. 3/3

    Pregunta

    En el chat, o instala el CLI y ejecuta notholy login en tu terminal.

    $ notholy login