Custom Anti-detect browser development help

virchual

Junior Member
Joined
Feb 18, 2024
Messages
149
Reaction score
68
I'm a Pyhton/JS programmer by profession and I'm a lot into social media automation, data scraping and any other kind of web automation related to that.
I have 3+ years of experience in this field.

I have working experience with browser automation frameworks like selenium, playwright and a bit with puppeteer as well.
Since I'm here I'm reading a lot about anti-detect browsers. I have tested a few of anti-detect browsers because I need them for managing multiple accounts on a website for long term.
These anti-detect browsers have got my attention because of the interesting features they have like manipulating the digital fingerprints etc.

I have been thinking how would it be if I want to develop my own anti-detect browser?
I wonder what libraries these anti-detect browsers are using to create them and how they have been able to manipulate all the properties of the browsers.
If anyone can give me a starting guide or point me to some direction to learn about this kind of development then it'll be great.
Thanks a lot to everyone who's gonna participate in the discussion.
 
You need couple of people on your team for this. There's just lots of works to get this done.
 
I'm a Pyhton/JS programmer by profession and I'm a lot into social media automation, data scraping and any other kind of web automation related to that.
I have 3+ years of experience in this field.

I have working experience with browser automation frameworks like selenium, playwright and a bit with puppeteer as well.
Since I'm here I'm reading a lot about anti-detect browsers. I have tested a few of anti-detect browsers because I need them for managing multiple accounts on a website for long term.
These anti-detect browsers have got my attention because of the interesting features they have like manipulating the digital fingerprints etc.

I have been thinking how would it be if I want to develop my own anti-detect browser?
I wonder what libraries these anti-detect browsers are using to create them and how they have been able to manipulate all the properties of the browsers.
If anyone can give me a starting guide or point me to some direction to learn about this kind of development then it'll be great.
Thanks a lot to everyone who's gonna participate in the discussion.
Do u still working on it dude??
I'm really interested in this !!
 
Do u still working on it dude??
I'm really interested in this !!
Nopes. I found that it's beyond the skills of a single developer so I gave up on that. But may be in the future.
 
Use Chrome source code and delete all Google's stuff from it.
 
Nopes. I found that it's beyond the skills of a single developer so I gave up on that. But may be in the future.
Dude I think it's possible because of AI
i was exploring all Anti-detect system and what they used to be different on same System

I found this things : May be they use Fake Geo locations , Random User Agents , Random Language , Random window Size And Use proxy for each profile .... idk this is enough or not

currently i'm working on selenium with chrome driver Using Threading for fast the process for every profile...
With the help of Ai and Right prompt may be bypass the Detection of Browser Fingerprint and other things (idk those other rn)

Sharing all information for the past 6 months of research on automation ( My TG is @@KillerKnight012 )
If any of u guys reading this and have suggestions plz contact... Let's Grow together guys
 
There are fingerprint generating libraries online. I forgot where but you can pay for one of these services and get as many as you want for a few cents. That can be a core feature of your anti detect browser
 
It's not that complicated. Focus on the core engines - blink, gecko. And take it from there. You don't have to build a fresh engine for each profile, instead mimic how headless browsers are coded. You could write your own sdk or use the base implementations of the common ones, like chrome-driver. And then generate custom configurations for each profile. You'd be surprised how much chrome is customizable by simple config:// settings. You can even vary the gpu engine chosen to add different paint signatures which determine the reso, refesh rates etc. There is much more that these multiaccounting browser can do to make each profile statistically unique.

I've been mulling stating a sideproject for this... and it's not a team project. No project is... just depeneds on how focused and commited you are... are mostly how organised your arch is going to be. Build the arch well at the start, instead of a patchwork sort of build.
 
Last edited:
Dude I think it's possible because of AI
i was exploring all Anti-detect system and what they used to be different on same System

I found this things : May be they use Fake Geo locations , Random User Agents , Random Language , Random window Size And Use proxy for each profile .... idk this is enough or not

currently i'm working on selenium with chrome driver Using Threading for fast the process for every profile...
With the help of Ai and Right prompt may be bypass the Detection of Browser Fingerprint and other things (idk those other rn)

Sharing all information for the past 6 months of research on automation ( My TG is @@KillerKnight012 )
If any of u guys reading this and have suggestions plz contact... Let's Grow together guys
Thanks. Will reach out.
There are fingerprint generating libraries online. I forgot where but you can pay for one of these services and get as many as you want for a few cents. That can be a core feature of your anti detect browser
Informative. Thanks!
It's not that complicated. Focus on the core engines - blink, gecko. And take it from there. You don't have to build a fresh engine for each profile, instead mimic how headless browsers are coded. You could write your own sdk or use the base implementations of the common ones, like chrome-driver. And then generate custom configurations for each profile. You'd be surprised how much chrome is customizable by simple config:// settings. You can even vary the gpu engine chosen to add different paint signatures which determine the reso, refesh rates etc. There is much more that these multiaccounting browser can do to make each profile statistically unique.

I've been mulling stating a sideproject for this... and it's not a team project. No project is... just depeneds on how focused and commited you are... are mostly how organised your arch is going to be. Build the arch well at the start, instead of a patchwork sort of build.
Thanks!
 
Back
Top