Expanding on Didier Stevens comments.Not all rootkits/hidden components are malicious
. Legitimate programs can use rootkits for legitimate reasons. Most ARK tools check for rookit-like behavior which is not always indicative of a malware infection. It is normal for a Firewall, some anti-virus and anti-malware software, CD Emulators
, virtual machines, sandboxes
and Host based Intrusion Prevention Systems (HIPS) to exhibit rootkit-like behavior or hook
into the OS kernal/SSDT (System Service Descriptor Table) in order to protect your system. SSDT is a table that stores addresses of functions that are used by Windows. Whenever a function is called, Windows looks in this table to find the address for it. Both legitimate programs and rootkits can hook into and alter this table.
When used for malicious reasons, a rootkit takes active measures to obscure its presence (hide itself from view
) within the host system through subversion or evasion of standard operating system security tools and APIs
used for diagnosis, scanning, and monitoring. Rootkits are able to do this by modifying the behavior of an operating system's core parts through loading code into other processes, the installation or modification of drivers, or kernel modules. Rootkits hook into the Windows 32-bit kernel, and patch several APIs to hide new registry keys and files they install. Hooking
is one of the techniques used by a rootkit to alter the normal execution path of the operating system. Rootkit hooks are bascially installed modules which intercept the principal system services that all programs and the OS rely on. By using a hook, a rootkit can alter the information that the original OS function would have returned. There are many tables in an OS that can be hooked by a rootkit and those hooks are undetectable unless you know exactly what you're looking for.API Kernel hooks are not always bad
since some system monitoring software and security tools use them as well. If no hooks are active on a system it means that all system services are handled by ntoskrnl.exe which is a base component of Windows operating systems and the process used in the boot-up cycle of a computer. Anti-rootkit (ARK) scanners do not differentiate between what is good and what is bad...they only report what is found
. Therefore, even on a clean system some hidden components may be detected when performing a scan to check for the presence of rootkits and you should not be alarmed if any hidden entries created by legitimate programs are detected. In most cases further investigation is required after the initial ARK scan by someone trained in rootkit detection or with advanced knowledge of the operating system. Report logs need to be analyzed and detected components identified in order to determined if they are benign, system critical or malevolent before attempted removal. Using an ARK scanner without knowing how to tell the difference between legitimate and malicious entries can be dangerous if a critical component is incorrectly removed.
If you're unsure how to use a particular Anti-rootkit (ARK) tool or interpret the log it generates, then you probably should not
be using it. Some ARK tools are intended for advanced users
or to be used under the guidance
of an expert who can interpret the log results and investigate it for malicious entries before taking any removal action. Incorrectly removing legitimate entries could lead to disastrous problems
with your operating system.