PAGES
← all tools
◆ Endpoint Security (EDR/XDR)

Fibratus

v3.1.0 open-source

Security sensor for realtime threat detection and protection

Summary

Fibratus is an open-source security sensor for Windows that watches system events in real time and matches them against a behavior-driven rule engine and YARA memory scanner to catch attacker tradecraft, malware, and other emerging threats. It runs as an agent installed on the endpoint itself, with events routed to output sinks or written to capture files for offline forensic analysis, and it can be extended with Python-based filaments for custom tooling. That places it in the hands of detection engineers 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 who write and tune behavioral rules rather than rely solely on signature-based antivirus, and it ships with 50-plus curated detection rules covering privilege escalationprivilege escalationGaining permissions beyond those an account or process initially had. It can turn limited access into administrator control or access to another user's resources., defense evasion, and execution tactics out of the box. The project has been active since 2016 and shows sustained development, with 205 commits and 12 releases in the past year across a dozen contributors.

Security sensor for realtime threat detection and protection

How Fibratus helps

Which process on this endpoint just tried to escalate privileges or hide its tracks?

matches live process, image, and registry events against the shipped rule set covering privilege escalation, defense evasion, and execution tactics, and names the rule and offending process

Is malware hiding shellcode or an unbacked payload in a running process's memory?

scans process memory with YARA rules and flags regions matching known malicious patterns, tying the hit back to the responsible process

Did a process reach system calls directly to slip past hooked defenses?

watches for direct and indirect syscall invocation patterns that bypass normal API monitoring and raises a detection naming the technique

Which processes escalated using a token with elevated integrity or a different user context?

enriches process events with access token details such as integrity level and elevation type, so a rule can catch tokens that don't match the parent's privilege level

What actually happened on this host during an incident, step by step, after the fact?

writes the full event stream to a capture file that can be replayed and inspected offline, independent of whatever was visible at the time

Can I check whether a suspicious call chain came from a legitimate module or from injected code?

exposes callstack telemetry for memory and handle operations like allocation, process-open, and thread-open, so a rule can inspect the originating module and address for each frame

all 18 features, with the evidence for each →

Languages

Not documented

Features

18 capabilities across 4 capability groups · 2 backed by code, an API document or a real run

Built from Fibratus'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 →

  • Fibratus covers 2 of the 11 endpoint investigation and controls capabilities we track.
  • Fibratus covers 1 of the 8 investigation and response capabilities we track.
  • Fibratus covers 1 of the 3 runtime security capabilities we track.

What Fibratus offers you

  • User-defined detection rules2
  • Command-line interface1
Process telemetry 1 feature Endpoint investigation and controls since 2021
Extended event data access shipped Provides additional filter fields and parameters for thread, process, and ancestry details in kernel events. 13 releases · first seen Aug 2021

Shared capability: Process telemetry

release 13 total

  • Enriches events with process access token details including integrity level and elevation type. v3.0.0 · Apr 2026 · source · release history
  • Adds thread start address symbol and module filter fields for richer thread-origin detection. v2.4.0 · May 2025 · source · release history
  • Adds teb parameter and thread.teb_address filter field to expose Thread Environment Block address in thread events. v2.3.0 · Dec 2024 · source · release history
  • kevt.arg filter field extracts arbitrary event parameters by internal name v1.10.0 · Mar 2023 · source · release history
  • process.uuid filter field provides a repetition-resistant identifier for processes v1.10.0 · Mar 2023 · source · release history
  • handle events include Driver image path enrichment for driver object types v1.8.0 · Nov 2022 · source · release history
Host network isolation 1 feature Endpoint investigation and controls since 2025
Host isolation action shipped Allows rules to trigger a host isolation action when a detection condition is met. 1 release · first seen May 2025

Shared capability: Host network isolation

release

  • New isolate rule action for isolating a host when a rule fires. v2.4.0 · May 2025 · source · release history
Threat indicator matching 1 feature Investigation and response since 2021
Complex filter logic and function support shipped Enables the use of CIDR containment, MD5 hashing, fuzzy string matching, and unary logical operators within event filters. 4 releases · first seen Apr 2021

Shared capability: Threat indicator matching

release

  • Enables bare boolean expressions in filters for more flexible event querying v2.0.0 · Sep 2023 · source · release history
  • Adds fuzzy matching operators (ifuzzy, fuzzynorm, nifuzzy) for string filters. v1.4.0 · Aug 2021 · source · release history
  • Adds cidr_contains and md5 function support in filters v1.2.0 · Apr 2021 · source · release history
  • Adds unary not operator to filters v1.2.0 · Apr 2021 · source · release history
