[Bug]: 100% CAPTCHA/Bot Detection Rate on Google SERP despite Mobile Proxies (Free Version)

Author: zekiyetarhan17-codeCreated Jun 25, 2026Updated Sep 16, 2026

Hello team,

We are currently running a high-concurrency SERP telemetry worker pool (our Harvester module built on Golang) connected to CloakBrowser via Playwright. Over the last few days, we have experienced a complete halt in our scraping pipeline. Every single Google SERP iteration is immediately flagged by bot detection (CAPTCHA), making it impossible to complete any workflow.

We are utilizing high-quality mobile proxies with frequent IP rotation, which previously worked flawlessly. It appears that the recent core and anti-spam updates from Google (late June 2026) have compromised the stealth capabilities of the current Free build.

Environment:

  • CloakBrowser Version: Free build (Chromium v146)
  • Automation Framework: Playwright (driven by Go worker pools)
  • Proxy Setup: High-trust Mobile Proxies (residential IP range) with geoip=True enabled.
  • OS/Architecture: [Sunucu işletim sistemini buraya yaz, örn: Ubuntu 24.04 LTS]

Steps to Reproduce:

  1. Launch the CloakBrowser free binary using Playwright.
  2. Pass a clean Mobile Proxy via launch arguments along with humanize=True and headless=False.
  3. Navigate to Google SERP and perform a standard query search.
  4. Immediate CAPTCHA or "Unusual traffic" block occurs, blocking any further rendering or DOM interaction.

Observations:

  • IP reputation is not the issue, as the same mobile proxies function perfectly in a standard browser.
  • We avoid any CDP-heavy commands like page.waitForTimeout() to prevent CDP leaks.
  • Is there a scheduled stealth patch for the free (v146) binary to address the recent Google anti-bot updates, or are the necessary C++ fingerprint patches strictly mitigated in the v148 (Pro) build right now?

Any insights or ETA for an updated free release would be highly appreciated.