undetected_chromedriver

https://github.com/ultrafunkamsterdam/undetected-chromedriver

Optimized Selenium Chromedriver patch which does not trigger anti-bot services like Distill Network / Imperva / DataDome / Botprotect.io Automatically downloads the driver binary and patches it.

• Tested until current chrome beta versions
• Works also on Brave Browser and many other Chromium based browsers, but you need to know what you're doing and needs some tweaking.
• Python 3.6++**

Installation

pip install undetected-chromedriver

or , if you're feeling adventurous, install directly via github

pip install git+https://www.github.com/ultrafunkamsterdam/undetected-chromedriver@master     # replace @master with @branchname for other branches

---

Message for all

I will be putting limits on the issue tracker. It has beeen abused too long.
any good news?
Yes, i've opened Undetected-Discussions which i think will help us better in the long run.

---

What this is not

THIS PACKAGE DOES NOT, and i repeat DOES NOT hide your IP address, so when running from a datacenter (even smaller ones), chances are large you will not pass! Also, if your ip reputation at home is low, you won't pass!

Running following code from home , and from a datacenter.

import undetected_chromedriver as uc
driver = uc.Chrome(headless=True,use_subprocess=False)
driver.get('https://nowsecure.nl')
driver.save_screenshot('nowsecure.png')

3.5.0

• selenium 4.10 caused some issues. 3.5.0 is compatible and has selenium 4.9 or above pinned. I can't support <4.9 any longer.
• Removed some kwargs from constructor: service_args, service_creationflags, service_log_path.
• added find_elements_recursive generator function. which is more of a convenience funtion as lots of websites seem to serve different content from different frames, making it hard to use find_elements

3.4.5

• What a week. Had the recent advancedments in Automation-Detection algorithms pwned (so i thought) with 3.4.0, but apparently, for some OS-es this caused an error when interacting with elements. Had to revert back using a different method, fix bugs, and now eventually was still able to stick to the initial idea (+ fixing bugs)
• Update to chrome 110 caused another surprise, this time for HEADLESS users.
• although headless is unsupported officially, i did patch it!
• happy to announce IT IS NOW UNDETECTED AS WELL (but still unsupported ;))
• special thanks here to @mdmintz and @abdulzain6
• also special thanks to @sebdelsol for his help troughout the issues section completely voluntarily, you must be crazy :)

3.4.0

Big update! be careful as it -potentially- could break your code.

• rewritten the anti-detection mechanism instead of removing and renaming variables, we just keep them, but prevent them from being injected in the first place. This will keep us safe from detection at least for the near future.

• rewritten the file naming, to prevent ending up with 1000 of {randomstring}_chromedriver.exe 's instead it is just called undetected_chromedriver.exe

• cleanup removed compat,v2 files and tests folder

3.2.0

• added an example containing some typical webdriver code, answers to commonly asked questions, pitfalls + showcasing some tricks to ditch the need for multithreading.

>>>> example code here <<<<

• added WebElement.click_safe() method, which you can try in case you get detected after clicking a link. This is not guaranteed t o work.

• added WebElement.children(self, tag=None, recursive=False) to easily get/find child nodes. example:

  body = driver.find_element('tag name', 'body')
  
  # get the 6th child (any tag) of body, and grab all img's within (recursive). 
  images = body.children()[6].children('img', True)
  srcs = list(map(lambda _:_.attrs.get('src'), images))
  

• added example.py where i can point people at when asking silly questions (no, its actually quite cool, everyone should see it)

• added support for lambda platform

• added support for x86_32

• added support for systems reporting as linux2

• some refactoring

3.1.6

still passing strong

• use_subprocess now defaults to True. too many people don't understand multiprocessing and name == 'main, and after testing, it seems not to make a difference anymore in chrome 104+

• added no_sandbox, which defaults to True, and this without the annoying "you are using unsecure command line ..." bar.

• update Docker image. you can now vnc or rdp into your container to see the actual browser window

• of course, "regular" mode works as well

3.1.0

this version might break your code, test before update!

• added new anti-detection logic!

• v2 has become the main module, so no need for references to v2 anymore. this mean you can now simply use:

  import undetected_chromedriver as uc
  driver = uc.Chrome()
  driver.get('https://nowsecure.nl')
  

  for backwards compatibility, v2 is not removed, but aliassed to the main module.

• Fixed "welcome screen" nagging on non-windows OS-es. For those nagfetishists who ❤ welcome screens and feeding google with even more data, use Chrome(suppress_welcome=False).

• replaced executable_path in constructor in favor of browser_executable_path which should not be used unless you are the edge case (yep, you are) who can't add your custom chrome installation folder to your PATH environment variable, or have an army of different browsers/versions and automatic lookup returns the wrong browser

• "v1" (?) moved to _compat for now.

• fixed dependency versions

• ChromeOptions custom handling removed, so it is compatible with webdriver.chromium.options.ChromiumOptions.

• removed Chrome.get() fu and restored back to "almost" original:

  • no with statements needed anymore, although it will still work for the sake of backward-compatibility.