Jump to content

frozen

Members
  • Content Count

    250
  • Joined

  • Last visited

Community Reputation

0 Neutral

About frozen

  • Rank
    True Member

Recent Profile Visitors

4,936 profile views
  1. Another day another false positive of a file I have had on my hard drive since 2008 Malwarebytes www.malwarebytes.com -Log Details- Scan Date: 2/11/21 Scan Time: 2:36 AM Log File: 3a8d9690-6c44-11eb-a771-90e6ba57cdd5.json -Software Information- Version: 4.3.0.98 Components Version: 1.0.1157 Update Package Version: 1.0.36957 License: Premium -System Information- OS: Windows 10 (Build 19041.804) CPU: x64 File System: NTFS User: System -Scan Summary- Scan Type: Threat Scan Scan Initiated By: Scheduler Result: Completed Objects Scanned: 3577
  2. Over the past several months Malwarebytes has been flagging decades old files as malware during its scheduled scans. Rather than report the issue I simply told MBAM to quarantine or delete the file and get on with my day. Today I downloaded an update to a piece of software I used regularly QuickAccess Popup https://www.quickaccesspopup.com/ and the download was fine. I unzipped the file and ran the EXE. No problem. Then the scheduled scan popped up the following detection. Malwarebytes www.malwarebytes.com -Log Details- Scan Date: 2/8/21 Scan Time: 8:04 AM Log File: 98
  3. It is still flagging putty.exe here today. I has not done so in the past with me. Malwarebytes www.malwarebytes.com -Log Details- Scan Date: 9/1/20 Scan Time: 8:11 AM Log File: 95487764-ec54-11ea-8acc-90e6ba57cdd5.json -Software Information- Version: 4.2.0.82 Components Version: 1.0.1025 Update Package Version: 1.0.29307 License: Premium -System Information- OS: Windows 10 (Build 18362.1016) CPU: x64 File System: NTFS User: System -Scan Summary- Scan Type: Threat Scan Scan Initiated By: Scheduler Result: Completed Objects Scanned: 331590
  4. Adding "C:\Program Files\Mozilla Firefox\firefox.exe" as an exclusion to Ransomware and re-enabling Ransomware detection in MBAM allows me to run FIreofox even from the profile on D Drive. That is probably until the the next firefox update I guess.
  5. I just noticed that MBAM is still blocking FIrefox.exe from running. The EXE is still there on the hard drive. I had to close MBAM to run the program. There is s of course nothing inin quarantine. THis is because MBAM did a RTP detection on it. I guess I will have to disable Ransomware altogether in MBAM. If I do then Firefox is allowed to run, Same thing happens if MBAM is closed altogether.
  6. Same thing here. I have been updating FIrefox without issues until April this year and was always using the profile on D drive. Only since then have I had to use the C profile to do the update I bet if I leave FIrefox alone for a day or so I will again be able to use the profile on D drive again without any repercussions from MBAM. At least that was what I experienced earlier this month.
  7. What is weird is that if I perform the update while using the D drive profile MBAM first flags Updater.exe when FIrefox is restartred after the update. Then MBAM simply terminates FIrefox upon restarting Firefox. None of this behavoir occurs when I use the C drive profile.
  8. The problem occurs in my case when I use my normal profile which is stored over on D drive. If I use the profile that is over on C drive (which is a copy of the files I made from the D drive profile) the problem does NOT occur.
  9. I am just glad I am not the only one seeing this behaviour. It was lonely here for the first 3 months
  10. Another Firefox update today. I started FIrefox using the profile that is stored on D: rather than the normal C: partition update came down via Help | About clicked on the restart Firefox after the update was applied and whamo Malwarebytes www.malwarebytes.com -Log Details- Protection Event Date: 7/29/20 Protection Event Time: 9:52 AM Log File: 20da2f3a-d1ab-11ea-bcb0-90e6ba57cdd5.json -Software Information- Version: 4.1.2.73 Components Version: 1.0.990 Update Package Version: 1.0.27635 License: Premium -System Information- OS: Windows 10 (Build 18362.959)
  11. It sure looks like there is an issue with MBAM Ransomware module since disabling it does not cause this behavior with the profile on the other partition. Even after updating MBAM with Ransomware enabled using the profile on another partition Firefox got shutdown. Malwarebytes www.malwarebytes.com -Log Details- Protection Event Date: 7/1/20 Protection Event Time: 2:17 PM Log File: 8cac3786-bbcf-11ea-81a1-90e6ba57cdd5.json -Software Information- Version: 4.1.2.73 Components Version: 1.0.972 Update Package Version: 1.0.26255 License: Premium -System Inform
  12. Sigh this is getting old very quickly. Another Firefox update. This time I started FFox with a profile whose extensions are identical to the other other profile I normally use. I updated from 77.0.1 to 78.0.1 restarted FIrefox and everything seemed fine. Firefox was not squashed by Malwarebytes. Closed Firefox. Started it back up this time with my normal profile that is stored on another partition. Whamo Firefox was blocked from running. It was not quarantined but simply blocked. The shortcut on the desktop top would not work saying that I did not have sufficient rights. I closed MBAM and
  13. Like all the previous times before if Ransomware in MBAM is enabled and I start FF up with the profile stored on C:\ which has all the files from the problem profile Firefox is not quarantined/ affect by MBAM.
  14. Why is my notifications in MBAM say Thursday? It is still Wednesday here in Canada and this event at 7:23PM is me updating to Firefox 77.0.1. Also why is it saying it quarantined the threat when in fact there is noting in quarantine in MBAM?
  15. It is indeed Ransomware protection in MBAM that is causing this. I saw a new story that Firefox released 77.0.1 today so I checked via Help | About and Firefox downloaded the update and required me to restart. Up until this time Ransomware in MBAM was enabled yes enabled. Before I clicked on the button on the FF update screen to restart the browser I turned off Rasomware protection in MBAM and then allowed FF to restart. FF started up and ran fine. I close down FF went to MBAM and enabled Ransomware protection. MBAM said it had quarantined firefox.exe yet when I went to MBAM quarantined screen
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.