windows 10 compatible
Kernel Mode, driver only, ring O, remote UDP keylogger.

Application Security

i did not implemented any IoCtl, in order to avoid any Security Issues. in addition, i did not implemented any Revc-datagram method’s for this exact same reason, however if you use this driver & see any security problems, please report them here as an issue.


Using this software is at your Own Risk. The Author will not be held responsible by any circumstances.


this project splits down into two parts:
1 KeyBoard hook.
2 Raw Networking (datagram socket manipulation).

to monitor the key strokes we need to get in beetwin the keyboard device IRP & the PS/2 port.
Much of the KeyBoard Hook implementation & code is borrowed from fdiskyou.
while to implement this ‘kernel man in the middle’, we need to mimic the IRP function passed down from the physical device up to the operating system processing; this is done by installing a hook beetwin the keyboard device and passing down each IRP request to the next implementation level.

Our hook (by the diagram above) will come in beetwin win32k.sys & KBDHID.sys, each request is cached by our hook, proccessed by Our driver and passed up to the next irql.
The Second part of Our driver Operation is to log the keystrokes & send them back to our monitoring server.
i have implemented a UDP-DataGram protocol, as we do not recieve or handle any data coming back from the server, and this also make’s the monitoring process a lot simpler by the server side.
Another Advantage to a udp implementation is that the port can be closed and opened constantly to make the #dfir work a lot harder, and udp is not a stream based connection so you can avoid traffic logs etc’.
to implement that i made use of the Wsk, (windows socket kernel), as to avoid any user-mode application.


you are encouraged to look at the source code your self.
so you can implement networking and hooks as you wish at the kernel level. the major code and main logic.


currently only the local keylogger is Generic and can be used W/O building the driver (as it simply logs the keystroke’s to C:\Windows\logs), but the remote udp based (that do not need to write any data to disk to run), needs to be build to your server address (or any other solution. this can be done with very minor code modifications. e.g let the driver read from the registry your ip and load it in /src/driver.c line 420).


The driver is not signed, so you will have to disable code integrity:
(From an elevated command prompt):
bcdedit /set testsigning on
shutdown /r -f -t 00

sc create kbMon type=kernel binpath=”\path\to\your\driver.sys”
sc start kbMon


bcdedit /set testsigning off
sc stop kbMon
shutdown /r -f -t 00

if you encounter any problems simply restart your computer.

For any bugs comment an issue at the github repo.