Selenium Webdriver is detectable

12,242

Solution 1

The W3C draft spec states in Appendix E that drivers should provide a mechanism for fingerprinting that a browser is being driven by WebDriver. At the moment, no implementations comply with this section of the spec. The Firefox driver currently comes closest, adding an attribute to the html tag. Future versions and drivers of other browsers will likely implement methods of detection in line with the specification.

Solution 2

Yes selenium is detectable.check Can a website detect when you are using selenium with chromedriver? If some one is using Firefox driver for automation then it is easy to detect if you put this code at your client side

        try{
        if(window.document.documentElement.getAttribute("webdriver"))
            alert("Caught in 1st case :- Selenium Webdriver is banned!!!");
        }
        catch(Exception){}
        try{
        if(navigator.webdriver)
            alert("Caught in 2nd case :- Selenium Webdriver is banned!!!");
        }
        catch(Exception){}`

But same code doesnt help if you are using chrome or IE driver.

Solution 3

I'd have to side with SiKing in that whatever addon you're using isn't part of the actual Selenium tools. Can you post a link to your addon? Maybe that would shed some more light.

Generally speaking, WebDriver simply automates the usage of a browser with the intent of replicating the actions of a human user as closely as possible. This, in and of itself, will be invisible to the server. Unless you're altering your browser's user agent, there would be nothing for the server to easily see to indicate any sort of automation in use.

However, while I've only recently begun studying this, repeated automated usages of an application may present patterns in server logs that could be far more consistent than a human user as far as interactions with an application. If you're using Selenium to scrape a site, for example, you could be leaving some fingerprints just due to the nature of an automated session. Things like extremely consistent click, inputs, page requests, etc. could be forming noticeable log patterns that could potentially expose automation.

Now, unless you're generating a lot of traffic or a lot of repetitive actions on the system, you're unlikely to be noticed. It would take something generating fairly abnormal in the logs, or a very observant sysadmin to trigger any sort of manual investigation... and even then, someone would have to know what to look for to make an accurate determination.

Share:
12,242
Stevo
Author by

Stevo

Updated on June 17, 2022

Comments

  • Stevo
    Stevo almost 2 years

    I read everywhere that it is not possible for websites to detect that a user is using a selenium webdriver... but why?

    For example the webdriver plugin in firefox adds an 'webdriver attribute' to the <html> element. So the <html>... goes to <html webdriver="true">...

    I am confused... why it is not possible to detect the webdriver?

    I wrote a little Javascript to get the document.outerHTML... and there is the webdriver attribute! = detected!?

    Here is my code I tested in Browser with Webdriver and without:

    <html>
    <head>
      <script type="text/javascript">
      <!--
        function showWindow(){
          javascript:(alert(document.documentElement.outerHTML));
        }
      //-->
      </script>
    </head>
    <body>
      <form>
        <input type="button" value="Show outerHTML" onclick="showWindow()">
      </form>
    </body>
    </html>
    

    Please can somebody explain me why it is not possible to detect the Webdriver?

  • Stevo
    Stevo almost 10 years
    Thanks. But this addon is pre-installed in the FirefoxDriver so I can't provide a link to it. I know that inhuman actions will logged and can expose automation but that was not my point. I am just confused about the 'WebDiver = true' attribute on the initial page load when using the FFDriver. @Arran 's comment brought some light into
  • m3nda
    m3nda over 7 years
    @Stevo Indeed, Firefox profile contains an addon which is merely "the javascript server part" of Firefox webdriver. The tag webdriver=true can be removed without problem. U can extract the addon the upload it elsewhere, then have a link to show ;-) but the better if simply ask people for looking the sources.