ByteWhite1x1 / Driver-DKOM
An advanced DKOM for drivers with "DRIVER_OBJECT"
☆16Updated last year
Related projects ⓘ
Alternatives and complementary repositories for Driver-DKOM
- Mapping your code on a 0x1000 size page☆69Updated 2 years ago
- UM-KM Communication using registry callbacks☆39Updated 4 years ago
- Freeze target threads (external - internal ) by avoiding SuspendThread detections. Or access registers from start address.☆30Updated 7 months ago
- ☆32Updated 2 years ago
- ☆41Updated 3 years ago
- ☆18Updated 2 years ago
- ☆48Updated last year
- ☆50Updated 11 months ago
- Hiding a system thread against conventional means of detection☆35Updated 4 years ago
- A simple MmCopyMemory hook.☆33Updated 2 years ago
- Execute anything in a legit memory region by attacking a windows driver☆20Updated last year
- clearing traces of a loaded driver☆44Updated 2 years ago
- Example driver on how to use SKLib☆4Updated 3 months ago
- ☆49Updated 2 years ago
- ☆28Updated last year
- POC Hook of nt!HvcallCodeVa☆50Updated last year
- Old way for blocking NMI interrupts☆25Updated 2 years ago
- Old project (2020) reformed. Modifies gRT->GetVariable sub function from EFI_APPLICATION. Tested on Win10 22H2 (AMD).☆45Updated 8 months ago
- ☆11Updated 2 years ago
- bypass to the p2c(s) that I have run over the past few months.☆53Updated last year
- ☆24Updated last month
- Bypass using kernel driver (not finish).☆19Updated last year
- An Undetected BE Kernel Driver I developed, Will probably be detected upon releasing this but can be made undetected very easily. Does no…☆54Updated 2 months ago
- Disable NMI Callbacks with Kernelmode Driver☆14Updated last year
- ☆55Updated last year