What Is CloakBrowser? – Definition and How It Works
Learn what CloakBrowser is, how a patched-Chromium stealth browser differs from a stealth plugin, and how to evaluate one against your own targets.
CloakBrowser is an anti-detect browser aimed at automated collection rather than at manual multi-accounting. It belongs to the same family as Camoufox: a modified browser build that ships fingerprint control inside the binary, driven from a script rather than clicked through a profile manager.
1. Build-Level Versus Plugin-Level Stealth
The distinction that separates this category from stealth plugins is where the change happens.
A plugin such as puppeteer-extra-plugin-stealth runs inside the page and rewrites properties after the browser has already produced them. That leaves the redefinition itself visible to code that examines property descriptors, prototype chains, or toString output.
A patched build changes what the browser produces in the first place. There is no redefined property because the value was never wrong. The trade-off is distribution: you now depend on someone else's browser build tracking upstream Chromium, and you inherit their release cadence for security fixes.
2. What to Expect From the Category
Browsers in this class generally offer configurable user agent and platform, screen and viewport geometry, timezone and locale, WebGL and canvas behaviour, font sets, and hardware properties — plus an automation entry point so the browser can be driven programmatically, usually over the Chrome DevTools Protocol.
Coherence is the quality that separates a good implementation from a poor one. Setting fields independently is easy and produces contradictory profiles; generating a profile whose values agree with each other is the harder problem and the one worth testing.
3. How to Evaluate One Honestly
Vendor claims in this category are difficult to compare, because "undetected" is meaningful only against a named defence, at a named difficulty, from a named network.
A defensible evaluation holds three things fixed:
- The target. Test the sites you actually collect from, not a general fingerprint-checking page. Passing a fingerprint audit and passing a bot manager are different results.
- The egress. Run the comparison from one egress type. A residential exit flatters every browser in the field and can erase the difference between them entirely; a datacenter exit is where the differences show.
- The challenge type. Distinguish a page that renders, a page that shows an interstitial and clears it, and a page that blocks outright. Collapsing those into one pass/fail number hides the result that matters.
Anyone reporting a comparison without stating the egress has reported a number that cannot be reproduced.
4. What It Does Not Cover
A stealth build addresses the browser. It does not supply addresses, and it does not pace requests. IP reputation is evaluated before any script runs, and request rate and navigation order are analysed independently of the browser you used.
Treat the browser as one component of three — build, egress, behaviour — and expect the weakest of the three to determine the outcome.
5. Summary
CloakBrowser is a patched-Chromium anti-detect browser for scripted collection, in the same category as Camoufox but on a different engine. The category's advantage over stealth plugins is that fingerprint values are produced natively rather than rewritten in-page. Evaluate any member of it against your own targets, from a fixed egress type, with challenge outcomes reported separately.