BrowserAutomationStudio 25.6.0 has been released

Bablosoft News
  • Browser version and fingerprint matching.

    Each BAS release can now contain multiple browser versions.

    The software allows you to switch between them and run different versions for different threads.

    To do this, use the "Browser Settings" action with the "Browser Version" parameter.

    The actions "Get list of available browser versions" and "Get current browser version" have also been added.

    It is planned to make a new release with a browser update every month.

    In best case scenario, users will receive BAS version shipped with the three latest versions of Chrome 2 weeks after the browser release.

    For example, if Chrome version 120 is released on December 1, then BAS version should be released in the middle of December and will contain browser versions 120, 119 and 118.

    But right now it is only intention, it is not 100% guaranteed that such schedule will be maintained.

    BAS version 25.6.0 ships with two versions of Chrome: 113.0.5672.64 and 111.0.5563.65.

    Added filtering option "Maximum browser version" when getting fingerprint.

    If you use the keyword "current" for the minimum and maximum browser version, then the resulting fingerprint will always match the real browser version

    With this update it is easy to change the browser version for each thread and then apply the fingerprint that matches that version.

    X64 browser version.

    When installing BAS on a 64-bit OS, the x64 version of the browser will be used.

    The vast majority of fingerprints are collected for x64 systems. Taking into account that BAS used x86 browser build previously, this inconsistency could be detected.

    In fact, although x86 support is formally retained, we strongly advice against using OS with this architecture. It may contain bugs, including critical.

    To ensure that proxy works correctly on x64 build, the tunneling library had to be updated.

    If this will lead to critical bugs in the proxy functionality, we will have to switch back to the x86 build of the browser, roll back the library version and change the tunneling method.

    Stack fingerprint.

    This factor will now always be exactly the same as in the real browser of the desktop version.

    Tweaking the Fingerprints.StackSizeDiff parameter is no longer necessary.

    The discrepancy can only be detected if mobile fingerprints are used.

    Browser Authenticity.

    In this version, additional measures have been taken to improve the authenticity of the browser:

    • Browser build is now official.
    • Added Google API keys.
    • Disabled some build options that are not used by default.
    • Disabled some command line options that are not used by default.

    Additionally, you can remove these options from the chrome_command_line.txt file:


    But this can lead to poor performance.

    Safe browsing.

    Added support for Safe browsing.

    The absence of this feature can be detected. For example, one well known test uses this technique to distinguish between Chromium and Chrome.

    Safe browsing support can be disabled on the settings page or by using the "Browser Settings" action

    Unlike a regular browser, BAS will not update safe browsing database dynamically, so the feature is available immediately after creating new profile, and additional traffic will not be used.

    Browser components.

    Added support for browser components. Their absence can also potentially be detected.

    Browser components support can be disabled on the settings page or by using the "Browser Settings" action

    Components will not be displayed on the chrome://components/ page, but they will be used by the browser.

    Unlike a regular browser, BAS will not update components dynamically.


    QUIC support is enabled by default. Obviously the absence of http3 can be detected by sites.

    There is at least one site that blocks a browser that doesn't use http3 and another that changes behavior when http3 is not present.

    http and non-udp sock5 proxies should automatically use the old version of the protocol.

    If you experience problems loading or displaying the site on the new version, you need to try disabling QUIC, if it helps, be sure to send the proxy, site and sequence of actions to

    Some methods for detecting BAS.

    Fixed BAS detection on one site.

    Fixed another method that could potentially lead to detection.

    Proxy for profile creation.

    BAS blocks any requests to the network between the time the profile was created and the time when proxy was set. This is done so that real ip is not used for requests to Google services.

    In the new version, _set_proxy_for_next_profile method is available, it allows you to change this behavior:

    _set_proxy_for_next_profile("block")! // Block network requests until the proxy is set or the first page load.
    _set_proxy_for_next_profile("direct")! // any requests will be made directly, without any proxy until it is set.
    _set_proxy_for_next_profile("socks5://")! // for initial requests the specified proxy will be used. After changing the profile, the proxy still needs to be applied to set the browser language.

    This method can be applied explicitly, it is also used automatically when switching to a profile that previously had a proxy installed.

    Bug fixing.

    Fix clipboard issues after enormous number of browser restarts.

    Fixed issues with PerfectCanvas generation for several methods.

    Better emulation for input events on "tel" input type on Android.

    Other fixes.


    Fixed issues with DPI emulation.

  • Thanks for the awesome update with new features. however, the latest version is giving me error when loading my script from the previous one. it gives me this error

    I need advice on how to go about this

  • @tibbar said in BrowserAutomationStudio 25.6.0 has been released:

    Thanks for the awesome update with new features. however, the latest version is giving me error when loading my script from the previous one. it gives me this error

    I need advice on how to go about this

    Does this error happen with all scripts or only with a specific one? Can you send me a problematic script in a pm?

  • @Fox Thanks for the quick reply. I sent you the problem script. maybe you could figure out why that happens. also, the old scripts that were from december and january seem to work. but not the script from the before ver 25.6.0

  • Can't use chrome-extension after applying android fingerprint :( previous versions do it very well


  • @thanhvodad, @support said in BrowserAutomationStudio 25.5.0 has been released:

    Support for extensions in mobile fingerprints is disabled.

    You can try to enable them by execute code: _settings({"Fingerprints.Extensions": "Enable"})!, but not fact if it will work.
    Mobile devices don't support extensions, and therefore it is not natural to use extensions with a mobile fingerprint.

  • @GhostZ said in BrowserAutomationStudio 25.6.0 has been released:


    sorry it doesn't work :(