-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Browser Automation Studio is undetected #212
Comments
It appears that the fingerprint feature is a paid service. There is a lot of cool stealthy software out there. We mostly give attention to FOSS-privacy tools. I will take a look, but will probably not make modifications to show it can be detected. |
Hey abraham, even the free version passes it. |
Nice. I will definitely check it out. In the future, I may introduce some concepts showing that fingerprint and score are of little value compared to server-side fingerprints. Everything that does not blend-in with normal traffic on the site can be detected. For example, you could generate 200 – 1000 requests in 24 hours, and usually, it can be traced. If you would like to try this out for fun, I can try to tag and name your browser in the analysis section. Make sure to generate many requests. |
should every regist be signed or just the first ? |
around 400 executions have been done. |
Okay, try now. In the analysis section, you see “bad” for the hidden fingerprint, but let me know if I missed the target. If you open a different or clean browser, it should go away. |
I'm just looking at last 2 hrs today, but can pick a different date. |
sadly doesn't seem to work. thank you non the less. |
Yes i do. want me to upload it or anything? |
Hey, you can either download the free version from BAS here: https://bablosoft.com/shop/BrowserAutomationStudio#download |
yes its worker.exe full cli
|
It using JavaScript to fake fingerprint and it can detected and heavy |
Hey, it seems like BAS ( https://bablosoft.com/shop/BrowserAutomationStudio ) is currently undetected,
from the looks of it they use a custom compiled chrome version.
The text was updated successfully, but these errors were encountered: