Smart computer users know that once a computer is infected by a rootkit, it’s changed forever. And as Windows rootkits go, Hacker Defender is among the most dangerous. The author of Hacker Defender, holy_father, explains why he does what he does, and what you can do to detect his rootkit.

Antivirus companies sell a fake sense of security, but they do not bring real security to your computer. Antivirus just fights programs that are visible to common users. They don’t care about the cause.

If I publish Hacker Defender’s antidetection code, antivirus companies will do nothing but add a few bytes to their databases of virus patterns, or simply fool my engine in some way. They show their customers they can handle rootkits based on my antidetection engine, but they won’t solve the problem. So there would be easy ways to bypass them again and again.

This attitude brings money to security companies because their users download upgrades and buy new versions of their products. This is why these security companies don’t want to change the situation.

Yes, antivirus products will protect you against wildly spreading threats like destructive worms. But the real danger for users is from pointed attacks, where private tools are used. These tools use the same methods as my tools. They are not detected because security companies have no chance to download them and add those few bytes to their databases. Security companies catch only the tools they know and do not solve the cause. So attackers will succeed with their tools.

This has to be changed. Hacker Defender and other rootkit projects force security companies to care about the core of the problems, to develop better and better products. And after years, I see the results. The situation is better. But there is still a lot of work to be done with rootkit detectors and antivirus products.

This is why I will continue in my work to try to find ways to bypass their poor products until antivirus companies come with the real solution. And this is why a lot of my customers are security guys who offer penetration testing etc., not bad (or blackhat) guys.

People often ask me why I don’t write security applications instead of rootkits. It is clear that I would have to prefer one of these applications, either rootkit or anti-rootkit. If it is rootkit, no one will use my anti-rootkit, so it would be a waste of time to implement anti-rootkit. If it is anti-rootkit, then again, no one will use the rootkit. I’ve decided for the rootkit way because it is more painful for so called security companies.

For example, Microsoft claims that Windows Malicious Software Removal Tool for XP/2000/2003 (MSRT) can detect Hacker Defender. I always test the latest MSRT with Hacker Defender, and the latest MSRT does not even detect the latest public version of Hacker Defender (hxdef 1.0.0 revisited), which was published weeks ago and is available for download to everyone, with full source code.

You can try it on your machine yourself.

For the paid versions of Hacker Defender, the code of the public version is scrambled and changed to avoid antivirus detection. Tests for eight antivirus products (Avast!, AVG, Kaspersky, McAfee, NOD32, Norton, Panda, PC-cillin) with the newest upgrades, are always made before the customer receives the final product. The code is always unique for each customer, which means that detection of one customer’s product should not affect other customer’s products.

If you think about it, simple code scrambling in what is called dangerous or malicious software results in a clean scan report. It is really as easy as changing one byte here and there to fool your expensive antivirus product.

This fact forced us to think about how antivirus products are implemented and what all those powerful heuristics engines that reveal even unknown future threads really mean. Just visit some antivirus vendor website to see what they offer. Then modify a few bytes in your favourite destructive malware and create your own opinion.

The antidetection engines in more advanced paid versions of Hacker Defender also evade the latest versions of all well known modern rootkit detectors like BlackLight, RootkitRevealer, IceSword, UnHackMe and RKDETECTOR 2.0.

It is curious that Hacker Defender’s antidetection was implemented months ago and hasn’t changed (except some minor bugfixes) since then. In spite of this fact, no security product is able to beat it today.

The world is still waiting for the first real rootkit detector that would bypass Hacker Defender’s antidetection engine. Hacker Defender is just there to show they have to improve their products.

Editor’s Note: While we helped a bit with english and formatting, this is pure holy_father.

Background: