reveng_rtkit
%20x86__64%20and%20Kernel%205.11.0--49--generic-yellow){kind=icon}
reveng_rtkit is a Linux Loadable Kernel module (aka LKM) based rootkit targeting Linux Kernel: 5.11.0-49-generic as it was only tested on it till now.
:no_entry_sign: [Disclaimer]: Use of this project is for Educational/ Testing purposes only. Using it on unauthorised machines is strictly forbidden. If somebody is found to use it for illegal/ malicious intent, author of the repo will not be held responsible.
reveng_rtkit mechanism:
Rootkit features:
| Sl. no. | Name | Features |
|---|---|---|
| 1. | Finding Syscall Table address | By creating custom kallsyms_lookup_name function to get address of sys_call_table symbol from kernel memory. |
| 2. | Function Hooking | Get the address of the syscall from sys_call_table to get them hooked, then modify CR0 register to remove write protect bit and then modify/edit the sys_call_table and then again applying write protection to kernel memory. |
| 3. | Hide Rootkit | Hides itself by deleting itself(or entry) from responsible linked list. |
| 4. | Hide Processes/implants | Done in same way, as mentioned above in Sl. no. 2. |
| 5. | Unable to rmmod rootkit module | Using kernel function called try_module_get() makes impossible for admins to remove our rootkit. |
| 6. | Interactive Control | Implementing an IOCTL which manages the features of the rootkit and allows the user to send it commands. |
| 7. | Bypassing | Can bypass infamous rkhunter antirootkit |
Let's see what functions will be called during loading the rootkit:
| Defined within Filename | Functions | function name in rootkit.c | Working | Effectivity of remove_rootkit() | Mode of access |
|---|---|---|---|---|---|
| hide_show_helper.h | proc_lsmod_hide_rootkit() | hide_rootkit() | Hides rootkit from "/proc/modules" file, "/proc/kallsyms" file and "lsmod" command. | No effectivity | ./client_usermode |
| hide_show_helper.h | sys_module_hide_rootkit() | hide_rootkit() | Hides rootkit from "/sys/module/ |
No effectivity | ./client_usermode |
| hide_show_helper.h | proc_lsmod_show_rootkit() | show_rootkit() | Reveals our rootkit in "/proc/modules" file, "/proc/kallsyms" file and "lsmod" command. | Will work effectively | ./client_usermode |
| hide_show_helper.h | sys_module_show_rootkit() | show_rootkit() | Reveals our rootkit in "/sys/module/ |
_ | ./client_usermode |
| rootkit.c | tidy() | tidy() | In this function we do some clean up. If we don't do this, there will be some errors during unloading the rootkit using rmmod. |
_ | _ |
| rootkit.c | protect_rootkit() | protect_rootkit() | This is very simple function which just makes impossible to unload the rootkit by "rmmod rootkit" command even if it is visible. However it is still possible to unload by "rmmod -f rootkit" if kernel was compiled with support for forced unloading modules. link: sysprog21.github.io | _ | ./client_usermode |
| rootkit.c | remove_rootkit() | remove_rootkit() | Making rootkit removable from kernel using rmmod | _ | ./client_usermode |
| hook_syscall_helper.h | hacked_kill() | rootkit_init() and rootkit_exit(void) | Process/Implant Hiding | _ | cmd prompt: kill -31 \ |
| hook_syscall_helper.h | hacked_kill() | rootkit_init() and rootkit_exit(void) | getting rootshell | _ | cmd prompt: kill -64 \ |
NOTE:
Function tidy(), sys_module_hide_rootkit() and sys_module_show_rootkit() are not used in code. They were commented out. The reason behind that will be discussed in details in my blog post.
How to use it:
- Clone the repo
$ git clone https://github.com/reveng007/reveng_rtkit.git - Enter the directory
$ cd reveng_rtkit/ - Now, we have 2 directories: kernel_src and user_src.
- user_src:
Contains
usermode client codeto interact with our rootkit module (once it it loaded into the kernel) via the registered Character Device file. - kernel_src:
Contains
kernelmode rootkit: reveng_rtkitwhich will be responsible for the whole mayhem :wink:.
- user_src:
Contains
$ cd kernel_src/
$ make
$ sudo insmod reveng_rtkit.ko
- To interract with the kernel rootkit. Open another terminal
$ cd reveng_rtkit/user_src/ - compile and run the code
$ gcc client_usermode.c -o client_usermode $ sudo ./client_usermodeNOTE: Be sure to run the code with root priv., because we are interracting with device driver, which is a part of the Linux kernel.
- Another method to interract with it is via kill syscall interception:
- To hide process/implant:
$ kill -31 <pid>
- To hide process/implant:
- To get root shell (without providing a password):
$ kill -64 <any pid>
NOTE:
This rootkit is capable of providing rootshell to only bash and sh shell, not others. Although, it is possible for other shells as well but with some tricks. We can use system() C function alike function in Linux Kernel programming, so that we 1st trigger a bash/sh shell then offer rootshell to the attacker. I have'nt got that type of kernel function till now, but as soon as I get it, I will add it up. If anybody viewing this know about this, or interested to contribute, are most welcome to make a pull request.
- To remove this rootkit module: 1stly make module visible via
showcommand using client_usermode file as reveng_rtkit while loading hides itself from being revealed (also change toremovemode, if you have made rootkit module toprotectmode previously).reveng007@ubuntoo ~/D/k/B/L/x/1/g/kernel_src> sudo ../user_src/client_usermode [sudo] password for reveng007:
[+] Created by @reveng007(Soumyanil)
|+++++++++++++++++++ Available commands ++++++++++++++++++|
hide : Command to hide rootkit => In this mode, in no way this rootkit be removable
show : Command to unhide rootkit => In this mode, rootkit_protect and rootkit_remove will work effectively
protect : Command to make rootkit unremovable (even if it can be seen in usermode)
remove : Command to make rootkit removable
kill -31 process in the below prompt to close without any error
kill -64 root in the below prompt to close without any error
[+] Driver file opened [?] Enter the Value to send: show [+] Written Value to Device file [*] Reading Value from Device file: Value present in Device: show
[+] Device file closed reveng007@ubuntoo ~/D/k/B/L/x/1/g/kernel_src> sudo ../user_src/client_usermode
[+] Created by @reveng007(Soumyanil)
|+++++++++++++++++++ Available commands ++++++++++++++++++|
hide : Command to hide rootkit => In this mode, in no way this rootkit be removable
show : Command to unhide rootkit => In this mode, rootkit_protect and rootkit_remove will work effectively
protect : Command to make rootkit unremovable (even if it can be seen in usermode)
remove : Command to make rootkit removable
kill -31 process in the below prompt to close without any error
kill -64 root in the below prompt to close without any error
[+] Driver file opened [?] Enter the Value to send: remove [+] Written Value to Device file [*] Reading Value from Device file: Value present in Device: remove
[+] Device file closed
### Bypassing ***rkhunter*** antirootkit:
Here is the log file, that was generated:
[](https://asciinema.org/a/488606)
- Only one warning is present:
1. /usr/bin/lwp-request : [stackexchange](https://unix.stackexchange.com/questions/373718/rkhunter-gives-me-a-warning-for-usr-bin-lwp-request-what-should-i-do-debi)
So, this is not a threat! cool!
### Update:
Today, I found out this ***Warning***.
Then searched for other options of ***rkhunter*** to get more informations about this "**warning**", that which exact processes are actually causing this warning (`suspicious (large) shared memory segments`). Found out this:
We can see it is telling us, `configured size allowed: 1.0MB`, i.e. those processes which takes more than 1MB gets flagged. But main point is our rootkit is not getting flagged :) (More like False-Positive thing).
There are several links related to this:
1. [serverfault](https://serverfault.com/questions/697865/rkhunter-suspicious-shared-memory-segments)
2. [linuxquestions](https://www.linuxquestions.org/questions/linux-security-4/rkhunter-gives-warnings-about-large-shared-memory-segments-and-a-few-strange-files-4175649554/)
### To-Do list :man_mechanic::
- Hiding process files completely. Our hidden process file can be accessed to open/read. If someone does, `ls <filename>`, they can easily open them.
- Successfully able to hide and reveal our LKM module from `/sys/module/` directory using sycall interception, in order to decieve usermode programs [issue #6](https://github.com/reveng007/reveng_rtkit/issues/6).
- Adding system() C function alike function in Linux Kernel programming, in order to open a new bash/sh prompt [issue #1](https://github.com/reveng007/reveng_rtkit/issues/1).
- Adding Linux Kernel Sockets [issue #2](https://github.com/reveng007/reveng_rtkit/issues/2).
- Surviving system reboot [issue #5](https://github.com/reveng007/reveng_rtkit/issues/5).
- Breaking `kernel_src/reveng_rtkit.c` [issue #8](https://github.com/reveng007/reveng_rtkit/issues/8).
- Adding Capabilty to `bypass SELinux enabled Linux System` [issue #9](https://github.com/reveng007/reveng_rtkit/issues/12).
- Bypassing `chkrootkit antirootkit` [issue #4](https://github.com/reveng007/reveng_rtkit/issues/4).
- Getting detected by `chkrootkit antirootkit` till now, under `chkproc section`: [chkproc.c](https://github.com/Magentron/chkrootkit/blob/master/chkproc.c)
### Limitations:
- This LKM based rootkit can only be used in those Linux OSs, which don't have these two protections:
1. Secure Boot
2. Adding a grub parameter to "`/etc/default/grub`" file.
This thing was pointed out to me by [Artem Baranov](https://www.linkedin.com/in/artem-baranov-86163135) and this [link](https://blog.delouw.ch/2017/04/18/signing-linux-kernel-kodules-and-enforce-to-load-only-signed-modules/) was shared to me, on my linkedin post, by [Victor Sergeev](https://ae.linkedin.com/in/victor-sergeev/), for further research.
#### Detailed Blog article on ***reveng_rtkit*** LKM rootkit, is available [now](https://reveng007.github.io/blog/2022/03/08/reveng_rkit_detailed.html), where I have explained how I created this LKM rootkit step by step.
> If you(viewers) have spotted anything erronious or something which should be made correct, haven't documented correctly or haven't credited someone's work properly, please don't hesitate to reach out to me via those social media handles listed at the end of this file.
### Honourable Mentions:
- [kurogai/100-redteam-project](https://github.com/kurogai/100-redteam-projects#honorable-mentions)
- [milabs/awesome-linux-rootkits](https://github.com/milabs/awesome-linux-rootkits#speak_no_evil-related-stuff)
- Selected by BSides St Pete, Florida to be presented - [link](https://drive.google.com/file/d/19Jv-Ju-6tVjO2OD1uyKkYC7hxXhWemcY/view).
- Selected by BSides Prishtina, Kosovo to be presented - [link](https://drive.google.com/file/d/1Z0bljsYvX8nr4BbOQi6N0XdtfsCIYP_B/view?usp=share_link).
- BlackHat, USA - [twitter-thread](https://twitter.com/reveng007/status/1594670602870173696)
### Resources that helped me:
1. This project is heavily inspired by [Heroin](https://web.archive.org/web/20140701183221/https://www.thc.org/papers/LKM_HACKING.html#A-b) by Runar Jensen (didn't get any of his social media handle ;( ) and [Diamorphine](https://github.com/m0nad/Diamorphine/) by [@m0nadlabs](https://twitter.com/m0nadlabs) open source LKM rootkit projects. Especially, the `Syscall interception mechanism section` was totally taken from [Diamorphine](https://github.com/m0nad/Diamorphine/) repo by [@m0nadlabs](https://twitter.com/m0nadlabs).
2. https://github.com/pentesteracademy/linux-rootkits-red-blue-teams
3. Rootkit features: https://github.com/R3x/linux-rootkits
4. Excellent resource for grabbing lkm rootkit concepts: https://jm33.me/tag/lkm.html
5. Simple LKM rootkit: https://theswissbay.ch/pdf/Whitepaper/Writing%20a%20simple%20rootkit%20for%20Linux%20-%20Ormi.pdf
6. IOCTL: https://github.com/Embetronicx/Tutorials/tree/master/Linux/Device_Driver/IOCTL
7. https://infosecwriteups.com/linux-kernel-module-rootkit-syscall-table-hijacking-8f1bc0bd099c
8. LKM HACKING: https://web.archive.org/web/20140701183221/https://www.thc.org/papers/LKM_HACKING.html
9. Hide Files and Processes:\
i. https://web.archive.org/web/20140701183221/https://www.thc.org/papers/LKM_HACKING.html#II.2.1.</br>
ii. https://web.archive.org/web/20140701183221/https://www.thc.org/papers/LKM_HACKING.html#II.5.</br>
iii. https://jm33.me/linux-rootkit-for-fun-and-profit-0x02-lkm-hide-filesprocs.html
10. Get Rootshell: https://xcellerator.github.io/posts/linux_rootkits_03/
11. kobject: https://www.win.tue.nl/~aeb/linux/lk/lk-13.html
12. https://sysprog21.github.io/lkmpg/
13. https://ish-ar.io/kprobes-in-a-nutshell/
14. Editing cr0 register: https://hadfiabdelmoumene.medium.com/change-value-of-wp-bit-in-cr0-when-cr0-is-panned-45a12c7e8411
15. https://www.researchgate.net/publication/240376985_UNIX_and_Linux_based_Rootkits_Techniques_and_Countermeasures
## Slides from my talk on [BSides Singapore](https://bsidessg.org/)
1. PPT: [PPT Version](https://github.com/reveng007/reveng_rtkit/blob/main/reveng_rtkit%20-BSides%20Singapore.pptx)
2. PDF: [pdf Version](https://github.com/reveng007/reveng_rtkit/blob/main/reveng_rtkit%20-BSides%20Singapore.pptx.pdf)
### Author: @reveng007 (Soumyanil Biswas)
---
[](https://twitter.com/reveng007)
[](https://www.linkedin.com/in/soumyanil-biswas/)
[](https://github.com/reveng007/)