explaingit

redteamfortress/defenderkiller

Analysis updated 2026-05-18

45C++Audience · researcherComplexity · 4/5Setup · hard

TLDR

A Windows security research tool that force-closes any process, including protected security software, by using a Microsoft-signed driver that Windows fully trusts. Built as a proof of concept for authorized security testing and education.

Mindmap

mindmap
  root((DefenderKiller))
    What it does
      Force-closes any process
      Bypasses process protection
      Evades EDR monitoring
    How it works
      Uses Microsoft-signed driver
      Operates at kernel level
      CLI with load kill unload
    Use cases
      Security product testing
      Red team assessments
      Security research education
    Audience
      Security researchers
      Red team operators
    Tech stack
      C++
      Windows kernel driver
      Command-line interface

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Test whether your security software can resist being terminated by a privileged attacker.

USE CASE 2

Research how kernel-level process termination works on Windows for educational purposes.

USE CASE 3

Validate that EDR and antivirus watchdogs properly restart after a process kill event.

USE CASE 4

Demonstrate risks of signed driver abuse in authorized red team or security assessments.

What is it built with?

C++Windows kernel driverCLI

How does it compare?

redteamfortress/defenderkillerburakcan/meshcore-mishmeshkigumotvc/cslol-manager
Stars454743
LanguageC++C++C++
Setup difficultyhardmoderateeasy
Complexity4/53/52/5
Audienceresearchergeneralgeneral

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · hard Time to first run · 1h+

Requires running on a Windows system with administrator privileges and involves loading a kernel-level driver, which may trigger security software or require specific Windows configuration.

No license is included in the repository, default copyright applies and all rights are reserved by the author.

In plain English

DefenderKiller is a security research tool written in C++ that can force-shutdown any process on a Windows computer, including ones that are normally protected from being closed. It does this by repurposing a legitimate, Microsoft-signed driver file called KSLDriver.sys, which was originally built in 2011 for Microsoft's own malware protection software. Because the driver carries Microsoft's official digital signature, Windows trusts it at the highest level and allows it to run with deep system privileges. The core idea is notable because other similar tools typically rely on drivers from third-party companies. Since this driver is signed by Microsoft itself, it is not on Microsoft's Vulnerable Driver Blocklist, a security feature meant to stop known problematic drivers. The README claims the tool currently has zero detections across seventy antivirus engines on VirusTotal. It also states that the technique bypasses Protected Process Light (PPL), a Windows mechanism designed to shield critical system and security processes, and evades certain monitoring hooks that endpoint detection and response (EDR) software relies on. The tool works through a command-line interface with three main commands: load, kill, and unload. A user first loads the Microsoft-signed driver into the system, then specifies a target process by its name or numeric identifier to terminate it, and finally unloads the driver when done. When the kill command is issued, the tool communicates with the loaded driver through a specific internal control code, instructing the Windows kernel to terminate the target process directly. Since the termination happens at the kernel level, normal security software cannot easily intercept or block it. The author notes this is a proof of concept. Some security products have watchdog services that automatically restart their processes if they are killed. The author suggests the tool could be modified to run in a loop, repeatedly targeting known security process names to prevent them from restarting. The README includes a link to a detailed blog post on Medium covering the reverse engineering and technical breakdown of the driver. The project is framed for authorized security testing and educational purposes only, with a disclaimer that users should only run it on systems they own or have explicit permission to test.

Copy-paste prompts

Prompt 1
Help me understand the security implications of a Microsoft-signed driver being repurposed to kill protected processes on Windows. What makes this different from using third-party drivers?
Prompt 2
I want to test my endpoint security product's resilience. Can DefenderKiller be used to verify whether my antivirus watchdog properly restarts after its process is killed? Walk me through the load, kill, and unload workflow.
Prompt 3
Explain how Windows Protected Process Light PPL works and why a kernel-level driver signed by Microsoft can bypass it. What should security teams do to defend against this kind of technique?
Prompt 4
I am building a detection rule for my EDR. What indicators of compromise should I look for when a legitimate Microsoft-signed driver like KSLDriver.sys is loaded and used to terminate security processes?

Frequently asked questions

What is defenderkiller?

A Windows security research tool that force-closes any process, including protected security software, by using a Microsoft-signed driver that Windows fully trusts. Built as a proof of concept for authorized security testing and education.

What language is defenderkiller written in?

Mainly C++. The stack also includes C++, Windows kernel driver, CLI.

What license does defenderkiller use?

No license is included in the repository, default copyright applies and all rights are reserved by the author.

How hard is defenderkiller to set up?

Setup difficulty is rated hard, with roughly 1h+ to a first successful run.

Who is defenderkiller for?

Mainly researcher.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.