Questions about this topic? Sign up to ask in the talk tab.
Difference between revisions of "Jynx Rootkit/2.0"
From NetSec
(→Archive Contents) |
|||
| Line 49: | Line 49: | ||
</strong> | </strong> | ||
=Archive Contents= | =Archive Contents= | ||
| + | [root@ares jynx2]# ls | ||
| + | Makefile README config.h jynx2.c packer.sh reality.c | ||
| + | {{info|In this rendition of jynx, two '''shared libraries''' are built by the installation process. One, '''jynx2.so''' functions as the actual rootkit, while the other, '''reality.so''', functions as a method for the remote access user to be able to see their own files and processes.}} | ||
| + | |||
=Configuration Options in Config.h= | =Configuration Options in Config.h= | ||
{{warning|Improper configuration of Jynx2 can result in severe system instability, including [[segmentation fault|segmentation faults]] of nearly every process on the infected host.}} | {{warning|Improper configuration of Jynx2 can result in severe system instability, including [[segmentation fault|segmentation faults]] of nearly every process on the infected host.}} | ||
Revision as of 23:42, 16 March 2012
|
Jynx2 is an expansion of the original Jynx LD_Preload rootkit written in C with several modifications for multi-factor authentication, a more compatible shell drop, and additional hiding features. |
_ _,.-.' .-.
_ .' |,' ."".| |.""._
( || ,',"". `._`' ` ' `.
`\ | `" .-"`-..` . `.
| `..--.._ | \
_,| _...'_.' ,+. `.
,""'| `...-'..""(__.._ -" `"--.. `.
|`._,' ,' /\ .'""` .'""`. `. | `. \
' / / / || || |.`.`. . | \
`.__,'-._' /|` -"' `-.' \ \ \ `"-' \
' `. / /_| | |'""| | .-""'`'"`-,.-"\ .
. / .\ . / | | `._.' || ,' \ \
' / / |/ /_.-+._`-..--"-. . . \ `
/ /.' ' ,'""'-. `"."'""'`.. |. \ \
/ . | j . . | |\__," |. ` ' \
. | | | | ' | '| | ' ` \ \ .
| | | `.____,' ..____,' | | . \
| | | | ._ _..---._ _,' | . '
| | | | | "" . |`"' \ `.| ' ' ' .
| | | | | | | ` ` . . \ |
| | | | | ' | \ `. | | . |
' ' | | | . ` \ \ | | | |
\ ` | | | . `. | | | |
\ \ ' | ` ' ` `+..|___|___|_........
\ \ \| ' . `. `. |
`. \ . . ` `. `-. .'
_,'`. \' . \ `-.._ `._ ,'
_." `._ `.` | . `._ .
`._ _,`"--`. | . `. |
`-._ ,' | `. `|_
,' | | `. `.
.' __...__.| | \ __..._ _,..,.__ `.
`-`"' `._..--'-.__ .' `-..' ``'"--..-'
`"---'
/$$$$$ /$$ /$$ /$$ /$$
|__ $$ | $$ /$$/|__/ | $$
| $$ /$$ /$$ /$$$$$$$ /$$ /$$ | $$ /$$/ /$$ /$$$$$$
| $$| $$ | $$| $$__ $$| $$ /$$//$$$$$$| $$$$$/ | $$|_ $$_/
/$$ | $$| $$ | $$| $$ \ $$ \ $$$$/|______/| $$ $$ | $$ | $$
| $$ | $$| $$ | $$| $$ | $$ >$$ $$ | $$\ $$ | $$ | $$ /$$
| $$$$$$/| $$$$$$$| $$ | $$ /$$/\ $$ | $$ \ $$| $$ | $$$$/
\______/ \____ $$|__/ |__/|__/ \__/ |__/ \__/|__/ \___/
/$$ | $$
| $$$$$$/
\______/
Contents
Archive Contents
[root@ares jynx2]# ls Makefile README config.h jynx2.c packer.sh reality.c
|
|
In this rendition of jynx, two shared libraries are built by the installation process. One, jynx2.so functions as the actual rootkit, while the other, reality.so, functions as a method for the remote access user to be able to see their own files and processes. |
Configuration Options in Config.h
|
Improper configuration of Jynx2 can result in severe system instability, including segmentation faults of nearly every process on the infected host. |
MAGIC_STRING
MAGIC_GID
MAGIC_DIR
CONFIG_FILE
LIBC_PATH
First of all, you need to dig into config.h, and ensure that the settings meet your needs.
MAGIC_STRING should be changed to the name of the directory you want to hide from the system. This can be used as a prefix to your main directory as well as for files. MAGIC_GID will be the Group ID to hide as well. Make sure that you set MAGIC_DIR Group ID to MAGIC_GID for hiding purposes as well. This will help disguise the processes from the system, including commands like ps. CONFIG_FILE defaults to ld.so.preload, which is usually located in /etc. You shouldn't have to change this unless you're going to dig a little deeper into hiding Jynx-Kit. MAGIC_ACK and MAGIC_SEQ have been dropped in Jynx2, since the new backdoor hooks accept() system call, and still includes SSL support. After installing Jynx2, ensure that you restart the daemon that you want to use as the backdoor.