Runtime threat detection 1 feature Runtime security since 2022
Stateful runtime detection shipped Enables the definition and execution of rules that track state across multiple events to perform temporal correlation. 2 releases · 1 other source · first seen Aug 2022

Shared capability: Runtime threat detection

Also counts toward: User-defined detection rules

release

  • New configuration flag permits disabling the rule engine entirely. v2.2.0 · Sep 2024 · source · release history
  • stateful-event-tracking in rules allows new stateful runtime detections. v1.6.0 · Aug 2022 · source · release history

example

  • Write a rule using the new stateful event tracking feature to correlate events over time. # Rule definition example name: MyStatefulRule type: stateful-event-tracking ... v1.6.0 · Aug 2022 · source
Other / not yet classified 14 features Features we have not matched to a capability yet. A suggested match is marked.
Detection rule authoring and validation verified Allows users to write, validate, and manage detection rules for structural and syntactic correctness. 28 releases · 3 other sources · first seen Aug 2021

Also counts toward: User-defined detection rules

release 28 total

  • Adds 11 new detection rules covering lateral movement, defense evasion, credential access, and suspicious DLL-loading techniques — including 'Untrusted DLL loaded from masqueraded Windows directory', Suspicious LSASS process access, 'Potential privilege elevation via arbitrary section creation', 'CldApi DLL loaded… v3.1.0 · Aug 2026 · source · release history
  • Adds 24 new built-in detection rules covering LSASS dumping, ClickFix infection chains, DLL side-loading, shellcode via ETW, WMI abuse from Office, Windows Defender tampering, suspicious print processors, Vault client DLL loads, XSL/HTA script execution, and more. v2.4.0 · May 2025 · source · release history
  • New foreach function for iterating over pseudo fields such as ps._ancestors, ps._modules, and pe._sections in rule conditions. v2.4.0 · May 2025 · source · release history
  • ps.modules field has been removed; use the foreach function with ps._modules to evaluate module attributes. v2.4.0 · May 2025 · source · release history
  • registry.key, image.name, and file.name now yield only the base name. Use registry.path, image.path, or file.path to obtain the full path. v2.4.0 · May 2025 · source · release history
  • ps.pe.sections field has been removed; use the foreach function with pe._sections to evaluate section attributes. v2.4.0 · May 2025 · source · release history

command line

  • validate — Validate rules for structural and syntactic correctness v2.2.0 · Sep 2024 · command-line history

example

  • Use foreach with ps._ancestors to check any ancestor process name, replacing the removed ps.ancestor indexed lookups for multi-level chain detection. fibratus run --filter "foreach(ps._ancestors, $a, $a.name = 'winword.exe')" v2.4.0 · May 2025 · source
  • List every rule currently loaded by Fibratus to audit your active detection coverage. fibratus rules list v2.2.0 · Sep 2024 · source
Smart event filtering with approvers shipped suggested Dynamically evaluates and discards events before they reach the full processing pipeline, reducing processing volume while retaining detection-relevant events. 9 releases · 2 other sources · first seen Nov 2016

Suggested capability: Process telemetry. This is our guess, not confirmed.

Also counts toward: Command-line interface

release 9 total

  • Delivers filtering and approver pipeline performance improvements including pattern precompilation, path string interning, object pooling, cached filter values, and more efficient wildcard matching. v3.1.0 · Aug 2026 · source · release history
  • Adds smart event filtering with approvers, dynamically evaluating and discarding events before they propagate through the full processing pipeline to substantially reduce processing volume while preserving detection-relevant events. v3.1.0 · Aug 2026 · source · release history
  • Introduces smart event filtering with approvers that dynamically evaluate and discard events before they propagate through the full processing pipeline, substantially reducing processed event volume while preserving detection-relevant events. v3.1.0 · Aug 2026 · source · release history
  • Adds additional file filter fields for finer-grained file event filtering. v2.3.0 · Dec 2024 · source · release history
  • Adds dip.names, sip.names, and file.extension filter fields v1.2.0 · Apr 2021 · source · release history
  • Adds matches and imatches string matching operators v1.2.0 · Apr 2021 · source · release history

example

  • Use string matching operators to filter events based on file extension or process name. matches(file.extension, '*.exe') and imatches(process.name, 'cmd') v1.2.0 · Apr 2021 · source
  • Negate a condition using the new unary operator to exclude specific traffic. not matches(dip.names, '10.0.0.0/8') v1.2.0 · Apr 2021 · source
