PAGES
← all tools
◆ Digital Forensics & Incident Response

Hayabusa

v4.3.0 open-source

Hayabusa (隼) is a sigma-based threat hunting and fast forensics timeline generator for Windows event logs.

Summary

Hayabusa is an open-source, free command-line tool that parses Windows event logs (.evtx files) and builds a forensics timeline for incident response and threat hunting, aimed at DFIRDFIRDigital forensics and incident response, investigating what happened during a security incident and containing it. The work includes preserving evidence, reconstructing activity and restoring systems. practitioners and SOCSOCA security operations center, the team or function that monitors threats, investigates alerts and coordinates incident response. Its work can be internal, outsourced or shared. analysts working through host or enterprise-wide log data. It's written in memory-safe Rust and multi-threaded for speed, and its documentation describes it as the only open-source tool with full Sigma specification support, including v2 correlation rules, backed by thousands of curated detection rules. Results export as CSV, JSON or JSONLJSONLA text format where each line is a self-contained, valid JSON object, making it easy to stream, append, and process large datasets line by line without parsing a full JSON array into memory. for downstream review in Elastic Stack, Timesketch, or Timeline Explorer, and it can run on a single host or scale across an enterprise via the Velociraptor artifact. First committed in 2020, it remains active with 36 contributors and a release 18 days ago.

Hayabusa (隼) is a sigma-based threat hunting and fast forensics timeline generator for Windows event logs.

How Hayabusa helps

What happened on this host, in order, once every event log is pulled into one place?

builds a single consolidated timeline across all supplied evtx files, sorted by time, exportable as CSV, JSON or JSONL for review in Elastic Stack, Timesketch, or Timeline Explorer

Which events in this log set match known attacker techniques?

runs the full Sigma rule specification, including v2 correlation rules, against the logs using thousands of curated detection rules and flags each hit with its rule and severity

Did an attacker touch a domain controller or file server, and does that deserve extra attention?

lets critical hostnames be marked in advance, or auto-discovered for domain controllers and file servers, so any alert against them is automatically escalated one severity tier higher

Is this evtx file corrupted or tampered with before I trust what it says?

checks the chunk header checksums while building the timeline and reports integrity problems instead of silently parsing bad data

What does a single log file actually contain before I commit to processing it?

pulls per-file metadata — computer names, event counts, first and last timestamps, channels, and providers — so a file's coverage can be checked without a full run

Is there hidden base64-encoded content in these logs, such as PowerShell or service-creation activity?

scans events including PowerShell Classic and Core logs and service-creation records, extracts base64 strings, and decodes them into readable output

all 37 features, with the evidence for each →

Languages

Not documented

Features

37 capabilities across 5 areas

Built from Hayabusa's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • Hayabusa covers 1 of the 8 investigation and response capabilities we track.

What Hayabusa offers you

  • Command-line interface19
  • CSV data export4
  • JSON data export2
Threat Detection and Alerting 2 capabilities Hayabusa applies Sigma rules to Windows event logs to surface malicious or suspicious activity. Detection results are organised by MITRE ATT&CK tactic so analysts can understand coverage at a glance.
MITRE ATT&CK tactic coverage metrics shipped Shows how many alerts were raised per MITRE ATT&CK tactic, giving analysts a quick view of coverage across the kill chain. 8 releases · 2 other sources · first seen Jun 2022

Also counts toward: CSV data export

release 8 total

  • Adds unique and total alert counts per MITRE ATT&CK tactic in detection output summaries. v3.10.0 · Jul 2026 · source · release history
  • Adds unique and total alert counts per MITRE ATT&CK tactic in detection results, giving practitioners a clearer picture of tactic coverage across a scan. v3.10.0 · Jul 2026 · source · release history
  • Supports MITRE ATT&CK v19, keeping tactic and technique mappings current with the latest framework revision. v3.9.0 · Apr 2026 · source · release history
  • Updates MITRE ATT&CK tags to Sigma V2 format (e.g., defense_evasion → defense-evasion). v2.17.0 · Aug 2024 · source · release history
  • MITRE ATT&CK tags are reformatted to Sigma V2 style (e.g., defense_evasion → defense-evasion); tooling that matches on the underscore format will no longer match. v2.17.0 · Aug 2024 · source · release history
  • Changes %MitreTactics%, %MitreTags%, and %OtherTags% output in JSON from strings to arrays of strings. v2.12.0 · Dec 2023 · source · release history

example

  • View the time range of logs processed when scanning a directory with metrics. hayabusa metrics -d /logs/corporate/ v2.2.2 · Feb 2023 · source
  • Export findings to CSV including all rule tags for deeper MITRE ATT&CK mapping. hayabusa scan -f evtx.log --csv results.csv --all-tags v1.3.0 · Jun 2022 · source
Sigma rule detection with field modifiers shipped Evaluates Sigma rules against Windows event logs using advanced field modifiers, including negated and field-reference comparisons. 9 releases · 1 other source · first seen Apr 2022

