Jump to content

PEACE has been detected as Malware


Sitedrifter

Recommended Posts

The audio equalizer I use called PEACE was detected as malware today after upgrading to the latest version.

 

Malwarebytes
www.malwarebytes.com

-Log Details-
Protection Event Date: 5/3/19
Protection Event Time: 6:04 AM
Log File: d5a12ea4-6d8a-11e9-8a05-c07cd1fbefdf.json

-Software Information-
Version: 3.7.1.2839
Components Version: 1.0.563
Update Package Version: 1.0.10442
License: Premium

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

-Blocked Malware Details-
File: 1
Generic.Malware/Suspicious, C:\EqualizerAPO\config\Peace.exe, Quarantined, [0], [392686],1.0.10442


(end)

 

https://sourceforge.net/projects/peace-equalizer-apo-extension/

 

I hope this is a false positive.

 

 

Thanks

PeaceSetup.zip

Link to post
Share on other sites

  • Staff

 

Hi,

This is most probably a caching issue, so Quit malwarebytes from the systemtray.

Then navigate to the following folder: C:\ProgramData\Malwarebytes\MBAMService

In there, locate the file HubbleCache and delete it.

Restart Malwarebytes again. A new Hubblecache will then be created again, so it will properly pick it up and remember to not detect this anymore.

 

Link to post
Share on other sites

Same issue

 

1. I removed the file from quarantine

2. I quit malwarebytes

3/. I deleted the Hubble file

4. restarted Malwarebytes

5. Executed the program PEACE and got the same thing (see below)

 

 

Malwarebytes
www.malwarebytes.com

-Log Details-
Protection Event Date: 5/3/19
Protection Event Time: 9:00 AM
Log File: 7044efd2-6da3-11e9-bead-c07cd1fbefdf.json

-Software Information-
Version: 3.7.1.2839
Components Version: 1.0.586
Update Package Version: 1.0.10446
License: Premium

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

-Blocked Malware Details-
File: 1
Generic.Malware/Suspicious, C:\EqualizerAPO\config\Peace.exe, Quarantined, [0], [392686],1.0.10446


(end)

Link to post
Share on other sites

  • Staff

Thanks.

This should work again now. No need to update the database as this takes immediate effect already anyway.

Please wait for about a 10 minutes, just in case. If still being detected, then it might be the caching issue (as some ISPs do proxy-caching), so just delete the hubblecache again then for it to take immediate effect.

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.