BotBrowser

---

What BotBrowser actually does

BotBrowser rebuilds Chromium with fingerprint handling moved into the binary and driven by external profile files, so one profile describes a whole device rather than a scattered list of per-surface overrides.

What BotBrowser's maintenance signals mean

The liveness field here is pushed_at, read as 2026-08-08 against a field check 6 days later. That is inside 90 days, and 90 days is where the second edition of the rubric put ACTIVE after moving it down from the first edition's 180.

The reason for the move is worth stating, because it is the kind of threshold that looks arbitrary until you know what it is measuring against: detection changes on a shorter cycle than half a year, so a six-month-old evasion is not a current one. What a recent push does not tell you is what was in it. A commit landing on a branch is not a release, not a fix, and not a test — it is evidence that somebody is still there.

The release field is a second and different signal. 151.0.7922.47 was published 2026-08-06, and the gap between that date and the push date above is the interval in which work exists but has not been cut into anything you can pin a dependency to. A project that pushes constantly and tags rarely and a project that does the reverse look very different to anyone trying to depend on either.

Where BotBrowser sits in this catalogue

BotBrowser is filed in section 01, open-source anti-detect browsers & forks, whose scope is this: Browsers whose source you can read: anti-detect Firefox and Chromium forks, hardened builds, and the profile managers built on top of them. An entry sits in exactly one section here. Where a project could defensibly go in two, it is placed where a reader would look for it first rather than where it fits most tidily, and that is an editorial decision rather than a measured one.

Filed beside it in the same section: Camoufox (ACTIVE), Donut Browser (ACTIVE), Undetectable Fingerprint Browser (NRND). Comparing an entry against its own section-mates is more informative than comparing it against the catalogue as a whole, because everything in a section is answering roughly the same question and the differences left over are the ones that matter.

It is published under MIT, alongside the rest of the MIT entries in this register, and it sits with everything else currently marked ACTIVE. Read those two facets together: a permissively licensed project that stopped shipping is not a safer dependency than a copyleft one that did not, and a filter on one axis alone will tell you the wrong thing.

Substitutes for the same job, with no claim that either is better: AdsPower, Camoufox, Donut Browser, Multilogin, Undetectable Fingerprint Browser. The alternative relation is symmetric and carries no ranking, because this register publishes no ranking of any kind. The full BotBrowser comparison table sets all of them side by side on licence, push date, release cadence and state.

What to settle before you adopt BotBrowser

The anti-bot systems named in its own description are the author's stated target, not a result this register has confirmed for itself. Read the profile format before anything else: a binary-level spoof is only as coherent as the profile you hand it.