Basically I have a strange issue with avast. Namely, there is an executable file on my system that when I try and open avast reacts to as if it is infected. However when I manually scan the file either in the virus chest or restored (right click → scan) avast reports that it’s perfectly clear. So I want to ask if this is some sort of expected behavior? As in, why can’t avast detect the virus on a scan but apparently can when it opens. And which of the results is right? Is the file infected or not?
This is the first time I have had this situation with either the file or avast.
Have to scanned the file from virustotal? If you did, post the link here and an expert will assist you? Did you run a full system scan from Malwarebytes Antimalware? If MBAM didn’t detect anything? Use the method followed here https://forum.avast.com/index.php?topic=53253.0
Whilst I waited for a reply I scanned it with http://r.virscan.org and the site said it was fine. (results)
Malwarebytes Antimalware also reported it as clean. Although I am yet to run a full system scan over it. (I will later today since I am in a hurry now.)
As for virustotal I just went and scanned it. Here are the results.
Also, as I said the regular virus scan with avast it self also reports it as negative. That’s the main question I have really. Why is avast giving me conflicting results on this thing?
That’s the thing. I am not sure if it is a false positive or not. That’s basically what I came here to ask.
I am a bit more sure now but again, I am basically scared of there being something that only appears when the file actually executes. As a computer programer my self I can imagine ways to write programs that will behave that way. And the question is how and if this will be detected before execution if that is the case with my file.