Jump to content

kstev99

Members
  • Content Count

    18
  • Joined

  • Last visited

About kstev99

  • Rank
    New Member
  1. Malwarebytes www.malwarebytes.com -Log Details- Protection Event Date: 8/2/18 Protection Event Time: 11:18 PM Log File: 51469d66-96d4-11e8-925e-1c872c6044b0.json Administrator: Yes -Software Information- Version: 3.5.1.2522 Components Version: 1.0.391 Update Package Version: 1.0.6179 License: Premium -System Information- OS: Windows 10 (Build 17134.165) CPU: x64 File System: NTFS User: System -Blocked Website Details- Malicious Website: 1 , , Blocked, [-1], [-1],0.0.0 -Website Data- Category: RiskWare Domain: api2.poperblocker.com IP Address: 52.202.186.208 Port: [62705] Type: Outbound File: C:\Program Files\Firefox Nightly\firefox.exe (end)
  2. Strangely after re-booting it is no longer being identified as ransomware. When the ransomware was flagged, my steam client was downloading a large update. Not sure if that could be related or not, but it seems ok now. I have tried attaching the file as both a ZIP and RAR file, size around 10MB, but after the uploading progress bar reaches 100% I get an error every time that reads: There was a problem processing the uploaded file. -200
  3. This morning MBAM removed nexus.exe from my system. When I searched I found that the same thing happened to nexus.exe back in April 2017. It's Back!! -Log Details- Protection Event Date: 7/28/18 Protection Event Time: 10:52 AM Log File: 2b7892e2-927e-11e8-afd2-1c872c6044b0.json Administrator: Yes -Software Information- Version: 3.5.1.2522 Components Version: 1.0.391 Update Package Version: 1.0.6105 License: Premium -System Information- OS: Windows 10 (Build 17134.165) CPU: x64 File System: NTFS User: System -Ransomware Details- File: 1 Malware.Ransom.Agent.Generic, C:\Program Files (x86)\Winstep\nexus.exe, No Action By User, [0], [392685],0.0.0
  4. I am having the same problem. Tried closing down MBAM and restarting. Still says I am out of date, but clicking updates does nothing. I see someone else repeated this post, so the problem is apparently on Malwarebytes end and not the user.
×
×
  • 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.