reCAPTCHAs Detecting SeleniumBase After Chrome Update 132

[ALIMURTAZAAMJ]

Hello everyone,

I’ve noticed a persistent issue after updating Chrome to version 132 while using SeleniumBase for automation. It seems that reCAPTCHA is consistently detecting SeleniumBase and showing captchas for every Google search. This behavior wasn't as frequent before the update.

I’ve already tried:

Rotating user-agents using --user-agent but no significant improvement.
Using incognito mode and clearing cookies before running the script.
Tweaking SeleniumBase's stealth options like --disable-blink-features=AutomationControlled and modifying WebDriver flags.
Unfortunately, none of these approaches seem to resolve the detection. It appears Google has enhanced its bot-detection mechanisms alongside this update.

I would appreciate any advice or insights from the community:

Has anyone found a reliable workaround for avoiding detection in recent Chrome updates?
Are there any recommended adjustments to the SeleniumBase configuration to bypass reCAPTCHA?
Would switching to an alternative framework like Playwright or Puppeteer be a better approach for such scenarios?
Looking forward to your thoughts and suggestions!

Best regards,

[mdmintz]

Duplicate of #2977 (comment).

reCAPTCHA is different from other anti-bot services because it may throw CAPTCHAs even if not detecting Selenium.

Instead of bypassing reCAPTCHA, solve the audio challenge with an external repo:
https://github.com/search?q=pydub.AudioSegment.from_mp3+recaptcha+solver+language%3APython&type=code

---

If you think you've found a bug within SeleniumBase, please open another issue with a self-contained repro.