aeondave/chainsaw
offensive-tools/forensic/chainsaw/SKILL.md
Fast DFIR triage for Windows forensic artifacts (EVTX, MFT, registry, ESE/SRUM) with Sigma and built-in detection logic. Use when analyzing exported Windows event logs, performing first-response hunting, detecting log tampering gaps, or producing CSV/JSON findings quickly without full SIEM infrastructure.
$ install --global
skillsauthnpx skillsauth add aeondave/malskill chainsawInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 9, 2026, 4:38 AM208.4s1 file scanned
SKILL.md
- name:
- chainsaw
- description:
- Fast DFIR triage for Windows forensic artifacts (EVTX, MFT, registry, ESE/SRUM) with Sigma and built-in detection logic. Use when analyzing exported Windows event logs, performing first-response hunting, detecting log tampering gaps, or producing CSV/JSON findings quickly without full SIEM infrastructure.
- license:
- GPL-3.0
- compatibility:
- Windows/Linux/macOS; standalone binary from GitHub releases
- author:
- AeonDave
- version:
- 1.1
Chainsaw
Rapid first-response hunting across Windows artifacts with Sigma + Chainsaw rules.
When to use
- You have exported
.evtxlogs 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
- Validate artifact scope (which channels and time range are present).
- Run
huntwith Sigma + mapping and optionally Chainsaw rules. - Export to CSV/JSON and pivot on key EventIDs.
- If tampering is suspected, run
analyse gaps. - Correlate detections with process, registry, and network evidence.
High-value modes
hunt→ detection logic over event logssearch→ targeted string/regex/tau queriesanalyse shimcache→ execution timeline + optional amcache enrichanalyse srum→ network/application usage artifactsanalyse gaps→ potential selective log deletion indicatorsdump→ raw structured extraction from supported artifacts
Practical analyst tips
- Prefer bounded time windows (
--from/--to) for cleaner triage. - Use
--fullonly 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.
Related Skills
aeondave/offensive-linux-role
data-ai
VerifiedTrustedCommunity
Scoped routing: Linux operator; hosts, sessions, users, services, packages, logs, containers, SSH, network paths, privilege evidence.
4SKILL.mdUpdated Jun 5, 2026
aeondave/ics-technique
development
VerifiedTrustedCommunity
Offensive methodology for ICS/OT/SCADA environments in authorized industrial penetration testing and red team operations. Use when assessing PLCs, RTUs, HMIs, engineering workstations, historians, or field devices running Modbus, DNP3, EtherNet/IP, S7comm/S7+, Profinet, IEC 60870-5-104, BACnet, or OPC-UA. Covers passive OT network enumeration, protocol-level device interrogation, PLC coil/register read-write attacks, HMI session exploitation, historian and engineering workstation compromise, and safe escalation rules for critical infrastructure scope. Does not cover: general IT network exploitation (network-technique), physical hardware interfaces UART/JTAG/SPI (hardware-technique), wireless sensor network attacks (wireless-technique), RF/SDR signal analysis (hardware-ctf or wireless-technique), or CTF-framed ICS lab tasks (ics-ctf).
4SKILL.mdUpdated Jun 2, 2026
aeondave/game-technique
tools
VerifiedTrustedCommunity
Offensive methodology for authorized game security assessments, game client security research, and game-adjacent penetration testing in real-world engagements. Use when assessing game clients for cheating vulnerabilities, testing anti-cheat effectiveness, auditing game server protocols for score manipulation or economic fraud, reverse engineering game DRM or license validation, analyzing game save file protection, or assessing game mod/plugin security. Covers: process memory scanning and manipulation (Cheat Engine methodology), game binary reversing for license and DRM bypass, game network protocol analysis and packet replay, anti-cheat mechanism analysis, save file format reversing and tampering, speed hack and value injection techniques. Does NOT cover: CTF game challenges (game-ctf), game engine source code auditing (web-exploit-technique or vuln-search-technique for the backend), or general binary exploitation (pwn-ctf or reversing-technique).
4SKILL.mdUpdated Jun 2, 2026
aeondave/hardware-technique
development
VerifiedTrustedCommunity
Auth assessment: hardware/embedded methodology; UART/JTAG/SWD/SPI/I2C, firmware extraction, boot/debug paths, embedded OS evidence.
4SKILL.mdUpdated Jun 2, 2026