On iMac running Lion (current version)
I am getting strange lists of files to be deleted from Quarantine Manager (V 8.0.4C)
Jun 11...
Threat: Mal/Phish-A
This thread was automatically locked due to age.
On iMac running Lion (current version)
I am getting strange lists of files to be deleted from Quarantine Manager (V 8.0.4C)
Jun 11...
Threat: Mal/Phish-A
> Original Locations:
> /Library/Preferences/com.sophos.sav.plist,
> /private/var/db/launchd.db/com.apple.launchd/overrides.plist,
> /private/var/db/ntp.drift,
> /System/Library/Framworks/CoreServices.fra…work/Versions/A/Support/SFLSharedPrefsTool,
> /usr/lib/system/libremovefile.dylib,
> /usr/share/icu/icudt46l.dat
Do you still have those paths in the Quarantine Manager? I thought the paths had already been replaced with the correct locations?
The response to why they originally flagged those locations is "Possibly memory corruption, which is fixed by a reboot." The problem here is that the issue has not been reproducable to date and we've seen such a small number of incidents that we haven't been able to isolate the variables.
If you're still seeing them in the Quarantine Manager, if you forcibly remove them from teh quarantine manager and re-scan, the detections should either go away or show the proper location.
The one thing I *have* noticed from all occurances of this issue is that the files flagged as malicious are the ones that would have been most recently accessed at the time the detection was flagged.
> Original Locations:
> /Library/Preferences/com.sophos.sav.plist,
> /private/var/db/launchd.db/com.apple.launchd/overrides.plist,
> /private/var/db/ntp.drift,
> /System/Library/Framworks/CoreServices.fra…work/Versions/A/Support/SFLSharedPrefsTool,
> /usr/lib/system/libremovefile.dylib,
> /usr/share/icu/icudt46l.dat
Do you still have those paths in the Quarantine Manager? I thought the paths had already been replaced with the correct locations?
The response to why they originally flagged those locations is "Possibly memory corruption, which is fixed by a reboot." The problem here is that the issue has not been reproducable to date and we've seen such a small number of incidents that we haven't been able to isolate the variables.
If you're still seeing them in the Quarantine Manager, if you forcibly remove them from teh quarantine manager and re-scan, the detections should either go away or show the proper location.
The one thing I *have* noticed from all occurances of this issue is that the files flagged as malicious are the ones that would have been most recently accessed at the time the detection was flagged.