As I turned on my laptop (def. version 140710-0), Avast immediately detected a process, marked it as a Win32:Rootkit-gen [Rtk] and deleted it.
The filepath is C:\Program Files (x86)\Realtek\Realtek PCIE Card Reader\RIconMan.exe
This file has been on my computer since it was bought, and it seems to be bundled with a majority of Hewlett-Packard Win7 laptops ( http://www.shouldiblockit.com/riconman.exe-9495.aspx) ; and I have little reason to believe it was just suddenly infected.
So I’m not 100% sure what to do, I can’t submit a sample through the normal channels, since I don’t have one to submit. Avast seriously just deleted it with absolutely no input from me. I could attempt a system restore and disconnect my internet, so my computer doesn’t download the definition update that marked the process. But I don’t know if System restore actually undoes Avast Definition updates.
If nothing else I can at least report it here and see if anyone else has experienced the same issue.
It’s not in the chest. It just straight up deleted it. I’m not sure if that’s a setting you can tell it to do? (As in: Set it to automatically deleted infected files) Because I might have done that at some point; but either way, it’s just gone from my computer now.
You can use mail
send to virus@avast.com in a password protected zip file
mail subject: False Positive / undetected sample (select subject according to your case)
zip password: infected
S’alright. I did a system restore and disconnected my internet. Defs didn’t update so I quarantined it.
Actually, I scanned it with both the old definitions and the most recent ones. Both say no virus. Weird. Why was it detected in the first place, then?
I’ll keep it in the chest for now while I download the windows updates I downloaded before the restore. Maybe the updates caused avast to wig out about that process?
Avast is the only one marking it as a virus, though right now avast says it’s clean in my virus chest. Will update windows and report back and see if that changes anything.
Shouldn’t need to worry about it. Ran another virustotal with Avast’s new definitions and it’s not pinging as a virus anymore, both in virustotal and an actual avast scan of the file.
Bit of a hassle that I had to system restore to get the file back, but, oh well.