Two days ago, while I was searching on Google using my Mac, I encountered a CAPTCHA. This had happened occasionally before as well, especially when I used a VPN or shortly after disconnecting from one, but it usually resolved on its own.
What’s interesting is that this issue only happens on the Brave browser. When I access Google through Safari, everything works fine. I also tested it on my phone, which is connected to the same modem. When I use Brave on my phone to search on Google, I get the same CAPTCHA issue.
I reset the modem, and although both devices get different IP addresses afterward, the issue persists on Brave. It even happens when I use mobile data on my phone. The only way to fix it is by turning off the Brave Shield for Google.
Considering all of this, it seems like the issue is Brave-related. But if that’s the case, shouldn’t other users be experiencing this too? Why would both my Mac and my phone start having this issue on the same day? The only connections between the two devices are that they both connect to the same modem and that my Mac sometimes uses my phone’s internet. Both devices have Proton VPN installed, but the VPN was not active on either one. In fact, I had never even opened the VPN app on my phone since installing it. I later uninstalled the VPN app from the phone and restarted it, but the issue persisted as long as Brave Shield is enabled for Google.
I’m also having this issue. I’ve tried everything. I’m glad it’s not just me. Now my iCloud Password chrome extension doesn’t work either, it doesn’t recognize that I have the latest MacOS update. I’ve tried changing my DNS; ensuring no VPN connection; clearing my cache, cookies, etc… nothing seems to work.
I am also experiencing this. Typically I only encounter Google’s CAPTCHA verification when I have Brave VPN enabled, however it has now started occurring every single time I attempt to access Google in a Private Window, even with the VPN disabled. For me, it seems like the issue is specifically related to Private Windows, as it only occurs there and not during normal browsing. Not sure if the same is true in your case, but that has been my experience with this issue. This is happening on both Windows and iPhone.
I wonder if its related to https://github.com/uBlockOrigin/uAssets/commit/0a48546e08e26cb524d4b11426a8262110f64d9d
Also need to clear the “SOCS” cookie, via Devtools (F12) on google.com. Let me know if this helps
Try adding into brave://adblock
www.google.*#@#+js(trusted-set-cookie, SOCS, CAESHAgBEhJnd3NfMjAyNTA2MDQtMF9SQzEaAnJvIAEaBgiAgo7CBg, 1year)
This seems to have worked for me. Appreciated.
This seems to be working for me so far on my phone. I’ll update if that changes. It doesn’t seem to be a fix for the iCloud Passwords extension though 
A fix went out today, it only affect google.com. We don’t interact in the same way with iCloud or others. Was a specific rule from uBO upstream.
Asking internally, I can reproduce.
Looks like its limited by Apple for certain devices, namely Beta or Nightly. Does it work in Brave release?
The cookies section in the devtool always seems to be empty, but when I applied the code you gave, the problem seems to be solved for now on both devices. The part that worried me was that I deleted the application data on my android device and this problem occurred on two different devices.
No need to add or change anything, its in upstream Brave now
If anyone sees any google consents, just need some testers. (remove any previous rules previously). To counter the cookie consent showing on google.
Add this into brave://adblock, custom rules:
google.com##+js(rmnt, script, cookieUpdateConsentUrl)
The CAPTCHA issue started up again on my phone. I’m using the standard version of brave and the iCloud Password extension still doesn’t function since the CAPTCHA issue began.
Any CAPTCHA issues, open shields in the url, under Fingerprinting. Unselect “Screen” (as a test). See if this helps. If you’re using a VPN, won’t stop captcha checks for that
I hadn’t seen it for 2 days and it started again.
I did what you said but it came up again.
Yeah, it’s starting to happen for me again now too. Unfortunate.