SuperAntiSpyware Causes Destructive False Alarms - Fix Info Included.

Harvey

Administrator<br>Elite Member
Oct 9, 1999
35,059
73
91
Because the effect can be destructive, I'll give you the fix before I explain the problem.

If you have any version of SuperAntiSpyware earlier than ver. 4.40:

1. If any earlier version of SuperAntiSpyware reports alerts for a group that includes th name, Trojan.Agent/Gen-CDesc, exit the program, and DO NOT let it attempt to repair them.

2. Run your AV program and any other anti-malware programs, other than SuperAntiSpyware, and back up your system.

3. Uninstall any older version of SuperAntiSpyware, and download and install ver. 4.40.

The story:

Yesterday, a friend phoned with justified panic. He had just run SuperAntiSpyware ver. 4.30 which reported around 3,000 malicious entries as Trojan.Agent/Gen-CDesc[WV-LG] and others with the same name followed by other letters in the brackets. When he clicked to continue and clean the problems, the system said it had to reboot to complete the cleanup. When Windows restarted, many of his programs no longer worked and reported one or more missing files, mostly DLL's.

The good news for him is that it didn't destroy any data files, and if it had, he has been good about backing up his system. I saved his current data files to a flash drive and spent a couple of hours restoring his system from a two week old backup, and when I again ran SuperAntiSpyware, it reported the same problems. This time, I did NOT click to allow it to clean up the problems it found, and when I exited SuperAntiSpyware, everything was still working.

When I got home, I checked my version and found it was ver. 4.30 so I clicked to update it. The download reported the suspected trojan among the updates, and when it was done, it reported that my files were up to date, but when I restarted it, it still showed that the version remained as ver 4.30. I scanned my machine which found no problems.

I then searched Google for "Gen-CDesc" with and without the bracketed extensions and found a lot of reports about it as a trojan. No one reported a confirmed way to remove the trojan, but most reported no destructive activity, just progressively slower performance so I told him to keep working with the system as it was, and I would research the problem further.

One thing I noticed was that the reports that included progam failures also referred to SuperAntiSpyware. I finally found one forum thread where one reply noted that the OP's log file showed an older version of the program and suggested downloading and installing the latest version, ver. 4.40. The OP happily replied that that fixed the problem.

The fix

I downloaded the new version, uninstalled ver. 4.30, installed ver. 4.40 and swept my machine again. As expected, it found no problems, but at least, it appeared to work OK.

Today, I installed ver. 4.40 on my friend's machine and swept it. I had not deleted any files so it was scanning the same files that ver 4.30 reported as infected. This time, it found no problems. :cool:

I don't know what specific conditions existed to trigger these false alarms or how widespread they are, but installing ver. 4.40 fixed the problem.
 
Last edited:

balloonshark

Diamond Member
Jun 5, 2008
7,157
3,625
136
Was this the thread? http://forums.superantispyware.com/index.php?/topic/3955-thousands-of-infections/

Whenever I see a "detection" I just assume it's a false positive and search the vendors forum, wilderssecurity or dslreports for complaints/horror stories before acting. In the past I would freak out which didn't help matters :\

Thanks for the heads up! I'll keep this in mind when I look at my friends and families machines.
 

lxskllr

No Lifer
Nov 30, 2004
60,151
10,613
126
I just ran V4.36 from my UBCD4Win disc, and it didn't find anything out of the ordinary in my XP VM.
 

Harvey

Administrator<br>Elite Member
Oct 9, 1999
35,059
73
91

No, I don't think that was the post I found, but thanks for the link. It's far more complete and descriptive of the problem, as well as the fix. I sent out a mass blast about it to my friends, and I can use it as reference if any of them asks for more info.

AFIK, this just started with one of the latest definition sets, which would explain why I didn't find that much info, yesterday.

I just ran V4.36 from my UBCD4Win disc, and it didn't find anything out of the ordinary in my XP VM.

As I noted, after dealing with my friend's problem, the first thing I did when I got home was to update the definitions in my ver. 4.30, which included the new definitions for Gen-CDesc and scan my system.

Like you, I found no problems. That does not mean the problem doesn't exist for some machines, somewhere. I saw the destruction on my friend's machine, which sent me searching for the info I reported, including the post reporting that replacing it with ver 4.40 resolved the problem.

The point is to do it before you encounter the problem, and the fix is free. I tested it on my machine and my friend's before posting it here. :)
 
Last edited:

lxskllr

No Lifer
Nov 30, 2004
60,151
10,613
126
I'm not completely sure I'm following you for the cause of the issue. Are you saying that a legitimate infection causes SAS to freak out, and delete files, or is it possibly the infection itself using SAS to delete files to be a dick?
 

Harvey

Administrator<br>Elite Member
Oct 9, 1999
35,059
73
91
I'm not completely sure I'm following you for the cause of the issue. Are you saying that a legitimate infection causes SAS to freak out, and delete files, or is it possibly the infection itself using SAS to delete files to be a dick?

The latest definitions cause the problem in older versions of SAS. SAS updated their definitions to include the Gen-CDesc group, which appears to be a legitimate trojan. The problem arises because SAS "thinks" it finds this infection in possibly thousands of uninfected dll's, but it's a false alarm. When you click the final button to remove them, it nukes all those dll's, and any apps that depend on them no longer work.

As I posted, when I installed ver. 4.40 and ran SAS again, it no longer found infections on the same files that it flagged with the previous version, ver. 4.30.

I hope that clears up any misunderstanding.
 

Ultralight

Senior member
Jul 11, 2004
990
1
76
Thanks for this. I run SAS' latest version and love it but I'll need to check a number of other systems to see what versions are installed.

Does this affect the free version as well?
 

Harvey

Administrator<br>Elite Member
Oct 9, 1999
35,059
73
91
Does this affect the free version as well?

Absolutely. My friend is running ver. 4.30 of the free version when the problem hit. The problem appears to be a catastrophic interaction between previous versions of the program and the newer definitions that include GenCDesc. Installing ver. 4.40 fixed it, and it no longer detects GenCDesc on the same files that previously caused the destructive alerts.