Advanced filter functions and operators shipped Extends the rule engine with new capabilities such as case-insensitive string comparison, minidump signature checking, and decimal-based object parameter parsing. 10 releases · first seen Nov 2022

release 10 total

  • New isolate rule action for isolating a host when a rule fires. v2.4.0 · May 2025 · source · release history
  • New intersects operator for filter expressions to check set intersection between field values. v2.4.0 · May 2025 · source · release history
  • Introduces match-all rule engine strategy to evaluate every matching rule rather than stopping at the first match. v2.4.0 · May 2025 · source · release history
  • Extends substr function with an optional argument for more flexible string slicing in filter expressions. v2.4.0 · May 2025 · source · release history
  • Adds image.is_dotnet filter field to detect .NET image loads in filter expressions. v2.3.0 · Dec 2024 · source · release history
  • Adds option to disable CLR metadata parsing. v2.3.0 · Dec 2024 · source · release history
Kernel event stream collection shipped suggested Captures high-performance kernel events with GIL-free processing. 9 releases · first seen Jan 2017

Suggested capability: Process telemetry. This is our guess, not confirmed.

release 9 total

  • System providers support runs specific providers in separate tracing sessions. v2.2.0 · Sep 2024 · source · release history
  • Dynamic event enablement inspects the loaded rule set and activates only required kernel event providers. v2.2.0 · Sep 2024 · source · release history
  • Event forwarding mode allows Fibratus to run as a pure forwarder without local rule evaluation. v2.2.0 · Sep 2024 · source · release history
  • New NTFS parser reads file data via raw device access, bypassing standard I/O. v2.2.0 · Sep 2024 · source · release history
  • Adds VirtualAlloc and VirtualFree kernel events to track memory allocation activity v2.0.0 · Sep 2023 · source · release history
  • Adds MapViewFile and UnmapViewFile kernel events plus mapped-files state for tracking file mappings v2.0.0 · Sep 2023 · source · release history
Event type discovery verified Lists the event types supported by the tool for use in rules and filtering. 6 releases · 1 other source · first seen Nov 2016

release

  • Adds CreateSymbolicLinkObject event type for detecting object-level symbolic link creation. v2.4.0 · May 2025 · source · release history
  • Adds DuplicateHandle event to detect handle duplication across processes v2.0.0 · Sep 2023 · source · release history
  • Adds DNS telemetry via QueryDns and ReplyDns events for monitoring DNS queries and responses v2.0.0 · Sep 2023 · source · release history
  • OpenProcess and OpenThread events are now available for tracking process and thread handle operations v1.5.0 · Apr 2022 · source · release history
  • Adds image_meta registry providing PE headers, sections, imports, and file information v0.6.0 · Jan 2017 · source · release history
  • Adds ElasticSearch output adapter v0.4.0 · Nov 2016 · source · release history

command line

Execution argument passing shipped Allows configuration of arguments passed to filaments during their execution. 6 releases · 1 other source · first seen Aug 2021

release

  • Adds an Eventlog alert sender so rule detections can be forwarded directly to the Windows Event Log. v2.3.0 · Dec 2024 · source · release history
  • Adds alert identifier to alert payloads. v2.3.0 · Dec 2024 · source · release history
  • Command line parameters and filter fields contain the original, unexpanded command line v2.0.0 · Sep 2023 · source · release history
  • New http output supports sending traces over HTTP v1.5.0 · Apr 2022 · source · release history
  • New eventlog output allows writing traces to the Windows Event Log v1.5.0 · Apr 2022 · source · release history
  • Enables passing arguments to filaments during execution. v1.4.0 · Aug 2021 · source · release history

example

  • Write a rule using the new stateful event tracking feature to correlate events over time. # Rule definition example name: MyStatefulRule type: stateful-event-tracking ... v1.6.0 · Aug 2022 · source
Digital signature verification shipped Verifies digital signatures on files or processes, with async verification, caching, and metadata-store initialization. 5 releases · first seen Sep 2023

release

  • Overhauls the digital signature verification pipeline with asynchronous verification, better cache keying, eager metadata-store initialization, and more robust handling of freshly added signatures. v3.1.0 · Aug 2026 · source · release history
  • Overhauled the digital signature verification pipeline with improved async verification, better cache keying, eager metadata-store initialization, and more robust handling of freshly added signatures. v3.1.0 · Aug 2026 · source · release history
  • Revamps the YARA scanner with restructured configuration. v2.3.0 · Dec 2024 · source · release history
  • YARA configuration settings were restructured and some properties were removed — existing YARA config blocks must be updated to match the new layout. v2.3.0 · Dec 2024 · source · release history
  • Exposes image signature information through image.signature.type and image.signature.level filter fields v2.0.0 · Sep 2023 · source · release history
