gitwtfhub

wtf is furtex?

matheuzsecurity/furtex — explained in plain English

Analysis updated 2026-05-18

163CAudience · researcherComplexity · 5/5Setup · hard

TL;DR

A Linux security research toolkit with 75+ tools for bypassing detection software during authorized red team testing. Uses kernel technologies to skip normal monitoring paths that security programs watch.

Mindmap

mindmap
  root((Furtex))
    What it does
      Bypasses detection software
      Skips monitored syscalls
      Manipulates kernel security programs
    Tech stack
      C language
      io_uring
      eBPF
      libbpf
    Categories
      io_uring tools
      bpf tools
      edrs evasion tools
      techniques folder
    Use cases
      Authorized red team testing
      Security research
      Detection bypass testing
    Requirements
      gcc and clang
      kernel headers
      Linux capabilities
    Audience
      Security researchers
      Red team operators
      Linux kernel experts

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Test your own Linux systems against detection bypass techniques during authorized red team engagements.

REASON 2

Research how io_uring and eBPF can be used to evade endpoint detection software.

REASON 3

Evaluate whether your Falco security rules catch the bypass techniques included in this toolkit.

REASON 4

Study how kernel-level tools manipulate BPF programs and maps for security research.

What's in the stack?

Cio_uringeBPFlibbpfgccclangmake

How it stacks up

matheuzsecurity/furtexgvanrossum/abc-unixatc1441/zbs_flasher
Stars163170171
LanguageCCC
Last pushed2024-07-17
MaintenanceDormant
Setup difficultyhardhardhard
Complexity5/55/54/5
Audienceresearcherresearchervibe coder

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · hard Time to first run · 1day+

Requires gcc, clang, make, kernel headers, libbpf-dev, specific Linux capabilities like CAP_BPF, and kernel 5.19+ for full functionality.

The explanation does not mention a license, so the terms of use are unknown.

Wtf does this do

Furtex is a post-exploitation and evasion research toolkit for Linux, built for red team engagements and authorized security research. The project provides a large collection of tools, 75 in the EDR evasion directory alone, organized into several categories. The authors stress that it should only be run on systems you own or have explicit permission to test. The toolkit is written in C and uses two Linux kernel technologies: io_uring and eBPF. The README does not explain these in detail, but the core idea is that io_uring handles input and output through a kernel workqueue, which lets the tools skip the normal syscall path that security software monitors. This design alone bypasses several common monitoring hooks without any extra effort. eBPF, meanwhile, lets the tools inspect and manipulate kernel-level security programs directly. The repository is split into five directories. The io_uring folder holds 13 tools for file, network, process injection, and data exfiltration operations. The bpf folder contains 15 tools for listing, dumping, writing to, and detaching BPF maps and programs. The ebpf folder holds BPF-side programs and loaders, while edrs contains the bulk of the toolkit with 75 tools for evading endpoint detection and response software. A techniques folder covers bypasses for Falco, a specific Linux security tool, with 13 tools targeting its default rules. Building the toolkit requires gcc, clang, make, kernel headers, and libbpf development files. Different kernel versions unlock different capabilities, with 5.19 needed for the full set of io_uring network operations. Many tools also require specific Linux capabilities, such as CAP_BPF for BPF tools or CAP_NET_RAW for raw network operations. The README is detailed about requirements and bypass coverage but does not explain what each evasion technique does at a high level. It assumes the reader already understands Linux security internals, kernel hooks, and EDR architecture. Beginners will find the command examples useful but will need outside references to understand why these techniques work.

Yoink these prompts

Prompt 1
I want to understand how the Furtex toolkit uses io_uring to bypass Linux security monitoring. Walk me through what io_uring does and why skipping the normal syscall path matters for evasion, explained for someone who knows basic Linux but not kernel internals.
Prompt 2
Help me set up a safe authorized testing environment to run Furtex evasion tools against my own Linux server. What Linux kernel version, packages, and capabilities do I need installed, and how do I verify they are present before running any tools?
Prompt 3
I have Furtex built and want to test which of my Falco security rules catch the 13 bypass techniques in the techniques folder. Help me design a testing plan that runs each technique one at a time and records whether Falco alerts on it.
Prompt 4
Explain the difference between the bpf folder tools and the ebpf folder tools in Furtex, and give me a plain-English breakdown of what listing, dumping, writing to, and detaching BPF maps actually means in a security context.
Prompt 5
I want to use Furtex as a learning resource for Linux kernel security. Suggest a study order for the five tool categories that starts with the most foundational concepts and builds up to the advanced evasion techniques.

Frequently asked questions

wtf is furtex?

A Linux security research toolkit with 75+ tools for bypassing detection software during authorized red team testing. Uses kernel technologies to skip normal monitoring paths that security programs watch.

What language is furtex written in?

Mainly C. The stack also includes C, io_uring, eBPF.

What license does furtex use?

The explanation does not mention a license, so the terms of use are unknown.

How hard is furtex to set up?

Setup difficulty is rated hard, with roughly 1day+ to a first successful run.

Who is furtex for?

Mainly researcher.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.