and to add to that, democratization of tools that allow this is essential, despite the fact that there will always be bad actors.
so, we built fortress, which is an open-source stealth chromium engine. it is a recompiled fork that corrects the browser fingerprint from inside the engine: the surfaces bot detectors read, canvas, webgl, audio, fonts, navigator, and about thirty more, are patched in chromium's c++, with no javascript layer sitting on top for a page to catch.
it beats the hardest bot detectors on the planet, works fully locally and is open source for y'all to see the patches we've made. and it comes with an mcp, so you can use it with your agents without having to do any major setup or code changes. do give it a try here!
I would like to ask a technical question: How does Fortress handle lower level detection such as WebRTC leakage of real IP and TCP/IP protocol stack fingerprints (TTL, window size, and other OS level features) after fixing fingerprints at the C++layer? Because the actual situation I encountered is that even if the browser fingerprint is perfect, the features of the network layer are not consistent and will still be marked.