or you can do it by mail
Put the file(s) in a password protected zip.file and send to virus @ avast.com
mail subject: False Positive
zip password: infected
you may add a link to this topic
Hi essexboy & Pondus,
If it is being reported and found to be a false positive detection, avast is known to solve these issue sometimes with a coming update. As it is a general detection for the Win32:Malware family the possibility of an eventual FP is there. Sometimes the protection in Punkbuster could be a tad aggressive. Bitdefender had a similar issue with punkbuster’s pbcl.dll and flagged that as a generic trojan. That was a fortnight ago,
polonus
Thanks essexboy, the files aren’t showing up in the chest, the File System Shield is picking them up though.
Reported the issue back to base,
polonus
Definition update just released
When will we get this cos I cant get at it? Current version 120621-1
@ZiiPMicJules
You can always update Engine and Virus definitions manually also, you do not have to wait for it to land there automatically,
polonus
Tried that - nothing updates
Tried manual update too, but there are no new defs to update 
Maybe there’s some waiting period.
Will try later, and THANKS guys for your help in resolving this issue.
Best wishes 
Many thanks chaps for all your help.
also getting punkbuster issues from from avast today
I have removed Avast for now and will try another AV
I hate to appear thick (wont be for the first time) but where are the “real time shields”?
I cant seem to find them!!!
Come on Avast, get this sorted, it has to be a simple fix!!!
Not too hard to find, just open the avastUI (click on the avast! tray icon) Real-Time Shields, then click the Expert Settings button, Exclusions.
The FP is due to the nature of the Punkbuster program. There were previous avast FP for Punkbuster, detecting it as Win32.Rootkit.gen[Rtk]. That was back in 2008, so the developers may have forgotten about that incident.
Gamers should know the average av solution can come up with these FPs once in a while with generic detection and report these FPs en masse. Developers should be aware too, but the occasional FP may slip through, as was the case here,
polonus
so was the newest update supposed to fix it? cause mine is up to date but still getting kicked 
Did someone say they were going to fix it? If they didn’t, I’d guess “no.” I’d also guess that because it’s friday night, we’re waiting until -at least- monday before they look–if then.
…if it’s free, you’re not a customer, you’re an advertising channel, and not a very important one, right Avast?
Dudes–you’re pissing off thousands of people at least, there will be an impact downstream, and the longer you wait to notice you’re doing it, the bigger the impact will be. Like others have already posted, seriously considering uninstalling Avast, as nothing else seems to work.
Hello? Bueller? Anyone?