How Google detects automation at signin

Hey there I made some research regarding this topic as recently I get sign-in blocked by google even with my strongest bot config (browser may not be secure error).
After some hours I encountered this super interesting issue: basically if you are automating chrome, firefox or whatever your are doing so by connecting with remote debugging pipe/port.
In the case of puppeteer, you will find the flag --remote-debugging-pipe in chrome://versions as it is automatically set in order for puppeteer/playwright/selenium to work.

Now it seems Google is able to detect such flag, probably using some javascript object. Any idea which object?
This means that in 100% of cases Google IS ALREADY detecting you, if you're able to pass it's because it let you through, but your account will eventually be flagged and banned or limited later.

My thesis is: no matter how many fingerprints you spoof or how consistent they are, Google will know you are automating just by checking for the presence of the flag.
You can solve this problem by setting or changing User Agent (for example with android UA it works) but I am pretty sure they know this and flag the account.
By the way it seems that starting from January 2021 some bad things will happen for automation
There is so little information about this on the web, some say navigator.webdriver will be set as "true" but that's an old story, there has to be some more.
@Gogol @Sebastiann

Google can detect that with Google API Keys.

Juat save yourself the headaches.

Go to any 3rd party site with Google login option.

Click it login and then navigate to any Google owned property your trying to reaxh.

Thank me later when you try the above.
I use this with selenium for Gmail, youtube, blogger, ad service, analytics, and search console.

lowridertj said:

Juat save yourself the headaches.

Go to any 3rd party site with Google login option.

Click it login and then navigate to any Google owned property your trying to reaxh.

Thank me later when you try the above.
I use this with selenium for Gmail, youtube, blogger, ad service, analytics, and search console.

Click to expand...

Yes I already know this method, google still knows that you're a bot and the problem isn't solved

Unless you figure out a way to strip the dom of the checkpoint for the driver being used its going to pick it up every time.

Im just saying and mentioned the work a round for others as well as yourself as you had not mentioned it being an option.


Can refer to this link that I had used when attempting to make a ghost version of the selenium / chromium browser
and also gives javascript that can be used for testing the driver being picked up when landing on a page.

But also gives ideas how to change some flags that can be caught as well.

https://stackoverflow.com/questions...when-you-are-using-selenium-with-chromedriver

Yep, interesting for me as well

lowridertj said:

https://stackoverflow.com/questions/33225947/can-a-website-detect-when-you-are-using-selenium-with-chromedriver

Click to expand...

This is gold!!!

Some JS variable have different values in different browsers. It's mismatch when you just changed only user agent .

Browser fingerprint