wraith-rs
Safe, idiomatic Rust abstractions for Windows process internals and security research.
What is wraith-rs?
wraith-rs provides high-level APIs for interacting with Windows internals that are typically only accessible through undocumented structures and techniques. It's designed for security researchers, anti-cheat developers, and anyone who needs to understand or manipulate Windows processes at a low level.
use ;
use ModuleQuery;
// Access process internals without raw pointers
let peb = current?;
let teb = current?;
println!;
println!;
// Find and inspect loaded modules
let query = new;
let ntdll = query.find_by_name?;
let nt_open_process = ntdll.get_export?;
Features
Core Navigation
- PEB/TEB Access: Safe wrappers around Process/Thread Environment Blocks with version-aware field offsets (Windows 7 through Windows 11 24H2)
- Module Enumeration: Iterate loaded modules via all three PEB lists (InLoadOrder, InMemoryOrder, InInitializationOrder)
- Export Resolution: Find exported functions by name, ordinal, or hash
- Memory Region Queries: Enumerate process memory regions with protection info
- Thread Enumeration: List threads in the current process
- Pattern Scanning: Scan memory for byte patterns with wildcard support (IDA-style signatures)
Advanced Manipulation
| Feature | Description |
|---|---|
| Module Unlinking | Remove modules from PEB lists (hide from GetModuleHandle, EnumProcessModules) |
| Manual PE Mapping | Load DLLs without LoadLibrary - invisible to module enumeration |
| Direct Syscalls | Invoke syscalls directly via syscall instruction, bypassing usermode hooks |
| Indirect Syscalls | Jump to ntdll's syscall instruction for cleaner call stacks |
| Spoofed Syscalls | Return address spoofing, stack frame synthesis, gadget-based indirection |
| Hook Detection | Detect inline hooks (jmp, mov/jmp, push/ret, int3) in loaded modules |
| Hook Removal | Restore hooked functions using clean copies from disk |
| Inline Hooking | Install detour hooks on functions with automatic trampoline generation |
| Anti-Debug | Manipulate PEB.BeingDebugged, NtGlobalFlag, heap flags, hide threads |
| Remote Process | Cross-process memory read/write, module enumeration, thread creation, injection |
Comparison with Other Libraries
| Feature | wraith-rs | ntapi | windows-sys | pelite |
|---|---|---|---|---|
| PEB/TEB access | Safe wrappers | Raw FFI | Not covered | No |
| Version-aware offsets | Win7-Win11 | Manual | N/A | N/A |
| Module enumeration | Iterator API | Manual | Manual | No |
| Pattern scanning | Module + region scanning | No | No | No |
| Module unlinking | Built-in | Manual | No | No |
| Manual PE mapping | Full pipeline | No | No | Parse only |
| Syscall invocation | Direct + Indirect + Spoofed | No | No | No |
| Hook detection | Pattern + disk comparison | No | No | No |
| Remote process ops | Full (read/write/inject) | Manual | Manual | No |
| Zero dependencies* | Yes | Yes | Yes | Yes |
*Core functionality has no required dependencies. Optional log integration available.
Why not just use ntapi/windows-sys?
Those are FFI bindings - they give you the raw function signatures. wraith-rs builds on top of those concepts to provide:
- Safety: No raw pointer juggling. Bounds checking on PE parsing. Validation on all inputs.
- Ergonomics: Iterator patterns, builder APIs, proper error types.
- Portability: Version-aware offsets mean code works across Windows versions without
#[cfg]everywhere. - Completeness: Full workflows (parse PE → allocate → map → relocate → resolve imports → call entry point) not just primitives.
Installation
[]
= "0.1"
Or with specific features:
[]
= { = "0.1", = ["full"] }
Feature Flags
[]
= ["navigation", "unlink"]
= [] # Module/thread enumeration, memory queries
= ["navigation"] # Module unlinking from PEB lists
= ["navigation"] # Manual PE mapping (LoadLibrary bypass)
= ["navigation"] # Direct/indirect syscall invocation
= ["syscalls"] # Return address spoofing, gadget finding, stack synthesis
= ["syscalls", "manual-map"] # Hook detection and removal
= ["hooks"] # Inline hooking framework for function interception
= [] # Anti-debugging techniques
= ["syscalls"] # Cross-process operations and injection
= ["navigation", "unlink", "manual-map", "syscalls", "spoof", "hooks", "inline-hook", "antidebug", "remote"]
Usage Examples
Module Enumeration
use Peb;
use ;
let peb = current?;
for module in new?
Pattern Scanning
use ;
// Scan a module for an IDA-style pattern
let matches = find_pattern_in_module?;
for m in &matches
// Use the Scanner builder for more control
let scanner = new?
.alignment // check every byte (default)
.max_results; // limit results
// Scan a specific module
let peb = current?;
let query = new;
let ntdll = query.find_by_name?;
let calls = scanner.scan_module?;
println!;
// Scan all executable memory regions
let results = scanner.scan_executable_regions?;
// Code-style pattern (bytes + mask)
let pattern = from_code?;
let scanner = from_pattern;
Direct Syscalls
use ;
// Enumerate syscalls from ntdll
let table = enumerate?;
// Get NtClose
let entry = table.get.unwrap;
println!;
// Invoke directly (bypasses any usermode hooks)
let syscall = from_entry;
let status = unsafe ;
Spoofed Syscalls
use ;
// Create a spoofed syscall with default gadget-based spoofing
let syscall = new?;
// The syscall will use a jmp gadget from ntdll to make
// the return address appear legitimate
let status = unsafe ;
// Find gadgets manually for custom use
let finder = new?;
let jmp_gadgets = finder.find_jmp_rbx?;
let ret_gadgets = finder.find_ret?;
for gadget in jmp_gadgets.iter.take
// Use different spoof modes
let simple_spoof = with_config?;
// Stack synthesis for more complex scenarios
let mut spoofer = new;
spoofer.resolve_all?;
let fake_stack = spoofer.build_thread_start_stack?;
Hook Detection
use ;
// Scan common system DLLs for hooks
let hooks = scan_for_hooks?;
for hook in hooks
Manual PE Mapping
use ManualMapper;
// Map a DLL without LoadLibrary - invisible to GetModuleHandle
let mapper = from_file?
.allocate?
.map_sections?
.relocate?
.resolve_imports?
.process_tls?
.finalize?;
// Call DllMain
mapper.call_entry_point?;
// Get exports from the mapped image
let func = mapper.get_export?;
Module Unlinking
use ModuleQuery;
use unlink_module;
let peb = current?;
let query = new;
let handle = query.get_module_handle?;
// Remove from all PEB lists
let guard = unlink_module?;
// Module is now hidden from GetModuleHandle, EnumProcessModules, etc.
// Guard automatically relinks on drop, or call guard.leak() to keep hidden
Anti-Debug
use antidebug;
// Check current debug status
let status = get_debug_status?;
println!;
println!;
// Clear debug indicators
clear_being_debugged?;
clear_nt_global_flag?;
clear_heap_flags?;
// Hide current thread from debugger
hide_current_thread?;
Remote Process Operations
use ;
// Open a process with full access
let proc = open?;
// Read/write memory across process boundaries
let value: u32 = proc.read_value?;
proc.write_value?;
// Read strings from remote process
let str = proc.read_string?;
let wstr = proc.read_wstring?;
// Allocate executable memory and write shellcode
let alloc = proc.allocate_rwx?;
proc.write?;
// Create remote thread to execute
let thread = create_remote_thread?;
thread.wait_infinite?;
// Enumerate modules in remote process
let modules = enumerate_remote_modules?;
for module in &modules
// Injection methods
let result = inject_shellcode?; // CreateRemoteThread
let result = inject_via_section?; // NtMapViewOfSection
Windows Version Support
wraith-rs uses version-specific offset tables for accurate structure access:
| Windows Version | Build | Status |
|---|---|---|
| Windows 7 SP1 | 7601 | Supported |
| Windows 8.1 | 9600 | Supported |
| Windows 10 (1507-22H2) | 10240-19045 | Supported |
| Windows 11 21H2 | 22000 | Supported |
| Windows 11 22H2 | 22621 | Supported |
| Windows 11 23H2 | 22631 | Supported |
| Windows 11 24H2 | 26100 | Supported |
Unknown versions fall back to Windows 10 offsets with a warning.
Architecture Support
- x86_64: Full support
- x86 (32-bit): Supported for most features
- ARM64: Not currently supported
Safety
wraith-rs uses #![deny(unsafe_op_in_unsafe_fn)] and documents all safety invariants. The library is designed to be safe against:
- Malformed PE files: Bounds checking on all RVAs and array accesses
- Corrupted PEB lists: Iteration limits and null checks prevent infinite loops
- Invalid syscall addresses: Validation that target contains actual syscall instruction
- Buffer overflows: String reads are bounded, no unbounded loops
However, many operations are inherently unsafe at the OS level (modifying PEB, invoking syscalls, mapping executable code). The library makes these as safe as possible but cannot prevent all misuse.
Intended Use
This library is designed for:
- Security research and authorized penetration testing
- Anti-cheat and anti-tamper development
- EDR/AV development and testing
- Malware analysis and reverse engineering
- Educational purposes
Users are responsible for ensuring they have proper authorization before using these techniques on any system or software.
Contributing
Contributions are welcome! Please ensure:
- Code compiles with
cargo build --all-features - Tests pass with
cargo test --all-features - No new clippy warnings
- Unsafe code has
// SAFETY:comments explaining invariants
License
MIT License - see LICENSE for details.
wraith-rs is not affiliated with Microsoft. Windows is a trademark of Microsoft Corporation.