For a time I was pleasantly impressed with avast!; I found it very good to use and the fact that it’s free to home users is wonderful, that was until I came across this file: fXp://ftp.untergrund.net/users/MagikGimp/Viruses/HoverDesk_2.5.zip. Unfortunately, as a result of the consequences of running this file (I am in the process of rebuilding my computer now) I can no longer use the software with confidence. I want to make it clear that I do not blame avast!, it being freeware after all but that I merely want to make this file aware to the developers in the hope that the disastrous effect it had on avast! may be resolved and that, in time, I may decide to use avast! again because I am now forced to look for an alternative.
When I ran the executable in the archive, as far as I can tell, it began to shut down avast! without warning. I saw messages that each component of the software was being stopped and even when avast!'s registry security measures were employed and I chose to not make changes to the registry, damage to my computer was still made. The next thing to happen was that a system reboot was forced and on logging-on again I was unable to run avast! at all. The main executable had in fact been damaged in such a way as it would no longer run and I also found that could no longer install ANY other anti-virus software (free or commercial trial product). On running Task Manager it could be seen that my CPU level was constantly at 100% and programmes with eight (?) digit random number names were executing and stopping although the programmes using the most CPU resources were standard software packages (including Task Manager) as if the malware was attaching itself to them if you see what I mean. The computer at this point was still usable but ran very slowly because of the maxed-out CPU resources. Any attempt to end the strange programmes with random names did not resolve the problems.
I advise you run this malware on a machine that you don’t mind having to rebuild as at the time I ran the executable (with full updates installed and after scanning the file before running it) it seemed there was nothing avast! could do to prevent the incredible damage it caused to my machine.