Add Wraith: signature-free runtime exploitation detector#1
Merged
Conversation
Wraith detects exploitation in progress by verifying the provenance of every system call a monitored process makes, rather than matching known vulnerabilities or payloads. When a memory-corruption exploit finally issues a syscall, the process is in a state benign code never produces — a syscall from injected memory, a W^X page, or a pivoted stack — so the technique catches zero-days and n-days alike by behaviour. Engine (links only nix + libc): - maps.rs parse /proc/<pid>/maps into typed regions - provenance.rs classify instruction/stack pointer against the map - syscalls.rs the security-relevant syscall table - detect.rs the invariants + an exploitation-chain correlator - event.rs detection events with hand-rolled JSONL output - tracer.rs the ptrace engine (spawn/attach, syscall loop) - bin/wraith.rs the CLI sensor (run/attach, severity gating, exit codes) Ships a benign false-positive control and a self-contained exploitation-behaviour simulator; 28 unit + 4 end-to-end tests, clippy clean under -D warnings, plus CI and a demo script. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KENq7TfeeKSdusxR7iAWEa
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Wraith detects exploitation in progress by verifying the provenance of
every system call a monitored process makes, rather than matching known
vulnerabilities or payloads. When a memory-corruption exploit finally
issues a syscall, the process is in a state benign code never produces —
a syscall from injected memory, a W^X page, or a pivoted stack — so the
technique catches zero-days and n-days alike by behaviour.
Engine (links only nix + libc):
Ships a benign false-positive control and a self-contained
exploitation-behaviour simulator; 28 unit + 4 end-to-end tests, clippy
clean under -D warnings, plus CI and a demo script.
Co-Authored-By: Claude Fable 5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01KENq7TfeeKSdusxR7iAWEa