There is a technique which allows to detect if javascript was executed by browser. We're not talking about scripts necessary for the website to function, but rather about things like searching for an element on a page, obtaining its coordinates, retrieving the element's code, and so on. This way, you can detect various software and frameworks for automation that utilize javascript. This applies not only to methods for working with DOM but also to basic operations like working with lists or strings. Previously, we addressed such vulnerabilities on a situational basis by hiding the methods that were specifically checked by a particular website. Now, we have decided to address the issue comprehensively by modifying almost all the javascript code executed by BAS in the browser. As a result, it will be impossible to detect the use of standard BAS actions. However, actions like "Javascript" and "Execute javascript on element" are still risky to use. For example, using the "Get Element Content" action to retrieve the code of an element is safe, whereas using the "Execute javascript on element" action with the parameter [[RESULT]] = self.innerHTML can be detected. An example of the improvements you can observe is the MetaMask extension. In version 25.7.0, the selectors on the extension's page doesn't work, but in version 25.8.0, this issue is resolved. This functionality was implemented by @Oyasumi-Punpun .