release 9 total

  • Supports the |neq and |fieldref|neq field modifiers from the Sigma 2.1 specification, enabling negated comparisons combinable with |contains|neq, |startswith|neq, |endswith|neq, and more. v3.10.0 · Jul 2026 · source · release history
  • Supports Sigma 2.1 |neq and |fieldref|neq field modifiers, enabling negated comparisons composable with |contains, |startswith, |endswith, and |fieldref in detection rules. v3.10.0 · Jul 2026 · source · release history
  • Supports the fieldref modifier (alias for equalsfield) for comparing two fields in a Sigma rule. v2.18.0 · Oct 2024 · source · release history
  • Adds fieldref|endswith modifier as an alias for endswithfield, enabling field-to-field suffix comparisons. v2.18.0 · Oct 2024 · source · release history
  • Supports Sigma V2 |exists: modifier for field-existence checks in detection rules. v2.17.0 · Aug 2024 · source · release history
  • Supports Sigma V2 |cased: modifier for explicit case-sensitive matching. v2.17.0 · Aug 2024 · source · release history

example

  • Write a Sigma rule that fires when a process name does NOT start with svchost — using the new |startswith|neq modifier. # In your Sigma rule .yml: detection: selection: Image|startswith|neq: 'C:\Windows\System32\svchost' condition: selection v3.10.0 · Jul 2026 · source
DFIR Investigation and Forensics 3 capabilities Hayabusa builds forensic timelines from Windows event log data and exposes hidden encoded content buried in PowerShell logs. These outputs are designed to support incident response and digital forensic investigations.
DFIR forensic timeline shipped Generates a chronological forensic timeline of Windows event log activity and exports it in CSV, JSON, or JSONL format. 31 releases · 15 other sources · first seen Aug 2022

Shared capability: Forensic timeline analysis

Also counts toward: Command-line interface, CSV data export, JSON data export

release 31 total

  • Adds -Z, --timezone <OFFSET> to dfir-timeline, search, eid-metrics, logon-summary, log-metrics, and extract-base64 to render output timestamps with a fixed UTC offset in signed +HH:MM or -HH:MM form (e.g.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ --timezone "+09:00" or -Z "-01:00"); conflicts with --utc and… v4.3.0 · Oct 2026 · source · release history
  • Merges csv-timeline and json-timeline commands into a single dfir-timeline command, controlled by the -t, --output-type flag (supporting csv, json, and jsonl). v4.1.0 · Sep 2026 · source · release history
  • New dfir-timeline command replaces csv-timeline and json-timeline, with output format selected via -t, --output-type: -t csv (default), -t json, or -t jsonl (case-insensitive); CSV-only flags -M, --multiline, -S, --tab-separator, and -R, --remove-duplicate-data now error if used with a non-CSV -t. v4.0.0 · Aug 2026 · source · release history
  • Adds dfir-timeline command (merging old csv-timeline/json-timeline) with -t, --output-type to select CSV (default), JSON, or JSONL output v4.0.0 · Aug 2026 · source · release history
  • Adds -V, --validate-checksums option to csv-timeline and json-timeline commands to verify chunk header checksums in EVTX files. v3.7.0 · Nov 2025 · source · release history
  • Rule modified date outputs an empty string instead of - when not defined, easing SIEM import. v3.6.0 · Sep 2025 · source · release history

docs

  • 4.0.0 [2026/07/29] - Black Hat Arsenal USA Release Combined the commands into a single dfir-timeline command whose output format is chosen with -t, --output-type : unspecified or -t csv outputs CSV (default), -t json outputs JSON, and -t jsonl outputs JSONL. The value is case-insensitive (e.g. -t JSONL ). docs update · Aug 2026 · source
  • dfir-timeline command now have a scan wizard enabled by default. dfir-timeline command. dfir-timeline command. dfir-timeline dfir-timeline command creates a forensics timeline of events. Choose the output format with -t, --output-type csv (the default), json , or jsonl . The value is case-insensitive (e.g. -t JSONL ). docs update · Aug 2026 · source
  • dfir-timeline : Save the timeline in CSV/JSON/JSONL format. docs update · Aug 2026 · source
  • Windows event log fast forensics timeline generator and threat hunting tool that consolidates events into CSV/JSON/JSONL timelines with full Sigma rule support.

example 11 total

  • Generate a timeline in JSONL format for easy ingestion into downstream tools. hayabusa dfir-timeline -f detections.csv -t jsonl v4.1.0 · Sep 2026 · source
  • Export SIEM timeline data in JSONL format for downstream ingestion hayabusa dfir-timeline --output-type jsonl -i logs.evtx v4.0.0 · Aug 2026 · source
  • Verify EVTX chunk integrity while building a CSV timeline — useful when investigating potentially corrupted or tampered event logs. hayabusa csv-timeline -d /mnt/evidence/evtx -o timeline.csv -V v3.7.0 · Nov 2025 · source
  • Generate a CSV timeline without abbreviated Channel/Provider names so SIEM ingestion or manual review sees the canonical field values. hayabusa csv-timeline -d /mnt/evidence/evtx -b -o timeline.csv v2.19.0 · Nov 2024 · source
  • Filter timeline output to a specific EventID while excluding duplicates to save space. hayabusa csv-timeline --include-eid 4624 -R -i /path/to/logs v2.7.0 · Aug 2023 · source
  • Scan only rules that have been verified to work correctly, defined in the proven rules list file. hayabusa json-timeline --proven-rules -i /path/to/logs v2.7.0 · Aug 2023 · source
