Skip to content
KitploitKITPLOIT
FerramentasExploitsBlog
Log in
Enviar
FerramentasExploitsBlog
Enviar

Ferramentas de Hacking, PenTest e Cibersegurança para o seu Arsenal de Segurança!

Kitploit é um diretório de ferramentas de hacking, cibersegurança e pentesting. Descubra as últimas atualizações de projetos para encontrar vulnerabilidades, analisar sistemas, automatizar testes e fortalecer sua segurança.

FeedsContatoPrivacidade© 2026 Kitploit

Diretório de Ferramentas

Categorias

Ver todas as categorias
Loading categories
wstrace — Standalone zero-driver Windows system and API monitor in Rust | Kitploit
Ferramentas/GitHubGitHub/gilnett/wstrace
Defensive ToolsDynamic Analysis (Sandboxing)Reverse EngineeringDebuggersForensicsInformation GatheringMalware AnalysisBinary AnalysisIncident ResponseLog Analysis
GitHubgilnett/wstrace

wstrace

Standalone zero-driver Windows system and API monitor in Rust

Ver Repositório
242120há 9h 56mRevisado pelo Kitploit

Mais Populares

Ver todos →

Descubra as ferramentas mais usadas pela nossa comunidade.

Explore todas as ferramentas

Navegue pela nossa coleção de ferramentas

Ver todas as ferramentas →
Compartilhar
Conteúdo não disponível no idioma solicitado. Mostrando versão em inglês.

wstrace logo

wstrace

High-performance zero-driver Windows system and API monitor in Rust.

License: GPL-3.0 GitHub Sponsors Ko-fi

Modern strace and real-time Process Monitor for Windows. Built in native Rust with zero kernel drivers required, featuring a real-time terminal user interface (TUI) and unbuffered streaming for headless diagnostics.


Architectural FAQ

Why zero kernel drivers?

Third-party kernel drivers (.sys) risk system crashes (BSOD), expand the attack surface, and require driver-signing exemptions prohibited in enterprise environments. wstrace runs 100% in userland using non-invasive Win32 debugging APIs and native Windows ETW interfaces.

Why is Administrator elevation not required?

Standard user accounts can run and trace any target via wstrace run <binary>. Spawned child processes inherit debugging handles (PROCESS_ALL_ACCESS) directly without UAC prompts. Telemetry for modules, threads, sockets, and I/O relies entirely on unprivileged Win32 APIs.

Why does elevation remain a benefit if present?

Elevation is an accelerator, not a gate:

  • Standard User (Default): Complete tracing for run, attach (user session), child processes (-C), interactive TUI, and streaming.
  • Administrator: Unlocks system-wide kernel ETW and cross-session inspection (wstrace all) to monitor background OS services and system daemons.

Installation

1. PowerShell One-Liner (Zero-Clone)

Run in PowerShell to automatically install the latest release to $HOME\.local\bin and add it to your User PATH:

irm https://raw.githubusercontent.com/gilnett/wstrace/main/packaging/install.ps1 | iex

2. Scoop Package Manager

Install via the personal bucket:

scoop bucket add gilnett https://github.com/gilnett/scoop-bucket
scoop install wstrace

Or install directly via URL:

scoop install https://raw.githubusercontent.com/gilnett/wstrace/main/packaging/scoop/wstrace.json

3. Standalone Binary (GitHub Releases)

Download precompiled standalone binaries from GitHub Releases.

4. Cargo (From Source)

Install directly from GitHub:

cargo install --git https://github.com/gilnett/wstrace.git

Or build locally from a cloned repository:

cargo build --release

The resulting binary is located at target\release\wstrace.exe.

4. Package Managers (Winget & Scoop)

[!NOTE] Winget and Scoop manifests are synchronized automatically with published GitHub Releases.

Windows Package Manager (Winget)

[!NOTE] The official package submission is currently undergoing review and verification on microsoft/winget-pkgs. Once approved and merged by community moderators, it will be installable directly via:

winget install gilnett.wstrace

Scoop

