hab auch grad danach gesucht und bei NAI folgendes gefunden:
When Virex 7.5.1 attempts to scan a file, (either via an on-demand, active scan, etc.), there are occasions when Virex will be unable to successfully complete this operation. This can happen if the file is in use and locked by another application or if the file is a 'special' file.
Locked files generate an error 2:
VShieldCore reports: [ActiveScanner] AV Engine reports object /Library/Caches/com.apple.LaunchServices.LocalCache.csstore~)[accessed by process 449] could not be scanned due to error 2
In this scenario, Virex 7.5.1 is denied access to the file by the Mac OS X operating system. This could be because the file is being modified or is held in use by another application. If you suspect this is the case, try quitting some open applications and retry the scan.
Special files generate an error 10:
VShieldCore reports: [ActiveScanner] AV Engine reports object (/dev/null)[accessed by process 438] could not be scanned due to error 10
A special file can be a number of things - including critical Mac OS system files and also objects which are not really files at all but which appear to be files to certain applications such as Virex. In general, quitting applications and retrying the scan will not help to get these items scanned. These errors are normal and expected behavior.