Logon activity summary shipped Summarises successful and failed logon events, including RDP activity, with first and last seen timestamps for each account. 15 releases · 5 other sources · first seen May 2022

Also counts toward: Command-line interface

release 15 total

  • Adds First Logon/Last Logon columns to the logon-summary successful logon table and First Attempt/Last Attempt columns to the failed logon table. v4.1.0 · Sep 2026 · source · release history
  • Adds -G, --geo-ip option to the logon-summary command to append Source ASN, Source Country, and Source City columns for each summarized logon source IP. v4.1.0 · Sep 2026 · source · release history
  • Adds -G, --geo-ip option to the logon-summary command, appending Source ASN, Source Country, and Source City columns for the source IP of each summarized logon. v4.1.0 · Sep 2026 · source · release history
  • Adds First Logon, Last Logon, First Attempt, and Last Attempt columns to the success and failure logon tables in logon-summary. v4.1.0 · Sep 2026 · source · release history
  • Expands logon-summary to aggregate RDP session events from Security event IDs 4778/4779, Terminal Services RemoteConnectionManager/Operational 1149, and LocalSessionManager/Operational 25, in addition to the existing 21 and 302 sources. v4.1.0 · Sep 2026 · source · release history
  • logon-summary now counts RDP session events: Security EIDs 4778/4779 (session reconnect/disconnect with client workstation name and IP) and Terminal Services events RemoteConnectionManager/Operational 1149 and LocalSessionManager/Operational 25, covering RDP activity even when 4624 events have been… v4.0.0 · Aug 2026 · source · release history

