This started yesterday with a reboot request after Norton Security 22.5.5.15 performed a scan it informed me that backdoor.regin was located in a Malwarebytes temp file. It was located in the root of Malwarebytes/00001263.temp. Rebooted
After posting in MBAM forum I was told as per below this is a Norton issue of false positives and Norton creating the temp file again.. "The issue you report has been a longstanding problem with Norton.
There are many threads about it, such as HERE and HERE
It has been discussed at the Norton forums, as well, HERE and HERE
The problem is with Norton, not with Malwarebytes...."
Today after a update and a quick scan malware was again found in the root of Malwarebytes in a temp file. Details below:
Filename: 00013676.tmp
Threat name: Trojan.Killproc!genFull Path: d:\utilities\malwarebytes anti-malware\00013676.tmp
____________________________
On computers as of
1/24/2016 at 2:01:52 PM
Last Used
1/24/2016 at 2:03:52 PM
Startup Item
No
Launched
No
Threat type: Virus. Programs that infect other programs, files, or areas of a computer by inserting themselves or attaching themselves to that medium.____________________________
00013676.tmp Threat name: Trojan.Killproc!gen
Locate
Very Few Users
Fewer than 5 users in the Norton Community have used this file.
Very New
This file was released less than 1 week ago.
High
This file risk is high.
____________________________
Source: External Media
Source File:
00013676.tmp___________________________
File Actions
Infected file: d:\utilities\malwarebytes anti-malware\ 00013676.tmp Removed
____________________________
File Thumbprint - SHA:
acc53e005ce702390562f76ec810ed2c7dab40394c61a6f91745a00378867cca
File Thumbprint - MD5:
Not available
SO why is NS creating a temp file in the root of Malwarebytes and as per MBAM forum, is it a NS issue/problem and what is the cure for this or is it a issue of needing a new patch to correct this issue/problem ??? Should I configure Norton not to scan MBAM DIR ?
Tons of fun.............