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/evtxecmdWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Packagec2e2707a…69740663
c2e2707a0ae2…d4b0697406631 file · 1.1 KBScanLowno findings
Sourcegithub.com/AeonDave/malskill/tree/main/offensive-tools/forensic/evtxecmd@21cd568
On this page
Deterministic extraction of Windows event logs for objective-driven incident analysis.
When to use
- You need structured parsing of
.evtxlogs 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
- Identify high-value log channels relevant to the objective.
- Parse EVTX files into structured output.
- Pivot by event IDs, providers, host, user, and time window.
- Normalize timezone assumptions before cross-source correlation.
- 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
- SKILL.md2.0 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | No | No |
| Uses connectors | No | No |
| Drives a browser | No | No |
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.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | Nov 13, 2026 | 21cd568 | c2e2707a | Signed | – |
More from AeonDave
All from this publisherMore in DFIR and threat hunting
See the category- hunting-for-command-and-control-beaconingmukul975/hunting-for-command-and-control-beaconing5
- audit-context-buildingtrailofbits/audit-context-building4
- incident-response-forensicssecurityskills/incident-response-forensics3
- extracting-credentials-from-memory-dumpmukul975/extracting-credentials-from-memory-dump3
- analyzing-browser-forensics-with-hindsightmukul975/analyzing-browser-forensics-with-hindsight3
- forensics-ctfaeondave/forensics-ctf3
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login