docs

  • x.x.x -G, --geo-ip command, which appends Source ASN Source Country Source City columns for the source IP address of each summarized logon. (#1920) (@fukusuket) docs update · Aug 2026 · source

example

  • Enrich logon summary with geographic data for source IPs. hayabusa logon-summary -f evidence.evtx -G v4.1.0 · Sep 2026 · source
  • Enrich a logon summary with GeoIP data to surface foreign source countries and ASNs for each summarized logon event. hayabusa logon-summary -d ./evtx/ -G ./GeoIP/ -o logon-summary.csv v4.1.0 · Sep 2026 · source
  • Customize the timestamp display format for session analysis in logon-summary. hayabusa logon-summary -t event_log.evtx --time-format iso8601 v2.2.2 · Feb 2023 · source
  • Generate a summary of logon events from EDR logs hayabusa -t edr -L -f logs.evtx v1.2.2 · May 2022 · source
Base64 extraction from PowerShell logs shipped Finds and decodes base64-encoded content hidden inside PowerShell event log entries across multiple event IDs and providers. 6 releases · 3 other sources · first seen Dec 2023

Also counts toward: Command-line interface

release

  • Expands extract-base64 to scan PowerShell event IDs 4100 and 4102 (Microsoft-Windows-PowerShell/Operational and PowerShellCore/Operational) and classic Windows PowerShell events 403/600, checking the ContextInfo and Payload fields for 4100/4102 and EventData.Data detail blocks for 403/600. v4.1.0 · Sep 2026 · source · release history
  • Expands extract-base64 command to scan PowerShell Event IDs 4100, 4102, 403, and 600 for encoded commands. v4.1.0 · Sep 2026 · source · release history
  • extract-base64 now scans PowerShell event IDs 4100/4102 (Microsoft-Windows-PowerShell/Operational and PowerShellCore/Operational) across ContextInfo and Payload fields, and classic Windows PowerShell EIDs 403/600 via the EventData.Data blob. v4.0.0 · Aug 2026 · source · release history
  • Adds PowerShell event IDs 4100, 4102, 403, and 600 extraction support to the extract-base64 command v4.0.0 · Aug 2026 · source · release history
  • Expands extract-base64 to cover PowerShell Classic EID 400 events, PowerShell Core logs, and System 7045 (Service Creation) events. v3.1.0 · Feb 2025 · source · release history
  • Adds --no-pwsh-field-extraction CLI argument to disable extraction of fields from PowerShell classic logs v2.11.0 · Dec 2023 · source · release history

example

  • Extract encoded commands from modern PowerShell operational logs using new event IDs hayabusa extract-base64 --eid 4100,4102 -i logs.evtx v4.0.0 · Aug 2026 · source
  • Extract base64-encoded payloads including PowerShell Core and service-creation events, then pipe tab-separated results into a SIEM-friendly CSV. hayabusa extract-base64 -d /mnt/evtx && hayabusa csv-timeline -d /mnt/evtx -S -o timeline_tabs.csv v3.1.0 · Feb 2025 · source
  • Scan PowerShell logs while forcing legacy parsing to match older output formats or reduce resource usage. hayabusa -t winlog --no-pwsh-field-extraction v2.11.0 · Dec 2023 · source
Input Flexibility and Platform Support 2 capabilities Hayabusa can ingest Windows event log data in multiple formats and runs natively on a range of operating systems including Linux ARM64. This allows it to fit into varied collection pipelines and deployment environments.
JSON log input shipped Accepts Windows event log data supplied as JSON or JSONL files, not just native .evtx files. 5 releases · 2 other sources · first seen Feb 2023

release

  • JSON input now supports the format exported from Splunk v2.14.0 · Mar 2024 · source · release history
  • Enables parsing of JSON input sources where the data is nested inside an array v2.13.0 · Feb 2024 · source · release history
  • Adds -G, --GeoIP CLI flag to enrich results with ASN organization, city, and country via MaxMind databases v2.2.0 · Feb 2023 · source · release history
  • Adds --JSON-input (-J) CLI flag to read JSON-formatted event logs as new input source v2.2.0 · Feb 2023 · source · release history
  • Adds -e, --exact-level option to filter scan results for specific rule levels v2.2.0 · Feb 2023 · source · release history

docs

  • Usage: hayabusa.exe computer-metrics <INPUT> [OPTIONS] -J, --json-input Scan JSON formatted logs instead of .evtx (.json or .jsonl) -V, --validate-checksums Enable checksum validation Usage: hayabusa.exe eid-metrics <INPUT> [OPTIONS] -J, --json-input Scan JSON formatted logs instead of .evtx (.json or .jsonl)… docs update · Aug 2026 · source

example

  • Scan a JSON event log file with IP enrichment enabled. hayabusa -t evtx -f events.json -J -G v2.2.0 · Feb 2023 · source
Linux ARM64 (aarch64) support shipped Runs natively on Linux aarch64 systems via a dedicated binary built with a musl cross toolchain. 4 releases · first seen Aug 2025

release

  • Adds Linux aarch64 (ARM64) musl release binary (hayabusa-<ver>-lin-aarch64-musl), built with a correct aarch64 musl cross-toolchain. v4.1.0 · Sep 2026 · source · release history
  • Adds Linux aarch64 musl release binaries (hayabusa-<ver>-lin-aarch64-musl) for ARM64 systems. v4.1.0 · Sep 2026 · source · release history
  • New Linux aarch64 (ARM64) musl release binary (hayabusa-<ver>-lin-aarch64-musl) built with a proper aarch64 musl cross toolchain. v4.0.0 · Aug 2026 · source · release history
  • Enables the 32-bit Hayabusa binary to run on 64-bit operating systems. v3.4.0 · Aug 2025 · source · release history
Configuration and Usability 2 capabilities Hayabusa provides options for tailoring analysis behaviour, such as marking certain hosts as critical, and enforces consistent command-line conventions to make scripting and day-to-day use predictable.
Critical systems configuration shipped Lets users designate specific systems as critical so they receive appropriate weighting during analysis. 6 releases · 6 other sources · first seen Mar 2022

Also counts toward: Command-line interface

release

  • New emergency severity level: add critical system hostnames (DCs, file servers) to config/critical_systems.txt and alerts automatically escalate one tier higher, with critical becoming emergency. v3.1.0 · Feb 2025 · source · release history
  • New config-critical-systems command automatically discovers domain controllers and file servers and populates ./config/critical_systems.txt. v3.1.0 · Feb 2025 · source · release history
  • |cidr pipe keyword adds CIDR matching capability in rules v2.3.0 · Mar 2023 · source · release history
  • Added support for the |base64offset|contains pipe keyword. v2.2.2 · Feb 2023 · source · release history
  • Adds the --debug CLI flag to display runtime memory utilization. v1.9.0 · Dec 2022 · source · release history
  • Adds -r / --rules option to specify a single rule for targeted testing v1.1.0 · Mar 2022 · source · release history

docs

  • -G, --geo-ip <MAXMIND-DB-DIR> Add GeoIP (ASN, city, country) info to source IP addresses GeoIP enrichment With -G, --geo-ip pointing at a directory that contains the MaxMind GeoLite2-ASN.mmdb GeoLite2-Country.mmdb GeoLite2-City.mmdb databases, the source IP address of each row is looked up and Source ASN Source… docs update · Aug 2026 · source
  • Usage: hayabusa.exe config-critical-systems <INPUT> [OPTIONS] docs update · Aug 2026 · source

example

  • Run a standard non-interactive scan, bypassing the wizard hayabusa -f evidence.evtx --no-wizard v2.10.0 · Oct 2023 · source
  • Match event data against a specific CIDR range using the new pipe # In rule YAML: pipe: "|cidr" v2.3.0 · Mar 2023 · source
  • Detect base64-encoded strings at a specific byte offset within an event log field using the new pipe keyword. hayabusa scan -r rules/ -t event_log.evtx -k 'Field Value |base64offset|contains "password"' v2.2.2 · Feb 2023 · source
  • Monitor memory consumption during a scan to identify resource-intensive rules. hayabusa -f rule.yml -i event.evtx --debug v1.9.0 · Dec 2022 · source
CLI option naming conventions shipped Uses lowercase kebab-case for all long-form command-line options, making the interface consistent and easy to script. 7 releases · first seen Mar 2022

Also counts toward: Command-line interface

release 7 total

  • The -t short flag is now assigned to --output-type for the dfir-timeline command; the previous --threads short form is no longer available (use --threads long form instead). v4.1.0 · Sep 2026 · source · release history
  • All command-line option long names standardized to lowercase: --GeoIP→--geo-ip, --HTML-report→--html-report, --UTC→--utc, --ISO-8601→--iso-8601, --RFC-2822/--RFC-3339→--rfc-2822/--rfc-3339, --JSON-input/--JSON-output→--json-input/--json-output, --EID-filter→--eid-filter; short flags… v4.0.0 · Aug 2026 · source · release history
  • Long-form flags renamed: --GeoIP→--geo-ip, --HTML-report→--html-report, --UTC→--utc, --ISO-8601→--iso-8601, --RFC-2822→--rfc-2822, --RFC-3339→--rfc-3339, --JSON-input→--json-input, --JSON-output→--json-output, --EID-filter→--eid-filter; any scripts using the old uppercase forms will… v4.0.0 · Aug 2026 · source · release history
  • Long CLI options are lowercased and hyphenated: --GeoIP→--geo-ip, --HTML-report→--html-report, --UTC→--utc, --ISO-8601→--iso-8601, --RFC-2822/--RFC-3339→--rfc-2822/--rfc-3339, --US-time/--US-military-time/--European-time→lowercase,… v4.0.0 · Aug 2026 · source · release history
  • The -t shorthand now maps to --output-type instead of --threads v4.0.0 · Aug 2026 · source · release history
  • Renames the --live_analysis option to --live-analysis v2.7.0 · Aug 2023 · source · release history
Other 28 capabilities
Pivot keyword generation shipped Generates a list of keywords from detection results to facilitate pivoting and deeper investigation into related artifacts. 7 releases · 3 other sources · first seen Apr 2022

Also counts toward: Command-line interface

release 7 total

  • Adds --include-tag option to the pivot-keywords-list command to load only rules matching specified tags v2.10.0 · Oct 2023 · source · release history
  • Adds --exclude-tag option to the pivot-keywords-list command to skip loading rules with specific tags v2.10.0 · Oct 2023 · source · release history
  • Adds -C, --clobber flag to pivot-keywords-list command to overwrite existing output files v2.7.0 · Aug 2023 · source · release history
  • Adds -M, --multiline flag to the search subcommand to enable multi-line string matching. v2.5.0 · May 2023 · source · release history
  • Adds search command to search for specified keywords in records v2.4.0 · Apr 2023 · source · release history
  • Adds -r, --regex option in the search command to search for regular expressions v2.4.0 · Apr 2023 · source · release history

example

  • Use AND logic in a search to find events where both cmd.exe and /c appear. hayabusa search -a -k 'cmd.exe, /c' v2.8.0 · Sep 2023 · source
  • Search event records for a specific attacker IP address to rapidly triage a potential incident. hayabusa search -i /path/to/logs.evtx --keyword "192.168.1.55" v2.4.0 · Apr 2023 · source
  • Identify suspicious PowerShell execution patterns using regex within the search module. hayabusa search -i /path/to/logs.evtx --regex "Invoke-Expression|IEX.*-EncodedCommand" v2.4.0 · Apr 2023 · source
Full data output expansion shipped suggested Outputs all field information beyond the rule's details section for comprehensive forensic analysis. 6 releases · first seen Apr 2022

Suggested capability: Forensic timeline analysis. This is our guess, not confirmed.

Also counts toward: Command-line interface, JSON data export

release

  • Adds RuleID field to all output profiles except minimal. v3.1.0 · Feb 2025 · source · release history
  • Supports the expand field modifier in detection rules. v3.0.0 · Dec 2024 · source · release history
  • Adds log file size output to the log-metrics command. v3.0.0 · Dec 2024 · source · release history
  • Adds -C, --clobber to csv-timeline, json-timeline, metrics, logon-summary, and search commands to overwrite existing output files. v2.6.0 · Jun 2023 · source · release history
  • Allows the search command to output results in JSON or JSONL format. v2.6.0 · Jun 2023 · source · release history
  • -F / --full-data flag added to output all field information beyond the rule's details v1.2.0 · Apr 2022 · source · release history
Custom rule repository support shipped Allows specifying a custom directory for rules and enabling automatic updates from external repositories like `hayabusa-rules`. 5 releases · first seen Mar 2022

Also counts toward: Command-line interface

release

  • New -S, --tab-separator option in csv-timeline, search, and log-metrics commands to delimit field output with tabs. v3.1.0 · Feb 2025 · source · release history
  • Supports XOR-encoded rule bundles (encoded_rules.yml) to minimize files on target systems and avoid antivirus false positives on rule content. v2.18.0 · Oct 2024 · source · release history
  • Loads rules/config files from a single rules_config_files.txt bundle, reducing the file footprint needed during live response. v2.18.0 · Oct 2024 · source · release history
  • -C / --config flag added to specify a custom rules directory instead of the default location v1.2.0 · Apr 2022 · source · release history
  • Adds -u / --update-rules flag to update rules from the hayabusa-rules repository v1.1.0 · Mar 2022 · source · release history
Log metadata metrics command shipped suggested Provides a command to retrieve per-file metadata for EVTX logs, including computer names, event counts, and time ranges. 2 releases · 2 other sources · first seen Nov 2024

Suggested capability: Forensic timeline analysis. This is our guess, not confirmed.

Also counts toward: Command-line interface

release

  • Adds --include-channel, --exclude-channel, --include-filename, and --exclude-filename options to the log-metrics command for targeted log analysis. v3.7.0 · Nov 2025 · source · release history
  • New log-metrics command retrieves per-file .evtx metadata: computer names, event count, first/last timestamps, channels, and providers. v2.19.0 · Nov 2024 · source · release history

example

  • Scope log-metrics to a specific channel and filename pattern to quickly profile activity from a single source without noise from other logs. hayabusa log-metrics -d /mnt/evidence/evtx --include-channel Security --include-filename Security.evtx v3.7.0 · Nov 2025 · source
  • Quickly profile a collection of EVTX files to understand their time range, event counts, and sources before running a full timeline. hayabusa log-metrics -d /mnt/evidence/evtx v2.19.0 · Nov 2024 · source
Canonical field name output shipped suggested Outputs raw Channel and Provider values without abbreviation to ensure compatibility with SIEM ingestion and downstream parsers. 2 releases · 2 other sources · first seen Nov 2024

Suggested capability: Forensic timeline analysis. This is our guess, not confirmed.

Also counts toward: Command-line interface, CSV data export

release

  • Adds automatic field-name abbreviations in the search command output, disableable with -b, --disable-abbreviations. v3.4.0 · Aug 2025 · source · release history
  • New -b, --disable-abbreviations option for csv-timeline, json-timeline, eid-metrics, log-metrics, and search commands to output raw Channel and Provider values instead of abbreviated forms. v2.19.0 · Nov 2024 · source · release history

example

  • Run a search and keep full, unabbreviated field names in the output for easier parsing or correlation. hayabusa search -d <evtx-dir> -b v3.4.0 · Aug 2025 · source
  • Generate a CSV timeline without abbreviated Channel/Provider names so SIEM ingestion or manual review sees the canonical field values. hayabusa csv-timeline -d /mnt/evidence/evtx -b -o timeline.csv v2.19.0 · Nov 2024 · source
Output profile management shipped Allows discovering, listing, and selecting from customizable output profiles for diverse export needs. 3 releases · 1 other source · first seen Oct 2022

Also counts toward: Command-line interface

release

  • The Details field in count rule JSON output is now a string for easier parsing v2.9.0 · Sep 2023 · source · release history
  • Adds %ExtraFieldInfo% alias to output profiles for fields not included in Details, now default in the standard profile. v2.6.0 · Jun 2023 · source · release history
  • Adds --list-profiles flag to print available output profiles v1.7.2 · Oct 2022 · source · release history

example

  • Discover which output profiles are available for use with the tool. hayabusa --list-profiles v1.7.2 · Oct 2022 · source
Computer metrics reporting shipped Lists event counts grouped by computer name. 2 releases · 1 other source · first seen Aug 2023

Also counts toward: Command-line interface

release

  • Adds uptime and timezone info to the computer-metrics command output. v3.2.0 · Apr 2025 · source · release history
  • Adds OS information output to the computer-metrics command. v3.1.1 · Mar 2025 · source · release history

example

  • Run the renamed metrics command to get event counts by computer name, ignoring duplicates. hayabusa eid-metrics --exclude-computer "LEGACY-PC" -i /path/to/logs v2.7.0 · Aug 2023 · source
Low-memory scanning mode shipped Reduces memory usage during analysis by disabling duplicate removal and sorting events, allowing scans on resource-constrained systems. 1 release · 2 other sources · first seen Mar 2024

release

  • Adds -s, --low-memory-mode option to reduce memory usage by up to 95% v2.14.0 · Mar 2024 · source · release history

example

  • Search a narrow time window in a large evidence set with minimal memory use, then sort only when needed for review. hayabusa search -d /mnt/evtx --timeline-start "2025-01-01T00:00:00" --timeline-end "2025-01-31T23:59:59" -s -o results.csv v3.1.0 · Feb 2025 · source
  • Scan large logs on a resource-constrained system while disabling duplicate removal to save memory. hayabusa search -t /path/to/large_logs.log -s v2.14.0 · Mar 2024 · source
Base64 payload extraction and decoding shipped Extracts and decodes base64-encoded content from event logs, including support for chained modifiers with UTF-16 encoding. 1 release · 2 other sources · first seen Nov 2024

Also counts toward: Command-line interface

release

  • New extract-base64 command extracts and decodes base64 strings from events. v3.0.0 · Dec 2024 · source · release history

example

  • Uncover encoded payloads hiding in event logs by extracting and decoding all base64 strings in one pass. hayabusa extract-base64 -d <evtx-dir> v3.0.0 · Dec 2024 · source
  • Detect base64-encoded UTF-16 strings hidden in PowerShell command lines using the new chained modifier support in a Sigma-style rule. detection: selection: CommandLine|utf16le|base64offset|contains: 'Invoke-Mimikatz' v2.19.0 · Nov 2024 · source
Sigma V2 correlation rules shipped Supports advanced Sigma V2 correlation rules including temporal proximity and name lookups for complex detection scenarios. 3 releases · first seen Dec 2024

release

  • Supports Temporal Proximity (temporal) correlation rules. v3.0.0 · Dec 2024 · source · release history
  • Supports Temporal Ordered Proximity (temporal_ordered) correlation rules. v3.0.0 · Dec 2024 · source · release history
  • Adds log file size output to the log-metrics command. v3.0.0 · Dec 2024 · source · release history
Visual event timeline shipped Generates a visual representation of event frequency directly in the terminal or exports it for downstream visualization. 1 release · 2 other sources · first seen Jun 2022

Also counts toward: Command-line interface

release

  • --visualize-timeline (alias -V) enables a new event frequency timeline visualization feature v1.3.0 · Jun 2022 · source · release history

example

  • Export timeline data with multiline formatting enabled using the new option. hayabusa csv-timeline -M input.log v2.3.2 · Mar 2023 · source
  • Generate a visual timeline of event frequency directly in the terminal. hayabusa scan -f evtx.log --visualize-timeline v1.3.0 · Jun 2022 · source
Encoded rule bundle support shipped Supports loading rule bundles from encoded YAML files to reduce file count and avoid antivirus detection during deployment. 2 releases · first seen Oct 2024

release

  • Supports XOR-encoded rule bundles (encoded_rules.yml) to minimize files on target systems and avoid antivirus false positives on rule content. v2.18.0 · Oct 2024 · source · release history
  • Loads rules/config files from a single rules_config_files.txt bundle, reducing the file footprint needed during live response. v2.18.0 · Oct 2024 · source · release history
Deep scan capability shipped Bypasses default Event ID filters to perform a thorough scan of all events for deeper investigation capabilities. 1 release · 1 other source · first seen Jun 2022

release

  • Adds the -D, --deep-scan flag to bypass the default Event ID filter and scan all events instead of only those with defined rules. v1.4.1 · Jun 2022 · source · release history

example

  • Scan all event logs in multiple directories without channel filtering to catch cross-channel threats. hayabusa csv-timeline -d /path/to/logs1 -d /path/to/logs2 -a -A v2.16.0 · Jun 2024 · source
Splunk log input support shipped Accepts logs exported from the Splunk REST API as a direct input source without manual conversion. 1 release · 1 other source · first seen Jun 2024

release

  • Adds support for analyzing Splunk logs exported from the REST API via a new input format v2.16.0 · Jun 2024 · source · release history

example

  • Parse Splunk REST API exported logs directly using the new input type. hayabusa json-timeline -J path/to/splunk_export.json v2.16.0 · Jun 2024 · source
Rule status filtering shipped Allows filtering detection rules by their status (e.g., active, deprecated) to reduce false positives from outdated detections. 1 release · 1 other source · first seen Mar 2024

release

  • Adds --include-status option to filter rules by their status v2.14.0 · Mar 2024 · source · release history

example

  • Run a scan using only active rules to reduce false positives from deprecated detections. hayabusa search -t /path/to/logs --include-status "active" v2.14.0 · Mar 2024 · source
HTML report generation shipped Generates an HTML summary report of detection findings for easier sharing and review. 2 releases · first seen Sep 2022

release

  • Adds a MITRE ATT&CK tactics summary to the HTML report for each detected computer. v2.12.0 · Dec 2023 · source · release history
  • Adds -H, --html-report flag to generate an HTML summary report v1.7.0 · Sep 2022 · source · release history
Record recovery shipped suggested Recovers hidden or deleted EVTX records from slack space during timeline analysis. 1 release · 1 other source · first seen Sep 2023

Suggested capability: Disk and filesystem forensics. This is our guess, not confirmed.

Also counts toward: Command-line interface

release

  • Adds %RecoveredRecord% field to the output profile when using --recover-records v2.8.0 · Sep 2023 · source · release history

example

  • Carve and recover hidden or deleted EVTX records from slack space during timeline analysis. hayabusa csv-timeline -x /path/to/evidence.evtx v2.8.0 · Sep 2023 · source
Sorted log file scanning order documented Scans discovered log files (evtx, JSON, or JSONL) in sorted path order rather than filesystem enumeration order during live analysis. 1 other source · first seen Oct 2026

docs

  • Log files found with -l, --live-analysis (evtx files, or JSON/JSONL files with -J ) are now scanned in sorted path order instead of the order the filesystem lists them. docs update · Oct 2026 · source
CSV post-processing and deduplication documented suggested Provides a command to sort CSV output by timestamp and remove duplicate detections across multiple endpoint files. 1 other source · first seen Sep 2026

Suggested capability: Forensic timeline analysis. This is our guess, not confirmed.

Also counts toward: Command-line interface

docs

  • sort-csv command that post-processes a Hayabusa CSV: it keeps the header, sorts the rows by the Timestamp column, and removes duplicate detections (comparing every column except , so the same event collected from overlapping/backup files collapses to one entry). docs update · Sep 2026 · source
Time-range filtering shipped suggested Filters event log analysis to a specific start and end time window using command-line options. 1 release · first seen Feb 2025

Suggested capability: Forensic timeline analysis. This is our guess, not confirmed.

Also counts toward: Command-line interface

release

  • Adds --timeline-start / --timeline-end time-range filtering options to the search command. v3.1.0 · Feb 2025 · source · release history
Renamed time offset option shipped suggested The `--timeline-offset` command-line option has been renamed to `--time-offset`. 1 release · first seen Nov 2024

Suggested capability: Forensic timeline analysis. This is our guess, not confirmed.

Also counts toward: Command-line interface

release

  • The --timeline-offset option has been renamed to --time-offset; any scripts or workflows using --timeline-offset will break. v2.19.0 · Nov 2024 · source · release history
Interactive scan wizard shipped Guides users through rule selection and configuration during a scan via an interactive CLI interface. 1 release · first seen Oct 2023

Also counts toward: Command-line interface

release

  • Adds the -w, --no-wizard option to enable an interactive scan wizard for rule selection, with traditional execution restored via --no-wizard v2.10.0 · Oct 2023 · source · release history
Hex to decimal field mapping shipped Maps hex field values to decimal numbers using configuration files. 1 release · first seen Sep 2023

release

  • Adds support for HexToDecimal in field mapping configuration files to convert hex values to decimal v2.8.0 · Sep 2023 · source · release history
Channel and Event ID mapping configuration shipped Allows configuring mappings between Windows event channels and event IDs to improve detection accuracy. 1 release · first seen Oct 2022

release

  • Adds rules/config/channel_eid_info.txt to configure Channel and EID mappings for more accurate detection results. v1.7.1 · Oct 2022 · source · release history
Rule author display in output shipped Displays the author of each detection rule in the standard output during scanning. 1 release · first seen Oct 2022

release

Timesketch output compatibility shipped suggested Generates CSV format compatible with Timesketch imports for seamless ingestion into the platform. 1 release · first seen Aug 2022

Suggested capability: Forensic timeline analysis. This is our guess, not confirmed.

Also counts toward: CSV data export

release

  • Adds a new timesketch output profile that generates CSV format compatible with Timesketch imports v1.5.1 · Aug 2022 · source · release history
Non-evtx log scanning shipped suggested Scans non-evtx binary log files that mimic evtx structure by specifying additional file extensions. 1 release · first seen Jun 2022

Suggested capability: Disk and filesystem forensics. This is our guess, not confirmed.

release

  • Adds --target-file-ext CLI option to specify additional file extensions (e.g., evtx_data) beyond the default .evtx for scanning v1.4.0 · Jun 2022 · source · release history
Live analysis mode shipped Performs live analysis on Windows systems without requiring a pre-exported event log directory, leveraging real-time event stream processing. 1 release · first seen Mar 2022

release

  • Adds -l / --live-analysis option to perform live analysis on Windows without specifying the event log directory v1.1.0 · Mar 2022 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for Hayabusa, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail Hayabusa puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

Show

63 entries

  1. October 20262
  2. September 20262
  3. August 20268
  4. July 20261
  5. April 20261
  6. November 20251
  7. September 20251
  8. August 20251
  9. April 20251
  10. March 20251
  11. February 20251
  12. December 20241
  13. November 20241
  14. October 20241
  15. August 20241
  16. June 20241
  17. April 20241
  18. March 20241
  19. February 20241
  20. December 20232
  21. November 20231
  22. October 20231
  23. September 20232
  24. August 20231
  25. June 20231
  26. May 20231
  27. April 20232
  28. March 20233
  29. February 20232
  30. December 20222
  31. November 20222
  32. October 20222
  33. September 20222
  34. August 20222
  35. July 20221
  36. June 20224
  37. May 20221
  38. April 20222
  39. March 20221
    Show

    63 entries

    Project health

    Issue, contributor and maintainer activity in Yamato-Security/hayabusa, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 12 +2 vs prior 12 months
    2. Maintainers 3 +2 joined · −2 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 6% of issues opened, last 12 months
    5. Median time to close < 1 day first maintainer reply 2.9 hours
    6. Open backlog 18 of 822 issues ever filed
    1. Issues opened / month 1 · 1 communitymaintainers
    2. Open backlog 18
    3. Contributors / month 2
    4. Commits / month 6
    5. Stars 3,346
    Issue themes, last 12 months
    • bugs 19%
    • features 7%
    • other 74%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →