Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
0xM0nCrush — Kernel-mode process terminator using a signed BYOVD driver. Works on all Windows 10/11. No offsets, no PDB. Rust. | Kitploit
Tools/GitHubGitHub/deathshotxd/0xm0ncrush
Defensive ToolsPrivilege EscalationExploitationPost-ExploitationPenetration TestingRed TeamingPayload Development
GitHubdeathshotxd/0xm0ncrush

0xM0nCrush

Kernel-mode process terminator using a signed BYOVD driver. Works on all Windows 10/11. No offsets, no PDB. Rust.

View Repository
1162414023 days agoReviewed by Kitploit
Share

0xM0nCrush - kernel-mode process termination

Windows 10 and 11 Rust 2021 MIT license BYOVD research only GitHub stars

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.

Quick start

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.

Demo

0xM0nCrush demonstration

Features

FeatureDetails
Cross-versionWorks on all Windows 10 and Windows 11 builds, no offsets
Kernel-mode killDriver terminates the PID from kernel context
PPL bypassMonProcessEX.sys kill path bypasses protected-process checks
Signed driverMonProcessEX.sys is a real signed HONOR driver
Not in MS block rulesAbsent from Microsoft's vulnerable-driver block rules
Self-sufficientTemporary driver installed, started, and cleaned up via SCM; a preloaded driver is reused as-is
Zero dependenciesStatic Rust binary; drop exe + driver, run
Configurabletargets.conf or -n, no recompile needed
ObfuscatedDevice path and target list encrypted at rest
Single executableOne binary; console output from a shell, silent when double-clicked
Dry-run modeEnumerate targets and PIDs before committing
Jittered loop--repeat re-checks with randomized interval
Exit codes + JSONC2-friendly automation interface

How it works

+-------------------------------------------------------------------------------------------+
| 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                           |     |
|   +---------------------------------------------------------------------------------+     |
+-------------------------------------------------------------------------------------------+

0xM0nCrush kernel execution architecture

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.

Build

cargo build --release --target x86_64-pc-windows-gnu
Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    871
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    548
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    383
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    361
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    305
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    280

Explore all tools

Browse our collection of tools

View all tools →