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

evtxecmd

⁨Auth/lab ref: Windows EVTX parsing and timeline extraction with EvtxECmd.⁩

v2026.11.13-21cd5683 installs+3 in 7 days39 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 aeondave/evtxecmd

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

SignatureSigned, ed25519
LjJJdZhREG…Xr6Wo/AA==The CLI checks the SHA-256 and the signature before it writes a file.
Packagec2e2707a…69740663
c2e2707a0ae2…d4b0697406631 file · ⁦1.1 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/evtxecmd@21cd568

Deterministic extraction of Windows event logs for objective-driven incident analysis.

When to use

  • You need structured parsing of .evtx logs at scale.
  • You need precise ScriptBlock/process/account/security event timelines.
  • You want reproducible CSV/JSON exports for timeline reconstruction.
  • You need fast offline analysis without SIEM dependency.

Core workflow

  1. Identify high-value log channels relevant to the objective.
  2. Parse EVTX files into structured output.
  3. Pivot by event IDs, providers, host, user, and time window.
  4. Normalize timezone assumptions before cross-source correlation.
  5. Promote findings only when evidence pointers are explicit.

High-value event classes

  • PowerShell ScriptBlock logging
  • Process creation and command-line telemetry
  • Logon and account-management events
  • Service/task creation and persistence-related changes
  • Security-control tampering indicators (Defender, logging, policy)

Practical analyst tips

  • Keep raw EVTX immutable and parse from working copies.
  • Use narrow time windows first, then expand as needed.
  • Keep a channel inventory to avoid false “no evidence” conclusions.
  • Treat parser output as evidence index; validate critical claims in source records.

Common pitfalls

  • Mixing local and UTC timestamps during merge.
  • Relying on one channel while missing related provider logs.
  • Equating presence of suspicious strings with confirmed execution.
  • Ignoring record gaps or truncation when assessing coverage.

Output expectations

  • Structured event dataset (CSV/JSON) with provider, event id, timestamp, host, user.
  • Event clusters aligned to investigative objectives.
  • Evidence pointers (channel + record id + timestamp) for each key conclusion.

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, 202621cd568c2e2707aSigned–

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