Summary of an article published on The Web Scraping Club on 2026-06-04 (for paid subscribers). Read the full article
Camoufox has been our default anti-detect browser for more than a year, but lately it does not pass the harder targets the way it used to. Part of that is normal cat and mouse. Part of it is that anti-bot vendors can read an open fingerprint-spoofing codebase line by line. The project also changed hands: active development moved to Clover Labs, and the public repo has more than 750 forks. So the question is whether anyone in the fork tree has built something better.
We filtered the forks down to the three that really touch the anti-detect surface: camoufox-reverse, LeooNic and JWriter20, with official Camoufox as baseline. Our target is leboncoin.fr, because it runs only DataDome. We traced DataDome’s property reads from inside the engine, tested a WebRTC leak behind a Bright Data proxy, examined a canvas noise patch, and ran a block-rate comparison on an Apple M2 Max.
What’s inside
- What DataDome reads at the engine level, compared between the Leboncoin homepage and a car listing page, and what that says about where to spend effort.
- How WebRTC ICE candidates leak a real IP behind an HTTP proxy, and why the origin the probe runs on can invalidate the measurement.
- How the Pixel-Recovery attack from the “Breaking the Shield” paper reverses canvas noise, and the content-dependent approach LeooNic’s patch uses against it.
- Why builds were matched by Firefox version (135 versus 146) so the comparison stays fair.
In the full article: Probe scripts and the repository folder with the test code, the full property-read tables, the per-build WebRTC and canvas results, the block-rate comparison and the verdict on the forks.