Malwarebytes Browser Guard Interferes with OneTrust CMP

[vladanp]

Overview:

We're experiencing an issue where the Malwarebytes Browser Guard extension is causing unintended interactions with our website's Consent Management Platform (CMP) implemented via OneTrust. Specifically, the extension automatically clicks the "Reject All" button whenever a new <div> is dynamically added to the DOM in our React application.

Issue Details:

• Automatic Clicks on "Reject All": Each time our React app adds a new <div> to the DOM—a common occurrence due to its dynamic nature—the Browser Guard extension triggers a click event on the OneTrust "Reject All" button.
• User Interface Disruption: This behavior causes dropdown menus, input fields, and other interactive elements to lose focus, significantly impairing user experience.
• Continuous Interference: Given that React frequently updates the DOM, this issue leads to constant interruptions, making the website difficult to use.

Request for Assistance:

We suspect that the Browser Guard extension is monitoring DOM changes and interacting with elements it deems related to privacy or tracking. We are seeking guidance on:

• Understanding why the extension is triggering clicks on the "Reject All" button upon DOM updates.
• How to configure the extension or our website to prevent this behavior without compromising user security.
• Whether there is a known workaround or if an update is planned to address this issue.

Impact:

This problem affects all users of our website who have the Malwarebytes Browser Guard extension installed, leading to a degraded user experience and potential loss of functionality.

Conclusion:

We value the security that Malwarebytes provides to our mutual users and hope to find a solution that maintains protection without hindering usability. Your assistance in resolving this matter is greatly appreciated.

Thank you for your time and support.

[JPopovic]

Hello Vladan,

What is the domain name (website name)?

[vladanp]

doodle.com

[JPopovic]

Thank you for reaching out to us with your concern.

It seems that turning off ads and trackers may resolve the issue you’re experiencing.

While I don't have a specific solution on hand that would involve changes from your side, one potential improvement could be removing the cookie banner from the DOM once the user has rejected it, as this might help.