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/scoping-an-incident-from-a-single-indicatorDFIR and threat hunting

scoping-an-incident-from-a-single-indicator

⁨Expands one indicator into the full scope of an incident: pivoting across data⁩

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

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install meltedinhex/scoping-an-incident-from-a-single-indicator

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

SignatureSigned, ed25519
MJiGW8vJqs…zwPnmzBg==The CLI checks the SHA-256 and the signature before it writes a file.
Packagefc342bee…969e9102
fc342beeb189…0bcb969e91024 files · ⁦3.1 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/scoping-an-incident-from-a-single-indicator@da7600a

When to Use

  • A detection fired on one indicator (a hash, IP, domain, or account) and you must find the full extent of the activity.
  • You need to bound the incident — which hosts, accounts, and infrastructure are involved — before containment.
  • You are building an investigative timeline from a single starting point.

Do not use premature containment on the first indicator alone — acting before scoping can tip off the adversary and leave footholds you have not yet found.

Prerequisites

  • Access to relevant data sources (EDR, proxy, DNS, auth logs) and the pivoting/enrichment skills.

Workflow

Step 1: Characterize the seed indicator

Establish what the indicator is, when it was first/last seen, and on which host/account it appeared.

Expand outward: the file's other hosts, the IP's other connections, the account's other logons, the domain's other resolvers. Each pivot yields new indicators to pivot again.

bash
python scripts/analyst.py scope events.json --seed <sha256-or-ip>

Step 3: Build the timeline

Order all discovered events chronologically to reconstruct the activity and find the earliest sign (candidate patient zero / initial access).

Step 4: Bound the scope

Define affected vs. unaffected explicitly: list involved hosts/accounts/infrastructure and the evidence for inclusion, and note what was checked and cleared.

Step 5: Hand off to containment

Produce the scoped picture (entities, timeline, indicators) so containment is coordinated and complete rather than piecemeal.

Validation

  • Every included entity has explicit evidence tying it to the incident.
  • The timeline has a defensible earliest event (initial access candidate).
  • Cleared entities are documented, so scope is bounded, not open-ended.

Pitfalls

  • Containing the first host before pivoting, alerting the adversary and missing other footholds.
  • Pivoting only one hop and missing second-order related entities.
  • No timeline, so initial access and dwell time stay unknown.

References

  • See references/api-reference.md for the pivot/scope helper.
  • NIST SP 800-61 and MITRE ATT&CK (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, 2026da7600afc342beeSigned–

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