Jump to content

Greybeard1

Members
  • Posts

    14
  • Joined

  • Last visited

Posts posted by Greybeard1

  1. Thanks Porthos. Apologies for posting in the wrong section.

    I've done that and tested it (having put LibreOffice back on the Protected list) and it flags an exploit as before. I didn't see any control ticks change when I restored the defaults.

    However, I haven't explore that area of Settings previously, and I notice the 3rd tab is "Application behavior protection" and includes a control in the "MS Office" column for "Office Spawning Batch Command Prevention". I turned off that control and and that does prevent an exploit being flagged.

    So it appears that control applies to other Office suites, not just MS Office. I assume it's a narrower exemption than taking protection off LibreOffice completely, which I think is better. Do you know if that's the way Malwarebytes is intended to work, or should it be possible to respond to the nature of the macro rather than react to it as a Spawning Batch Command? I can see from the log that cmd.exe was called so understand that it literally is a spawned batch command.

  2. Malwarebytes is flagging an exploit when attempting to run a macro in LibreOffice. Invoking the menu command Tools > Macro > Run Macro on a newly created blank text document or spreadsheet with only the built in macros will cause the application to close and the exploit to be flagged. This happens before selection of a macro to run.

    This occurs on a two separate new installations of LibreOffice 7.3.4, downloaded from https://www.libreoffice.org/download/download/?type=win-x86_64&version=7.3.4&lang=en-GB. SHA256 string of the downloaded file matches the target. Macro protection settings in the application do not affect the outcome.

    Saving a blank file and adding it to the Allow List in Malwarebytes does not prevent the behavior.

    I attach a typical log and zipped .odt file - the issue may be in the application itself, which I have not attached but can be downloaded as above.

    I have turned off LibreOffice in the Protection Applications list but see that as a temporary workaround.

    Thanks.

    mwb libre.txt LibreOfficeblank.zip

  3. Malwarebytes has reported m32-471-rc.exe, a 2009 version of Mercury Mailserver as MachineLearning/Anomalous.100

    Mercury is well respected software and no malicious activity was detected when I used this version, so I think it's a false positive. Log and zipped detected file attached.

    Reporting as feedback to detection engine; the file is redundant so whitelisting is moot.

    m32-471-rc.zip fp_mercury_mailsvr.txt

  4. Hi,

    I reported a false positive in Tessaract-OCR in January, which was confirmed. I have recently had the same false positive, plus two more from Tessaract (I have not changed my installation). Since they were connected, I reported the recent events on the same thread, but maybe that was the wrong thing to do as there has been no response.

    The thread, with attachments for the new event, is here

    Thanks

  5. Hi,

    Malwarebytes routine scan has reported Malware.AI in dawg2wordlist.exe, one of the supporting files for the Tessaract OCR software. As a minor and little used part of a long standing and reputable program my guess is that this is a false positive, please could you check?

    I can attach the file or provide the source I downloaded from if required

    Thanks, Chris

     

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.