Avast is currently flagging a file called mscorlib.ni.dll as Win32:Spyeye-BG (exact location: C:\Windows\assembly\NativeImages_v2.0.50727_32\mscorlib\62a0b3e4b40ec0e8c5cfaa0c8848e64a\mscorlib.ni.dll) on two of my computers (both running Windows 7). As one of these computers was clean last night (ran quick scan and full scan and both were clear) and the other has not been used for several days I suspect that this is an FP. The fact that the ‘last modified’ timestamp on the files in question corresponds in both cases with the installation of last week’s Windows updates on the computers would also seem to support this.
Am I right to think that this is a false positive?
I can’t access the folder C:\Windows\assembly\NativeImages_v2.0.50727_32. When I type the address in I get a message saying that Windows can’t find it. I suspect that it may be because it’s in the Assembly folder.
It is created on the fly from mscorlib.dll, so it is only there for a short time, if you don’t send it to the chest and just block, the file would disappear anyway.
There has just been another VPS update 110302-0, so I don’t know if that resolves this problem.