0xGREG / registry-callbacksLinks
UM-KM Communication using registry callbacks
☆40Updated 5 years ago
Alternatives and similar repositories for registry-callbacks
Users that are interested in registry-callbacks are comparing it to the libraries listed below
Sorting:
- Mapping your code on a 0x1000 size page☆71Updated 3 years ago
- Old way for blocking NMI interrupts☆27Updated 3 years ago
- ☆22Updated 3 years ago
- 将驱动映射到会话空间☆38Updated 3 years ago
- ☆63Updated 3 years ago
- Hiding a system thread against conventional means of detection☆40Updated 5 years ago
- ☆26Updated 2 years ago
- ☆43Updated 4 years ago
- clearing traces of a loaded driver☆47Updated 3 years ago
- search for a driver/dll module that has a wanted section bigger than the size of your image☆20Updated 4 years ago
- Discarded Section Manual Map☆68Updated 5 years ago
- ☆35Updated 3 years ago
- ☆48Updated 5 years ago
- ☆51Updated 2 years ago
- ☆48Updated 3 years ago
- ☆72Updated 3 years ago
- ☆70Updated 4 years ago
- detect hypervisor with Nmi Callback☆41Updated 3 years ago
- ☆34Updated 2 years ago
- page table manipulation to gain physical r/w☆42Updated last year
- ☆48Updated 3 years ago
- An advanced DKOM for drivers with "DRIVER_OBJECT"☆21Updated 2 years ago
- Register a callback in Kernel from a manually mapped driver☆43Updated 4 years ago
- A basic demonstration of directly overwriting paging structures for physical memory r/w and interprocess memory copy☆99Updated 2 years ago
- A simple MmCopyMemory hook.☆37Updated 3 years ago
- POC usermode <=> kernel communication via ALPC.☆66Updated last year
- POC kernel driver with hidden system thread☆13Updated last year
- ☆16Updated 3 years ago
- i stole this from some guys private repo on github☆58Updated 4 years ago
- Virtual and physical memory hacking library using gigabyte vulnerable driver☆70Updated 2 years ago