ThreatBeaconXSubscribe
HighVulnerability Research & Defense Evasion · 5 min read

KillerLand Exposes the Risks of Vulnerable Signed Drivers Used to Terminate EDR-Protected Processes

KillerLand is an open-source security research repository documenting vulnerable, signed Windows kernel drivers that can be abused to terminate processes, including those protected by endpoint detection and response (EDR) and antivirus software. The research highlights the risks associated with Bring Your Own Vulnerable Driver (BYOVD) techniques, where attackers exploit trusted drivers to undermine endpoint security controls.

Written by Jakka Lakshmi Koumudi·Published Oct 25, 2026


1. Description

Endpoint security solutions rely on processes and protective mechanisms to detect, investigate, and respond to malicious activity. However, attackers may attempt to weaken these defenses by abusing vulnerable kernel-mode drivers that have legitimate digital signatures.

The KillerLand repository, maintained by security researcher Jehad Abudagga, documents research into this technique. It identifies two drivers—libwasys.sys, associated with OPSWAT, and MonProcessControl.sys, associated with HONOR—as research examples of drivers weaponized to terminate processes from kernel mode.

The repository states that its research focuses on processes protected by endpoint security products, including EDR and antivirus solutions. It is a demonstration of a potential attack technique, not by itself evidence that these drivers have been used in a confirmed real-world campaign.

2. Technical Description

Bring Your Own Vulnerable Driver (BYOVD) is a technique in which an attacker introduces or abuses a legitimate but vulnerable signed driver to gain access to privileged kernel-level operations.

Windows kernel drivers operate with high privileges, making driver vulnerabilities particularly significant. If an attacker can load and abuse a vulnerable driver, the resulting kernel-level capabilities may be used to interfere with security software or other protected processes.

KillerLand documents two examples:

  • libwasys.sys — associated with OPSWAT.

  • MonProcessControl.sys — associated with HONOR.

The repository lists Microsoft as the signer for both drivers. A valid signature establishes information about a driver's signing status; it does not guarantee that the driver is free from vulnerabilities or unsafe behavior.

3. Attack Overview

A potential BYOVD attack involving process termination may follow this general sequence:

  1. Driver introduction: An attacker obtains access to a vulnerable signed driver on a target system.

  2. Driver loading: The driver is loaded if system security policies permit it.

  3. Kernel-level abuse: The attacker exploits the driver's functionality or vulnerability to perform privileged operations.

  4. Security process termination: The capability may be used to terminate EDR, antivirus, or other protected processes.

  5. Reduced defensive visibility: If security controls are disrupted, subsequent malicious activity may become more difficult to detect or investigate.

This sequence describes the general technique. The repository demonstrates research into process termination; it does not establish that every stage occurred in an actual intrusion.

4. Technical Analysis

KillerLand documents a collection of reversed drivers and proof-of-concept research intended to demonstrate how vulnerable signed drivers can be abused to terminate processes from kernel mode.

The repository lists the following drivers, both dated 18 October 2026:

  • libwasys.sys — OPSWAT-associated driver.

  • MonProcessControl.sys — HONOR-associated driver.

The research is significant because kernel-mode operations can bypass protections that depend primarily on user-mode process controls. Protected Process Light (PPL) is designed to restrict access to certain sensitive processes, but its effectiveness must be assessed alongside the privileges and capabilities available through kernel-mode components.

The repository's title and description emphasize that process protection alone may not be sufficient when a vulnerable driver provides a path to privileged operations. This reinforces the need to monitor driver loading, enforce driver security policies, and investigate unexpected attempts to interfere with endpoint security processes.

Important limitation: The repository's published proof-of-concept material is evidence of the researcher's demonstrated technique, not confirmation of exploitation in the wild. The presence of a driver in this repository also does not establish that every version of that driver is vulnerable or exploitable on every Windows system.

5. Indicators of Compromise (IOCs)

The repository publishes SHA-256 hashes for the two listed driver files. These may be useful for defensive validation, but their presence alone does not prove malicious activity.

  • libwasys.sys — 04fda396f42384d9295fe306336ee4a685a0c341debdc27ddf9169f0336b46a6

  • MonProcessControl.sys — 0e1cc4f205ddc6b78578de2da209ba3ba1f16fac482f4042bbd02036fc470f04

Source: KillerLand GitHub repository. Validate these hashes against the repository and trusted threat-intelligence sources before deploying detection rules.

6. Potential Impact

If a vulnerable driver is successfully abused, possible consequences include:

  • EDR and antivirus disruption: Security processes may be terminated, weakening endpoint defenses.

  • Reduced detection and response: Security teams may lose visibility or response capabilities during an intrusion.

  • Defense evasion: Attackers may attempt to disable protective tools before executing additional malicious actions.

  • Increased incident-response complexity: Kernel-level activity can make investigation and recovery more challenging.

  • Enterprise-wide exposure: Organizations with insufficient driver controls may face increased risk across managed Windows endpoints.

These are potential consequences of the technique, not confirmed impacts attributed to a specific incident involving KillerLand.

7. Recommendations

Immediate Actions

  • Review the two driver names and published SHA-256 hashes against endpoint inventories and security telemetry.

  • Investigate unexpected driver installations, loading events, and attempts to terminate EDR or antivirus processes.

  • Verify that endpoint security tamper protection and relevant Windows security controls are enabled.

  • Review Microsoft Defender Application Control or App Control for Business policies and the Microsoft vulnerable driver blocklist.

  • Escalate suspicious driver activity for forensic analysis before removing files or modifying evidence.

Preventive Measures

  • Enable the Microsoft vulnerable driver blocklist where supported and appropriate.

  • Evaluate the Attack Surface Reduction rule Block abuse of exploited vulnerable signed drivers.

  • Use Windows security features such as Hypervisor-protected Code Integrity (HVCI), also known as Memory Integrity, where compatible.

  • Apply least privilege and restrict who can install drivers or modify system-level components.

  • Monitor kernel-driver loading and correlate it with unusual process termination and endpoint-security service interruptions.

  • Test driver-blocking policies in audit mode before enforcement to identify compatibility issues.

  • Keep Windows, endpoint security products, and hardware-related software updated.

Microsoft notes that vulnerable-driver blocking policies should be tested carefully because blocking drivers can affect legitimate software and device functionality.

8. Conclusion

KillerLand highlights an important endpoint-security challenge: legitimate digital signatures do not automatically make kernel drivers safe. Through BYOVD techniques, vulnerable signed drivers may provide a route to privileged operations that can undermine endpoint protection, including defenses designed to protect sensitive processes.

For defenders, the priority is to combine driver security controls, endpoint telemetry, tamper protection, and timely investigation of suspicious kernel activity. Proactive driver management can help reduce the risk of security-tool disruption and improve resilience against defense-evasion techniques.

  • T1562.001 — Impair Defenses: Disable or Modify Tools: Relevant when an attacker disables or interferes with security software.

  • T1068 — Exploitation for Privilege Escalation: Potentially relevant when a vulnerable driver is exploited to obtain elevated privileges.

  • T1543.003 — Create or Modify System Process: Windows Service: Consider only if evidence shows a driver or related service is installed or modified as part of the observed activity.

These mappings describe possible relationships to the technique. They should not be interpreted as confirmation that every listed behavior occurred in the repository's demonstrations.

MITRE ATT&CK Mapping

T1562.001 – Impair Defenses: Disable or Modify Tools