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
noorqureshi/defense-dfir-triageDFIR and threat hunting

defense-dfir-triage

⁨First-response DFIR triage: scope an incident, collect volatile evidence, and find attacker activity on Linux/Windows. Load on "incident", "we got breached", "investigate this host", "IOCs", suspected compromise, or forensic triage. Signals: alert to investigate, suspicious host, "what happened".⁩

v2026.10.14-ee0e0c53 installs+3 in 7 days27 StarsMITsynced 22 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/defense-dfir-triage

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

SignatureSigned, ed25519
vbpihbhuMy…BwvdfWCQ==The CLI checks the SHA-256 and the signature before it writes a file.
Package57c55319…b3603eb5
57c553199d20…c362b3603eb51 file · ⁦1.4 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/defense/defense-dfir-triage@ee0e0c5

When it applies

A host or account is suspected compromised and you need to determine what happened, scope it, and preserve evidence — quickly, without destroying volatile data.

Why it works

Attacker activity leaves artifacts across a known set of locations (execution, persistence, logons, network). A disciplined order — preserve volatile first, then map to ATT&CK — gives a timeline and scope instead of a guess.

Method

  1. Preserve volatile first (order of volatility): memory (if warranted), then running processes, network connections, logged-on users — before shutdown/changes.
  2. Establish the timeline: parse Windows event logs (chainsaw/hayabusa with Sigma) or Linux logs/auth; look for initial access, execution, and lateral movement times.
  3. Check the usual artifacts:
    • Execution: prefetch/shimcache/amcache (Win), bash history//var/log (Linux), scheduled tasks/cron.
    • Persistence: services, run keys, WMI, startup, cron, systemd units, SSH keys.
    • Accounts/logons: new users, 4624/4625, sudo, privilege changes.
    • Network: current connections, DNS, beaconing patterns.
  4. Collect at scale with Velociraptor (hunts across hosts) to scope beyond one machine.
  5. Map findings to ATT&CK, extract IOCs, and hand detections to defense-detection-sigma.

Gotchas

  • Don't reboot/"clean" before capturing volatile evidence — you'll lose the memory/process picture.
  • Correlate timestamps across sources (watch timezones/clock skew) to build a real timeline.
  • Scope before remediating: one host is rarely the whole incident — hunt the IOCs fleet-wide.

Verify success

A timeline of attacker actions with initial access, persistence, and scope identified, plus IOCs and mapped ATT&CK techniques ready for detection/containment.

References

SANS DFIR posters; Velociraptor docs; chainsaw/hayabusa; MITRE ATT&CK.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

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

VersionPublishedCommitSHA-256SignaturePermission change
v2026.10.14-ee0e0c5Nov 13, 2026ee0e0c557c55319Signed–

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