Avast block Tightvnc

Avast Free Antivirus / Premium Security
1

Hi,
Since VPS 621-0 Avast block tightvnc service. It detect win32-Radmin-B[Tool] but tightvnc is ok.
Why is tightvnc detected as a malware?
Is there anybody else with the same problem?

Thanks

2

See this Topic - http://forum.avast.com/index.php?topic=21246.0 same detection and tightvnc.

3

Thanks for your rapid answer.
I had adding the winvnc path in excluding list but this is not a normal thing, I think.
Many persons on my office have the warning and are afraid and then contact me.
So is there a chance for this will be corrected on next VPS?

4

Yes it has… or, at least, in the next two, three updates ahead…

5

This problem is back with the latest update.

A few hours ago I received VPS 0645-0 and now tightVNC is detected.
I tried to add c:\program files\tightVNC to the exclusion list but that didn’t seem to help.

6

Same here… my only option is to shut down avast services before running it and then to keep telling Avast to take “No Action” when it complains… very annoying to say the least.

7

Same problem here with tightvnc 1.2.9 for win 32 and espescally WinVNC.exe from it.
Winvnc is identified as Win32.Trojan.gen if i remember well.
A solution ?
Thank’s

8

Then you need to send it to avast as a false positive as before (Mini Sticky) False Positives, how to report and what to do to exclude them until the problem is corrected.

If that is your exact entry in the Exclusions, then it won’t work.
c:\program files\tightVNC* should work but that wildcard use leaves a security hole, you should indicate the file name that is being detected not the wildcard example above.

9

Telling avast to take No Action shouldn’t work as No Action doesn’t mean ignore but, take none of the actions listed in the alert, e.g. Repair, Move to Chest, Delete, etc. However, even if you click the No Action avast shouldn’t let the suspected infected executable run, you need to add it to the exclusions lists.

10

As David said, the actions are valid for that session only.
To add it to the exclusions lists, please:

For the Standard Shield provider (on-access scanning):
Left click the ‘a’ blue icon, click on the provider icon at left and then Customize.
Go to Advanced tab and click on Add button…

For the other providers (on-demmand scanning):
Right click the ‘a’ blue icon, click Program Settings.
Go to Exclusions tab and click on Add button…

You can use wildcards like * and ?.
But be carefull, you should ‘exclude’ that many files that let your system in danger.