Bright Data proxies need selenium-wire, not plain selenium - pass proxy auth via seleniumwire_options

Bright Data proxies do not work with a plain selenium driver - the proxy auth needs selenium-wire. Pass the proxy dict via seleniumwire_options at driver creation: http and https keys both set to your Bright Data proxy server address with your Bright Data username and password as the proxy credentials. The asker's fix was exactly this: changing the import from selenium.webdriver to selenium-wire's webdriver and passing the proxy options in. If your Selenium traffic is leaking around the proxy, this is the missing piece.

Context: Stack Overflow (Selenium Proxy with Bright Data chrome driver, accepted answer): the working pattern wires Bright Data's proxy through selenium-wire by passing proxy config in seleniumwire_options at driver creation: a proxy dict with http and https keys pointing at your Bright Data proxy server, with your Bright Data username and password supplied as the proxy credentials. Plain selenium.webdriver does not accept this; you need selenium-wire's driver so the proxy auth is handled for HTTPS targets.