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
aeondave/chainsawDFIR and threat hunting

chainsaw

⁨Auth/lab ref: Fast DFIR triage for Windows forensic artifacts (EVTX, MFT, registry, ESE/SRUM) with Sigma and built-in detection logic.⁩

v2026.11.13-21cd5683 installs+3 in 7 days39 StarsGPL-3.0synced 10 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/chainsaw

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

SignatureSigned, ed25519
tK+hcLU7Gp…lpOqNDAQ==The CLI checks the SHA-256 and the signature before it writes a file.
Packageb96bc382…ef75af55
b96bc3825700…7608ef75af551 file · ⁦1.3 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/AeonDave/malskill/tree/main/offensive-tools/forensic/chainsaw@21cd568

Rapid first-response hunting across Windows artifacts with Sigma + Chainsaw rules.

When to use

  • You have exported .evtx logs and need fast threat triage.
  • You need ScriptBlock/Defender/service/task detection without SIEM.
  • You want timeline-oriented findings in CSV/JSON for incident notes.
  • You suspect selective EVTX tampering and need record/time gap checks.

Core workflow

  1. Validate artifact scope (which channels and time range are present).
  2. Run hunt with Sigma + mapping and optionally Chainsaw rules.
  3. Export to CSV/JSON and pivot on key EventIDs.
  4. If tampering is suspected, run analyse gaps.
  5. Correlate detections with process, registry, and network evidence.

High-value modes

  • hunt → detection logic over event logs
  • search → targeted string/regex/tau queries
  • analyse shimcache → execution timeline + optional amcache enrich
  • analyse srum → network/application usage artifacts
  • analyse gaps → potential selective log deletion indicators
  • dump → raw structured extraction from supported artifacts

Practical analyst tips

  • Prefer bounded time windows (--from/--to) for cleaner triage.
  • Use --full only after narrowing candidates (reduces noise).
  • Keep Sigma repository current; rule freshness impacts detection quality.
  • Mark whether a finding is direct event evidence or rule-based inference.
  • Always preserve the original logs and operate on copies.

Common pitfalls

  • Treating rule hits as final verdict without context.
  • Mixing local and UTC timestamps during timeline reconstruction.
  • Running broad hunts across huge log sets without narrowing scope first.
  • Ignoring capture/log retention gaps when concluding absence of activity.

Output expectations

  • Detection table with timestamp, host, rule, event id, key fields.
  • List of high-confidence suspicious commands/actions.
  • Optional tampering assessment (analyse gaps) with confidence notes.
  • Correlation pointers for downstream timeline reconstruction.

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.11.13-21cd568Nov 13, 202621cd568b96bc382Signed–

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