All Projects → landhb → Hideprocess

landhb / Hideprocess

A basic Direct Kernel Object Manipulation rootkit that removes a process from the EPROCESS list, hiding it from the Task Manager

Programming Languages

c
50402 projects - #5 most used programming language

Labels

Projects that are alternatives of or similar to Hideprocess

rkduck
Linux v4.x.x Rootkit
Stars: ✭ 83 (-74.77%)
Mutual labels:  rootkit
tor-rootkit
A Python 3 standalone Windows 10 / Linux Rootkit using Tor.
Stars: ✭ 142 (-56.84%)
Mutual labels:  rootkit
superhide
Example of hooking a linux systemcall
Stars: ✭ 48 (-85.41%)
Mutual labels:  rootkit
ebpfkit
ebpfkit is a rootkit powered by eBPF
Stars: ✭ 472 (+43.47%)
Mutual labels:  rootkit
Vegile
This tool will setting up your backdoor/rootkits when backdoor already setup it will be hidden your spesisifc process,unlimited your session in metasploit and transparent. Even when it killed, it will re-run again. There always be a procces which while run another process,So we can assume that this procces is unstopable like a Ghost in The Shell
Stars: ✭ 601 (+82.67%)
Mutual labels:  rootkit
NtSymbol
Resolve DOS MZ executable symbols at runtime
Stars: ✭ 78 (-76.29%)
Mutual labels:  rootkit
Bdvl
LD_PRELOAD Linux rootkit (x86 & ARM)
Stars: ✭ 232 (-29.48%)
Mutual labels:  rootkit
linux-rootkits-red-blue-teams
Linux Rootkits (4.x Kernel)
Stars: ✭ 56 (-82.98%)
Mutual labels:  rootkit
satan
🔓 x86 Linux Kernel rootkit for Debian 9 (4.9.0-11-686-pae)
Stars: ✭ 31 (-90.58%)
Mutual labels:  rootkit
rkorova
ld_preload userland rootkit
Stars: ✭ 34 (-89.67%)
Mutual labels:  rootkit
ebpfkit-monitor
ebpfkit-monitor is a tool that detects and protects against eBPF powered rootkits
Stars: ✭ 80 (-75.68%)
Mutual labels:  rootkit
first-steps-and-hardening-in-ubuntu-server-and-docker
First Steps in Ubuntu (Server) / Hardening and Config With Docker
Stars: ✭ 28 (-91.49%)
Mutual labels:  rootkit
SMM-Rootkit
SMM rootkit similar to LoJax or MosaicRegressor
Stars: ✭ 44 (-86.63%)
Mutual labels:  rootkit
Simple-Antirootkit-SST-Unhooker
This is a demo project to illustrate the way to verify and restore original SST in case of some malware hooks
Stars: ✭ 31 (-90.58%)
Mutual labels:  rootkit
lsrootkit
Rootkit Detector for UNIX
Stars: ✭ 53 (-83.89%)
Mutual labels:  rootkit
Umbra
A LKM rootkit targeting 4.x and 5.x kernel versions which opens a backdoor that can spawn a reverse shell to a remote host, launch malware and more.
Stars: ✭ 98 (-70.21%)
Mutual labels:  rootkit
Solaris
A local LKM rootkit loader/dropper that lists available security mechanisms
Stars: ✭ 47 (-85.71%)
Mutual labels:  rootkit
S6 pcie microblaze
PCI Express DIY hacking toolkit for Xilinx SP605
Stars: ✭ 301 (-8.51%)
Mutual labels:  rootkit
Father
LD_PRELOAD rootkit
Stars: ✭ 59 (-82.07%)
Mutual labels:  rootkit
raisin
Reverse shell and rootkit
Stars: ✭ 18 (-94.53%)
Mutual labels:  rootkit

HideProcess

Update: Now works for both 64bit and 32bit architecture! Tested on:

  • Windows 10 Enterprise Edition x64 Build 15063.rs2_release.170317-1834
  • Windows 7 SP1 x86

Demo

Writeup

For more information on the concepts used here please check out my article.

Limitations

Does not bypass PatchGuard or driver signing requirements.

Please use a VM whenever you run this. Current tests on Windows 10 observe it takes about 30 minutes after unlinking the process to induce a BSOD.

Compiling The Driver

The driver has a number of dependencies and you'll need to compile it using msbuild or visual studio. I used Visual Studio during the development process. You'll need:

  1. The Windows 10 SDK
  2. WDK 10

Once those are setup and integrated with Visual Studio, start a new empty KMDF (Kernel Mode Driver Framework) project and import the files in the /driver folder.

Under Debug -> [ProjectName] Properties -> Driver Settings -> General, make sure your Target OS Version is Windows 7 and the Target Platform is Desktop.

Then under Build -> Configuration Manager, make sure the Platform is Win32, and x86 is selected under "Active solution platform".

Now you should be able to use Build -> Build [ProjectName] to build the project. This will generate a .sys file if everything went well. Then put the .sys file in c:\Windows\System32\drivers[ProjectName].sys, or change the following define statement in loader.c to the path you've specified:

#define DRIVER "c:\\Windows\System32\drivers\Rootkit.sys"

Compiling The Loader

For the loader you can simply use the makefile and mingw to cross compile it.

sudo apt-get install mingw-w64

Then you can create a 32-bit Windows executable using the makefile with:

make 32bit

And a 64-bit Windows executable with:

make 64bit
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].