Rootkit Hunter Wiki
Brought to you by:
dogsbody,
dogsbodymark
Menu
▾
▴
scan2
Examples of some commands that can be run manually
# rkhunter --list tests
# rkhunter --update -c -sk --pkgmgr RPM
# rkhunter -c -sk --debug
# rkhunter -c -sk --configfile /media/disk/RKH/date/rkhunter.conf
# rkhunter --enable 'filesystem'
# rkhunter --enable "all”
# rkhunter --enable 'deleted_files'
Example of manual scan without skdet or unhide
# rkhunter --enable rootkits
( Rootkit Hunter version 1.4.2 )
Checking for rootkits...
Performing check of known rootkit files and directories
55808 Trojan - Variant A ( Not found )
ADM Worm ( Not found )
AjaKit Rootkit ( Not found )
Adore Rootkit ( Not found )
aPa Kit ( Not found )
Apache Worm ( Not found )
Ambient (ark) Rootkit ( Not found )
Balaur Rootkit ( Not found )
BeastKit Rootkit ( Not found )
beX2 Rootkit ( Not found )
BOBKit Rootkit ( Not found )
cb Rootkit ( Not found )
CiNIK Worm (Slapper.B variant) ( Not found )
Danny-Boy's Abuse Kit ( Not found )
Devil RootKit ( Not found )
Dica-Kit Rootkit ( Not found )
Dreams Rootkit ( Not found )
Duarawkz Rootkit ( Not found )
Enye LKM ( Not found )
Flea Linux Rootkit ( Not found )
Fu Rootkit ( Not found )
Fuck`it Rootkit ( Not found )
GasKit Rootkit ( Not found )
Heroin LKM ( Not found )
HjC Kit ( Not found )
ignoKit Rootkit ( Not found )
IntoXonia-NG Rootkit ( Not found )
Irix Rootkit ( Not found )
Jynx Rootkit ( Not found )
KBeast Rootkit ( Not found )
Kitko Rootkit ( Not found )
Knark Rootkit ( Not found )
ld-linuxv.so Rootkit ( Not found )
Li0n Worm ( Not found )
Lockit / LJK2 Rootkit ( Not found )
Mood-NT Rootkit ( Not found )
MRK Rootkit ( Not found )
Ni0 Rootkit ( Not found )
Ohhara Rootkit ( Not found )
Optic Kit (Tux) Worm ( Not found )
Oz Rootkit ( Not found )
Phalanx Rootkit ( Not found )
Phalanx2 Rootkit ( Not found )
Phalanx2 Rootkit (extended tests) ( Not found )
Portacelo Rootkit ( Not found )
R3dstorm Toolkit ( Not found )
RH-Sharpe's Rootkit ( Not found )
RSHA's Rootkit ( Not found )
Scalper Worm ( Not found )
Sebek LKM ( Not found )
Shutdown Rootkit ( Not found )
SHV4 Rootkit ( Not found )
SHV5 Rootkit ( Not found )
Sin Rootkit ( Not found )
Slapper Worm ( Not found )
Sneakin Rootkit ( Not found )
'Spanish' Rootkit ( Not found )
Suckit Rootkit ( Not found )
Superkit Rootkit ( Not found )
TBD (Telnet BackDoor) ( Not found )
TeLeKiT Rootkit ( Not found )
T0rn Rootkit ( Not found )
trNkit Rootkit ( Not found )
Trojanit Kit ( Not found )
Tuxtendo Rootkit ( Not found )
URK Rootkit ( Not found )
Vampire Rootkit ( Not found )
VcKit Rootkit ( Not found )
Volc Rootkit ( Not found )
Xzibit Rootkit ( Not found )
zaRwT.KiT Rootkit ( Not found )
ZK Rootkit ( Not found )
Performing additional rootkit checks
Suckit Rookit additional checks ( OK )
Checking for possible rootkit files and directories ( None found )
Checking for possible rootkit strings ( None found )
Performing malware checks
Checking running processes for suspicious files ( None found )
Checking for login backdoors ( None found )
Checking for suspicious directories ( None found )
Checking for sniffer log files ( None found )
Suspicious Shared Memory segments ( None found )
Performing Linux specific checks
Checking loaded kernel modules ( OK )
Checking kernel module names ( OK )
System checks summary
File properties checks...
All checks skipped
Rootkit checks...
Rootkits checked : 353
Possible rootkits: 0
Propupd issue with manual scans
You may have done a full scan, checked your log, investigated some warnings and established that some warnings are false positives, while others may need further investigation or second opinion.
It is possible that by running some kind of manual test, you can produce warnings for only false positives. If so, you can then run propupd command as the property update affects only the last scan.
This means that if you repeat a full scan, the warning are only in the category to be checked.
Naturally it may take a little testing to disable or enable certain tests, before your log shows only warnings that you have previously established as false positives.
If you can not work out how to minimize the log to output only false positives, you can not run propupd until your second opinion or further investigation validates your warnings are ALL false positives.
