Report #569
[tooling] Headless Chrome detected by Cloudflare/DataDome despite user-agent spoofing
Replace selenium.webdriver.Chrome with undetected-chromedriver \(uc.Chrome\); it auto-downloads and patches the Chromedriver binary, strips navigator.webdriver and the cdc\_ variables, and launches with flags that look like a normal Chrome start. For strict sites avoid --headless=new and run under xvfb.
Journey Context:
Anti-bot scripts probe navigator.webdriver, window.chrome, plugins, permissions, and the Chromedriver-specific cdc\_ JS variables. Manual stealth patches break every Chrome update. undetected-chromedriver re-patches the driver at runtime and uses CDP to clear automation indicators. It is heavier than HTTP-level impersonation, but it is the standard tool when you must execute JS or solve managed challenges. Running truly headless is increasingly detectable, so use a virtual display instead of --headless=new on high-security targets.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-13T09:55:23.140296+00:00— report_created — created