yahelite

[malpark]

  recently yahelite chat program was hacked and an unauthorized build was placed in it. it was a 325.5 build and most anti virus programs showed it as a trojan, the prorammer made a new build to 326.6 and it worked fine for a few days then avast showed it as a trojan, it's not a trojan, is ther anyway you can allow this programme with avast? what people are doing is going to his site and downloading 326.4 build which was before all this happened and it works ok, he has closed the yahelite forum and will reopen it in october

[wyrmrider]

you can exclude from detections
I have to run but you could also upload to virustotal for a double check first
you can send to virus@avast.com zipped and password protected with the password in the message body and a note about possible false positive

some one else may pick up the thread from Europe a little later

[malpark]

how do you exclide yahelite from the detectopns in avast?
 

[malpark]

detections 

[DavidR]

First and foremost confirm the detection.

You could also check the offending/suspect file at: VirusTotal - Multi engine on-line virus scanner and report the findings here. You can't do this with the file securely in the chest, you need to extract it to a temporary (not original) location first, see below.

Create a folder called Suspect in the C:\ drive, e.g. C:\Suspect. Now exclude that folder in the Standard Shield, Customize, Advanced, Add, type (or copy and paste) C:\Suspect\* That will stop the standard shield scanning any file you put in that folder. You should now be able to export any file in the chest to this folder and upload it to VirusTotal without avast alerting.

If it is indeed a false positive, see http://forum.avast.com/index.php?topic=34950.msg293451#msg293451, how to report it to avast! and what to do to exclude them (what you are asking, but shouldn't be done until confirmed as an FP) until the problem is corrected.