Jump to content

False-Positive: Malware.Ransom.Agent.Generic -> Excel.exe / Winword.exe


Recommended Posts

Hi,

we got 2 different detections in the past 2 weeks on two different clients. Today it was:

1)
Malware.Ransom.Agent.Generic
C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Excel.lnk
Blocked By Real-Time Protection

2)
Malware.Ransom.Agent.Generic
C:\Program Files\Microsoft Office\root\Office16\EXCEL.EXE
Blocked By Real-Time Protection


One or two weeks before before it was "Winword.exe" on a different client.
The Product had to be repaired - restoring the .exe did not work.

This is urgent, because just restoring out of quarantine does not work.

Regards,
Daniel

Link to post
Share on other sites
  • 2 weeks later...

Please look into this. I just had the same issue last night. Here is the log:

"Malwarebytes
www.malwarebytes.com

-Log Details-
Protection Event Date: 7/6/20
Protection Event Time: 1:58 AM
Log File: c31482ca-bf4d-11ea-b297-ace2d34b2fcc.json

-Software Information-
Version: 4.1.0.56
Components Version: 1.0.955
Update Package Version: 1.0.26449
License: Premium

-System Information-
OS: Windows 10 (Build 18362.900)
CPU: x64
File System: NTFS
User: System

-Ransomware Details-
File: 1
Malware.Ransom.Agent.Generic, C:\Program Files (x86)\Microsoft Office\Office12\WINWORD.EXE, Blocked, 0, 392685, 0.0.0


(end)"

I know it's not malware because I have a tight firewall & its a legit program I use every day. I also have Bitdefender running with Malwarebytes.

 

To fix this issue, I had to restart my computer 2-3 times and repair Microsoft word using Microsoft's repair function within the installer. Please look into this guys!  Much Appreciated!

Link to post
Share on other sites
  • Staff

Unfortunately, the beta only applies to the consumer version, however until the issue is resolved you should be able to either create exclusions or disable the shields for MS Office until the issue has been resolved by the Developers.  As I said, the aforementioned link has the latest information on this issue, and the fact that they have a beta which addresses this issue means a publicly available fix shouldn't be too far behind assuming testing of the beta goes well.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

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.