Avast Detecting Itself as an Infection

Hi,

We are using ADNM

Starting on 3/3/10, avast has consistently detected a number of it’s own processes as “Win32:Hybris-44 [Drp]” across our network and attempts to delete them, unsuccessfully. At least if it does manage to delete them, they start back up. The culprits are as follows:

aswWebSv.exe
avAgent.exe
aswServ.exe

I’m pretty sure these are false positive, so what steps can we take right now - i.e. do we need to wait for an update that fixes the problem, or is there something we can do to alleviate the issue. Also, what could cause this to happen? This isn’t the first time Avast has targeted itself, although at other times it usually targeted one of its files (which turned out to be uninfected)

Thanks for your help!

They seem fake:
ashServ.exe
ashWebSv.exe
should be good.
Also, the avAgent.exe seems infected.
Where are the file located?

I think that the correct file names may well begin with asw not ash as this is uses on some of the server based versions, I don’t know if that is correct in the ADNM though.

However, as Tech asks the key is the location of the files.

All processes have the path to the "\Program Files\Alwil Software\Avast4" directory, so that’s good.

Can either of you confirm that the ‘asw’ prefix is the correct one for ADNM? That is the prefix for the processes that are running on our systems.

Sorry I can’t confirm it as I don’t use the ADNM product.

Are they still being detected ?
If so - check the offending/suspect file at: VirusTotal - Multi engine on-line virus scanner and report the findings here the URL in the Address bar of the VT results page. 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.

Are there associated ash versions of these files in the avast4 folder ?

No, there are no ash version in the avast4 folder.

I was a little over-eager to continue this thread this morning, and I neglected to check if Avast was still detecting problems with itself; it is not. I tested the files on virus total as well, and they are all clean:

aswWebSv.exe: http://www.virustotal.com/analisis/ed1853d8342c679daeeb6ba7dead6dcb4fc9c54e949495136d26971e260f0363-1268075105
avAgent.exe: http://www.virustotal.com/analisis/84cc29618899873d0eb710c1d347dc903c5ac6f8468a8a4f6c8198a44f473ce9-1268075182
aswServ.exe: http://www.virustotal.com/analisis/3bd9340fc865e6e55e9924aaa737d2ccbbb0b0f45b031af07cf222ce0cda0e53-1268075367

Thanks for your help!

You’re welcome.

OK, so it looks like the ADNM version uses asw prefix, one down.

I don’t have avAgent.exe, so I’m guessing that is specific to the ADNM (acting as an agent) version, two down.

The VT results are good, so it looks like this was a VPS Update hiccup that was quickly corrected, three down.

Looks like your good to go.