I just did my first thorough scan in ages (usually do a standard), but with archives omitted, and got an interesting and surprising result. This was with both the program and VPS right up to date, 4.8.1335 and 090904-0 respectively.
I was alerted that it had found Win32:Dialer-gen13[trj] in, of all places, the VRDB file, ....\integ\avast.int. It did not find any problems elsewhere on the disk. So that file got successfully moved to the chest.
I'm guessing that since nothing else was found, the infected whatever was present on my system when I last generated the VRDB (March 24th) and slipped past avast during generation, but is no longer around except for the "recovery" data for it. So I've got three questions:
1) Sound like a reasonable and likely inference I'm making?
2) If so, am I probably safe to just delete the file and generate a fresh VRDB? Or possibly it's a false positive in the current defs which others have already reported, so I don't even need to delete but can simply restore it?
3) Some time, way back when, I'd asked whether avast scanned files for which it put data into the VRDB, to ensure that the resulting VRDB was clean, and was told yes it did. If the current alert is in fact legit, does that mean we can't take for granted that the VRDB is clean?
Oh, should also mention that I haven't yet run SAS or MBAM scans, to see if maybe one or both of those turns up something elsewhere on the disk that the avast scan missed. I'll post a follow-up shortly once those are done.