Curated security research, vulnerabilities, advisories and tools for practitioners.

KillerLand: Weaponized BYOVD Process Killer Collection Bypassing PPL & EDR Protections

Summary

Skip to content ## Navigation Menu Sign in Appearance settings * Platform * AI CODE CREATION * GitHub CopilotWrite better code with AI * GitHub Copilot appDirect agents from issue to merge * MCP...

Why it matters

Demonstrates how untrusted kernel IOCTL interfaces in signed OEM and vendor drivers continue to undermine Windows PPL security boundaries, enabling red teams to blind modern endpoint detection.
Published
Collected

📦 Full-Text Content Snapshot

R2 Archive · Full Article Preserved71 lines · 3.0 KB
📄 Raw .md⬇️ Download .md

Author: Jehad Abudagga (@j3h4ck) Source: github.com/redteamfortress/KillerLand

KillerLand
KillerLand

This repository is the result of hunting and reversing vulnerable signed kernel drivers for over a year. Every killer here abuses a legitimate driver to terminate any process from kernel mode, PPL-protected or not. Works on EDR/AV protected processes.

Each POC does a simple process kill by PID; you just customize it to whatever EDR process you want dead and it handles the rest from kernel. New ones get dropped as they get reversed.

All research by Jehad Abudagga (@j3h4ck).

Killers

#NameVendorSymLinkIOCTLSignerPOCDate
1libwasys.sysOPSWAT\\.\WasysControl0x22E00CMicrosoftrepo18/10/2026
2MonProcessControl.sysHONOR\\.\MonProcessControl0x22400CMicrosoftrepo18/10/2026

Loading

bash
sc create DriverName type= kernel binPath= C:\path\to\driver.sys
sc start DriverName

Running

bash
killer_poc.exe <PID>

Cleanup

bash
sc stop DriverName
sc delete DriverName

Driver Hashes

#DriverSHA256
1libwasys.sys04fda396f42384d9295fe306336ee4a685a0c341debdc27ddf9169f0336b46a6
2MonProcessControl.sys0e1cc4f205ddc6b78578de2da209ba3ba1f16fac482f4042bbd02036fc470f04

Disclaimer

Everything in this repository is published for educational and authorized security research purposes only. These tools and drivers exist to help defenders understand how BYOVD attacks work in practice so they can build better detections and block rules. Do not use any of this against systems you do not own or do not have explicit written authorization to test. The author takes no responsibility for misuse. If you use this to break something you shouldn't be touching, that's on you.

Author

Jehad Abudagga / Medium / LinkedIn / X / Telegram


📦 Full-Text Markdown Snapshot archived by Phying News · Original source: github.com/redteamfortress/KillerLand