
Kernel-mode process terminator using a signed BYOVD driver. Works on all Windows 10/11. No offsets, no PDB. Rust.
Cross-version Windows process termination from kernel context.
One signed driver. One IOCTL. No offsets. No PDB.
A cross-version Windows process terminator. It loads a signed HONOR
kernel driver (MonProcessEX.sys), resolves the PID of every target
process, and terminates it from kernel context through a single IOCTL.
No kernel offsets, no PDB downloads, no build-specific shellcode - the
technique works identically on every Windows 10 and Windows 11 build.
The tool is a single self-contained executable. When it needs the driver,
it installs it through the Service Control Manager, performs the kill, and
stops and deletes the temporary service before exiting. If MonProcessEX.sys
is already loaded, it reuses the existing driver and leaves it in place.
Targets are configurable at runtime through a config file, command line, or
the built-in defaults.
Cross-version by design. One driver, one IOCTL, one kill primitive. Works on all Windows 10 and Windows 11 builds.
1. Keep moncrush.exe and MonProcessEX.sys in the same folder.
2. Run from an elevated shell.
moncrush.exe -n "notepad.exe,calc.exe"
3. Targets die. The temporary driver service is cleaned up. Done.
No toolchain, no offsets, no build step.
| Feature | Details |
|---|---|
| Cross-version | Works on all Windows 10 and Windows 11 builds, no offsets |
| Kernel-mode kill | Driver terminates the PID from kernel context |
| PPL bypass | MonProcessEX.sys kill path bypasses protected-process checks |
| Signed driver | MonProcessEX.sys is a real signed HONOR driver |
| Not in MS block rules | Absent from Microsoft's vulnerable-driver block rules |
| Self-sufficient | Temporary driver installed, started, and cleaned up via SCM; a preloaded driver is reused as-is |
| Zero dependencies | Static Rust binary; drop exe + driver, run |
| Configurable | targets.conf or -n, no recompile needed |
| Obfuscated | Device path and target list encrypted at rest |
| Single executable | One binary; console output from a shell, silent when double-clicked |
| Dry-run mode | Enumerate targets and PIDs before committing |
| Jittered loop | --repeat re-checks with randomized interval |
| Exit codes + JSON | C2-friendly automation interface |
+-------------------------------------------------------------------------------------------+
| USER MODE |
| |
| moncrush.exe |
| |
| +-------------------+ +-------------------+ +---------------------+ |
| | enumerate all | | resolve target | | match against | |
| | running | -> | PID via process | -> | target list, | |
| | processes | | entry | | collect PIDs | |
| +-------------------+ +-------------------+ +----------+----------+ |
| | |
| CreateFileW("\.\MonProcessEX") | |
| DeviceIoControl(IOCTL 0x22400C) | |
| output = termination status v |
+-------------------------------------------------------------------------------------------+
| KERNEL MODE |
| |
| MonProcessEX.sys signed HONOR kernel driver |
| +---------------------------------------------------------------------------------+ |
| | | |
| | IOCTL 0x22400C -> PID termination dispatch | |
| | | | |
| | | kernel-mode process lookup | |
| | v | |
| | EPROCESS located -> terminated from kernel context | |
| | | | |
| | v | |
| | process exit path invoked | |
| | | |
| +---------------------------------------------------------------------------------+ |
| |
| CLEANUP |
| +---------------------------------------------------------------------------------+ |
| | temporary service stopped + deleted (when this run created it) | |
| | preloaded driver reused as-is; never force-unloaded | |
| +---------------------------------------------------------------------------------+ |
+-------------------------------------------------------------------------------------------+
The driver exposes a kill IOCTL that terminates a process given its PID. The user-mode component enumerates running processes, resolves each target's PID, and submits it through the device interface. No kernel structures are touched from user mode, so the technique is immune to Windows version changes.
cargo build --release --target x86_64-pc-windows-gnu