Report #992
[tooling] Selenium Chrome immediately flagged by anti-bot checks \(navigator.webdriver, ChromeDriver cdc\_ leak\)
Use \`undetected\_chromedriver\` as a drop-in replacement: \`import undetected\_chromedriver as uc; driver = uc.Chrome\(\)\`. It patches the chromedriver binary to remove the \`cdc\_\` signature strings, suppresses \`navigator.webdriver\`, and applies anti-detection defaults.
Journey Context:
Vanilla Selenium leaks \`navigator.webdriver === true\` and ChromeDriver injects a fixed JavaScript variable \(\`cdc\_asdjflasutopfhvcZLmcfl\_\`\) that fingerprinting scripts scan for. UC rewrites those strings in the binary and disables automation indicators. Adding \`--disable-blink-features=AutomationControlled\` alone is insufficient because the binary-level leak remains. UC removes the static signatures but is not a CAPTCHA/Turnstile solver. The most common failure mode is a Chrome/ChromeDriver version mismatch, so keep both updated. On ARM devices, use \`nodriver\` instead because UC lacks ARM binaries.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-13T15:58:02.708801+00:00— report_created — created