Scanning for Rootkits with chkrootkit
Up-to-date and secure installations, firewalls, limited ssh access and strong passwords are all basic and essential aspects of security. However, continued active monitoring of server content for malware is also necessary.
One method of monitoring content is to scan for rootkits.
Scanning for rootkits will not stop all attacks, it is not an active defense. If your server has been compromised then a scan will not stop the rootkit. Unfortunately, the presence of a rootkit is a clear indication that your server security has been compromised will need to be rebuilt.
It is worth finding out how the rootkit got into your server in the first place so it doesn't happen again but you will still need to reinstall.
This article is about the scanning mechanism rather than identifying how something may have entered your system. It is only about checking the validity of the server content.
Scanning is easily done with a program called chkrootkit. This can also be automated so you don't have to log in and scan on a daily basis.
We're going to install chkrootkit from source. It is available from most repositories but installing from source ensures we have not installed a compromised scanning system (sadly, it's been known to happen!).
Let's begin. Log into your VPS and navigate to your sources directory (or create one if you don't have one you normally use). The sources directory can be placed anywhere. Placing it in root's home directory can make it easier to find and maintain, so we'll do that in our examples.
sudo mkdir /root/sources cd /root/sources
Download the latest chkrootkit version (this command will always fetch the latest version):
sudo wget ftp://ftp.pangeia.com.br/pub/seg/pac/chkrootkit.tar.gz
To check that the file you have is the same file that chkrootkit.org intended you to have, check the md5 signature. To do this enter:
This will create an output that is unique to the downloaded file - check this with the md5 signature which is available from a mirror website (see the note below):
Note: You may notice that we have checked the md5sum from a different server. On something as important as this, we want to make sure we don't have a questionable download.
If the two don't match then you have a compromised download. You will notice as you download more and more source code that they all have md5 or other style of signatures for integrity checks.
Unpack the download and move into the new directory:
sudo tar xvfz chkrootkit.tar.gz cd chkrootkit-0.47
In this example, we downloaded and unpacked version 0.47 - remember the download command above will always download the latest version.
Now you need to compile the program which will take less than 2 seconds:
sudo make sense
You can keep the folder in your sources directory or move the whole thing elsewhere more convenient for you. In this example, we will keep it in the sources directory.
To run the chkrootkit, simply give the command as the sudo user:
The output on the demo server should give the all clear, but a warning may look something like this:
Warning: Possible Showtee Rootkit installed /usr/include/file.h /usr/include/proc.h You have 9 process hidden for readdir command You have 11 process hidden for ps command chkproc: Warning: Possible LKM Trojan installed
Check the warnings and, as already said and as recommended, if you are infected you need to reinstall with a fresh image.
Naturally, all this can be automated with a cron job. As the procedure needs to be run as root, enter the root crontab configuration:
sudo crontab -e
The recommended method (from the chkrootkit website) is as follows:
0 3 * * * (cd /root/sources/chkrootkit-0.47; ./chkrootkit 2>&1 | mail -s "chkrootkit output" firstname.lastname@example.org)
That will run the command at 3am every day and, providing you have 'mail' installed and configured, email the results to the specified address.
© 2015 Rackspace US, Inc.
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License
See license specifics and DISCLAIMER