scoop install .\packaging\scoop\wstrace.json

Architecture

flowchart LR
    CLI["CLI Engine<br/><code>run | attach | all</code>"] --> PROBES

    subgraph PROBES["Zero-Driver Probes"]
        W32["Win32 Debug API<br/>(Proc, Threads, DLLs)"]
        NET["IP Helper API<br/>(TCP/UDP Sockets)"]
        ETW["Native ETW<br/>(I/O, Registry)"]
    end

    W32 & NET & ETW -->|TraceEvent| BUS["Lock-Free Bus<br/><code>crossbeam</code>"]

    BUS --> TUI["TUI View<br/>(ratatui)"]
    BUS --> STREAM["Stream View<br/>(stdout)"]

    TUI & STREAM --> OUT["Sinks<br/>(Console, JSON, Clipboard)"]

Quickstart & Usage

1. Verification

Confirm that wstrace is accessible in the current shell:

wstrace --version

2. Trace an Application (Interactive TUI)

Launch a target executable with real-time Win32 and system telemetry:

wstrace run <executable_path> [-- <arguments>...]

TUI Keyboard Controls

KeyActionDescription
Ctrl+CCopy SelectedCopies the highlighted event details into the Windows clipboard.
Ctrl+ACopy AllCopies all currently filtered events into the Windows clipboard.
Ctrl+E / SpacePause / ResumeFreezes the event view without dropping incoming telemetry.
Ctrl+XClear BufferEmpties the current event list from the display buffer.
TabCategory CycleFilters events: ALL -> FILE -> REG -> NET -> PROC.
fFailures OnlyRestricts view to failed operations (e.g. access denied, not found).
Up / DownNavigationSelects an event for deep inspection.
q / EscExitTerminates the tracing session cleanly.

3. Trace All System-Wide Activity

Monitor active processes, new spawns, exits, and loaded modules system-wide in real time:

wstrace all

4. Attach to a Running Process

Attach to an existing process by PID or binary name without restarting it:

# Attach by PID
wstrace attach -p <PID>

# Attach by process name
wstrace attach -n <process_name.exe>

5. Headless Stream Mode (CI/CD & Logging)

Writes live events directly to stdout with ANSI color codes:

wstrace -m stream [-d <seconds>] run <executable_path>

Comprehensive Manual & Advanced Options: For advanced path filtering (--include / --exclude), child tracking (-C), JSON reports (--export-json), clipboard exports (--copy), and scripting options, consult the CLI Reference Manual or run wstrace --help.


Architecture & Compatibility

  • Core Engine: Rust (2021 Edition)
  • Installer & Deployment: PowerShell (packaging/install.ps1)
  • Terminal UI: Ratatui + Crossterm
  • Telemetry Ingestion: Win32 APIs (ToolHelp32Snapshot, OpenProcess, VirtualQueryEx) & Event Tracing for Windows (ETW).
  • Target Architectures:
    • x86_64-pc-windows-msvc (Intel / AMD 64-bit)
    • aarch64-pc-windows-msvc (Qualcomm Snapdragon X / Windows on ARM)

Enterprise Compliance & Institutional Governance

wstrace is engineered to meet strict institutional requirements for deployment in high-security enterprise environments (banking, defense, healthcare, and critical infrastructure):

1. Zero Cloud Data Leakage (Air-Gapped & Sovereign)

wstrace is 100% offline and standalone. It maintains zero remote servers, initiates zero telemetry or analytics, and performs zero outbound network calls. Any sensitive data observed during live tracing (API tokens, file paths, credentials, memory contents) remains strictly confined to local RAM and never leaves the workstation.

2. Zero Kernel Drivers (Zero Ring-0 Footprint)

Unlike traditional tracing utilities that install third-party .sys kernel drivers—introducing system crash risks (Blue Screen of Death / BSOD) and ring-0 backdoor attack surfaces—wstrace operates with zero kernel drivers. It relies exclusively on non-invasive userland Win32 debugging and native Windows Kernel ETW consumer interfaces.

Baixar ferramenta