Kernel thread callstack analysis shipped Resolves kernel return addresses to driver modules and stitches callstack data to events via timestamps, enabling callstack-based filtering and detection. 5 releases · first seen Sep 2024

release

  • Introduces a kernel thread callstack summary filter field, resolving kernel return addresses to their corresponding driver modules and stitching callstack data to events via timestamps for more reliable callstack-based filtering and detection. v3.1.0 · Aug 2026 · source · release history
  • Adds callstack telemetry for VirtualAlloc, OpenProcess, and OpenThread events, enabling stack-aware detection of memory and handle abuse. v2.4.0 · May 2025 · source · release history
  • Adds additional callstack filter fields for deeper stack inspection in rules. v2.4.0 · May 2025 · source · release history
  • Kernel stack enrichment annotates process, file, thread, registry, and DLL events with call stack frames. v2.2.0 · Sep 2024 · source · release history
  • New callstack filter fields for writing rules that inspect kernel/user-mode call stacks. v2.2.0 · Sep 2024 · source · release history
Curated detection rules library shipped Provides a collection of pre-authored detection rules covering common adversary tactics such as privilege escalation and defense evasion. 2 releases · 1 other source · first seen Apr 2026

release

  • Adds 11 new detection rules covering lateral movement, defense evasion, credential access, and suspicious DLL-loading techniques. v3.1.0 · Aug 2026 · source · release history
  • Ships 50+ curated detection rules covering privilege escalation, defense evasion, and execution tactics. v3.0.0 · Apr 2026 · source · release history

docs

  • Windows sensor that detects and eradicates threats by analyzing system events against a behavior-driven rule engine and YARA memory scanner.
Rule metadata injection shipped Pushes matched rule tags and YARA detection results into event metadata for downstream consumption. 2 releases · first seen Sep 2021

release

  • Injects YARA rules matches into event metadata tags v1.4.2 · Dec 2021 · source · release history
  • Pushes matched rule tags into event metadata via event.rule.metadata.tags v1.4.1 · Sep 2021 · source · release history
Kernel event type aliases shipped suggested Maps legacy kernel event identifiers to new standard names for module loading events. 1 release · first seen Apr 2026

Suggested capability: Process telemetry. This is our guess, not confirmed.

release

  • The LoadImage and UnloadImage events are renamed to LoadModule and UnloadModule. v3.0.0 · Apr 2026 · source · release history
Syscall evasion detection shipped Scans for direct and indirect syscall abuse techniques used to evade security defenses. 1 release · first seen Apr 2026

release

  • Adds direct and indirect syscall evasion scanners to detect malware bypassing defenses via syscall abuse. v3.0.0 · Apr 2026 · source · release history
Windows Event Log alerting shipped Emits structured JSON alerts to the Windows Event Log for SIEM and log pipeline integration. 1 release · first seen Apr 2026

release

  • Supports emitting alerts to the Windows Event Log in structured JSON format for SIEM and log pipeline integration. v3.0.0 · Apr 2026 · source · release history
Thread pool telemetry shipped Captures thread pool event telemetry and exposes corresponding filter fields. 1 release · first seen May 2025

release

  • Incorporates thread pool event telemetry and exposes corresponding thread pool filter fields. v2.4.0 · May 2025 · 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 Fibratus, 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 Fibratus 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

17 entries

  1. August 20261
  2. April 20261
  3. May 20251
  4. December 20241
  5. September 20242
  6. September 20231
  7. March 20231
  8. November 20221
  9. August 20221
  10. April 20221
  11. December 20211
  12. September 20211
  13. August 20211
  14. April 20211
  15. January 20171
  16. November 20161
    Show

    17 entries

    Project health

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

    1. Contributors 1 −3 vs prior 12 months
    2. Maintainers 1 +0 joined · −0 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 31% of issues opened, last 12 months
    5. Median time to close 3.4 days first maintainer reply 8.3 hours
    6. Open backlog 35 of 101 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 35
    3. Contributors / month 1
    4. Commits / month 7
    5. Stars 2,547
    Issue themes, last 12 months
    • bugs 6%
    • features 56%
    • other 38%

    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 →