gonzo

From reading this, I'm not sure that you understood how we handle trackers completely. Perhaps I am wrong, but it doesn't hurt to try using different words. We block those (and many other) trackers at all times. If the functionality of the code that runs your website is dependent on those trackers in any way, there will be a problem when ad blockers are used. In most cases, the complaints that people have about advertisers targeting them -- making them feel like they are being stalked -- is because of trackers. If you are going to use a consultant, I want to make sure that you have the clearest picture possible so that any money spent is spent wisely.

Whitelisted!

A tracker can be used in multiple ways. The way that you are using it is in need of change, because the guidance provided to you so far only works for you and has no benefit to any potential customers of yours. A tracker can be a way of keeping track of a path that has been followed or a selection that has been made (hence the name). That is often misused and is considered an invasion of privacy by many. As mentioned, Browser Guard blocks trackers specifically for that reason. Another way a tracker can be used is the way you are using it. It is essentially a bridge tollbooth, and clicking the link pays the toll. If the gate on the tollbooth does not rise, you can not drive across the bridge. Your ability to conduct business should not be determined by the tracker. For reference, the trackers blocked on your site are the most commonly blocked trackers of all, and are blocked by many programs like Browser Guard, and not just Browser Guard.

Its good now.

Dev sides with you. Go for it. If you get it again, hit the Check For Updates link to load fresh databases.

If I can't get what I need to investigate further, probably not.

You can turn off malware protection, but if it is not a false positive, you may get malware. That is your call. I would not recommend it though.

It looks like you were following some posting, and I think that posting is at the heart of this. The question is which one...

@Spirituality1, THANK YOU. Can you post your log to go with that. I want to see if there is a md5 hash associated with that, and if it is the same one. This will likely have to go to the developer, so I want to not be a nuisance to him or to you. Also, exactly how did you make the block occur?

The upgrade should occur automatically. I am hoping they just got around to notifying you, as I don't see any types of blocks.

If a login is required, please send a screenshot that shows the block as it occurs. The log that you sent me is showing a md5 hash for the block you originally reported. I need to get with the developer to find out more there, but I was hoping to get evidence that determines whether the block you are seeing is legitimate or a false positive. So far, it is unclear.

Having went as far as adding an item to the cart and going to checkout, I did not encounter any issues. The problem that appeared in checkout was corrected by a hotfix on Thursday. A big problem is that people complain about a "block" but the term when used generically means virtually nothing. There are dozens of block types, and each is unique. We need to know how something is blocked in order to verify the block, and to troubleshoot it when appropriate. If you can find out more, it would be appreciated.

If you will provide a specific link (or search topic on that site) to follow that gets blocked, I will take a look. Otherwise, we are in the middle of a very nice three-day holiday. Your choice.

Have you tried putting affected sites on your ALLOW LIST for scam protection?

According to internal changelog, this was fixed by 2.3.18.

On 17 February 2022, we released Malwarebytes Anti-Ransomware Beta 10 version 0.9.19.73 with Component Update package version 1.1.459. The changelog for this build can be found below: Performance/protective capability: Corrects a deadlock which affected Anti-Ransomware operations Corrects a situation which resulted in a Anti-Ransomware crash

The site has been whitelisted. Please allow 15-30 minutes for changes to take effect. Sorry for the inconvenience.

It appears that a login is required. Due to that, you will need to provide screenshots. Blocks must be confirmed, and websites must be tested to assure no hidden dangers.

Awesome, and we all survived!

@jparker86, You were the lone non-Shopify checkout that was being affected (and reported it). Can you confirm your checkout process is now working as it should?

Available now for Chrome, Edge and Firefox browsers. All Browser Guard users will get this automatically the next time Browser Guard checks for program updates.

I have whitelisted the site. Please allow 15-30 minutes for changes to take effect. The reason for this block is that excessive notifications are a common practice in websites specifically designed to scare you into performing activity that benefits a scammer. Slowing them down or incorporating informative dialog into a webpage that is not using the browser's notification API would be beneficial. One more item here...you have a ecommerce site, and we are currently awaiting a hotfix release for Chrome browser users to fix suspicious activity blocks that are false positives. The hotfix has been submitted to Google, and we (and many customers) are waiting. Firefox users who use Browser Guard have an automatic update available to them already. Malwarebytes Premium users and non-Malwarebytes users are not affected by this problem. I am telling you in case it ends up being an issue for you. I expect the hotfix to be available to Chrome users by (my) tomorrow at the latest. Its already tomorrow for you!

How is it blocked? I am on your site right now. Your image is broken, so all I have is the extremely limited description which you have provided.

The Firefox hotfix is released. Firefox/Browser Guard users will automatically update the next time BG looks for updates, or can use the link I provided to do it immediately. Chrome users are waiting for approval from Google before the new version becomes available. I removed the image from your forum post, as there are dozens of identical images already posted for this bug.

It is a known bug in Browser Guard, affecting only Browser Guard users. A hotfix is already available for Firefox, and will be available shortly for Chrome. Google must approve the new version first. See this post for Firefox users: https://forums.malwarebytes.com/topic/283962-hotfix-version-2318-shopping-bug/ Chrome fix is coming soon.