False Positive found in network UNC path?

[carlds30]

Hello we are a corporate customer and need some help with recent scan results. Yesterday during a quick scan launched from a network workstations, MBAM detected 183 files infected. The log shows the infected files all reside on server share access by UNC path, not mapped drive. The user account that launched the MBAM scan does not have access rights to the folders/files indicated as infected in the log files. I am hoping this was some sort of false positive or perhaps error in the log file??? Does MBAB support scanning UNC paths? The same files were detected in a full scan about 1/2 hr after the first quick scan both show all files as being quarantined/deleted successfully. After logging in as administrator and updating to MBAM 1.50.1.1100 and lauching a full scan nothing was decteted. I also scanned the server locally to find nothing infected. Here is a relavant section from the log file:

Malwarebytes' Anti-Malware 1.50

www.malwarebytes.org

Database version: 6340

Windows 5.1.2600 Service Pack 3

Internet Explorer 8.0.6001.18702

4/14/2011 8:18:30 AM

mbam-log-2011-04-14 (08-18-30).txt

Scan type: Quick scan

Objects scanned: 157144

Time elapsed: 5 minute(s), 30 second(s)

Memory Processes Infected: 0

Memory Modules Infected: 0

Registry Keys Infected: 0

Registry Values Infected: 0

Registry Data Items Infected: 1

Folders Infected: 12

Files Infected: 183

\\servername\users\username1\my documents\goro-goro.txt (Malware.Trace) -> Quarantined and deleted successfully.

\\servername\users\username2\my documents\goro-goro.txt (Malware.Trace) -> Quarantined and deleted successfully.

\\servername\users\username3\my documents\goro-goro.txt (Malware.Trace) -> Quarantined and deleted successfully.

[miekiemoes]

Hi,

These are "ghost" detections and are caused because of the network you are scanning from. This causes misreads in malwarebytes. We have already corrected this in Malwarebytes version 1.50.1.1100

I see you are still using the previous version. That's why I suggest you update to the latest Malwarebytes version

Let me know if you're still having the same with latest version.

Edit: I overlooked the part that you have already updated to the latest version, and there were no "ghost/misread" detections anymore