CloakBrowser: Someone Modified Chromium’s Fingerprint at the Source Level

I clicked open the CloakBrowser page, and the first thing I saw wasn’t a list of features—it was that blunt description:

It’s not a configuration patch, nor is it JS injection.

That line hits hard.

Anyone who’s done web automation knows the drill: often, before the script even starts running, the browser itself gives away the game. Canvas, WebGL, audio, fonts, GPU, WebRTC, screen parameters, CDP input signals—layer after layer of checks, and in the end, the issue isn’t in your business logic.

CloakBrowser takes the heavier route.

It’s built directly on top of Chromium, handling a batch of browser fingerprint signals at the C++ source code level. The project page says it started with 49 source-level patches, and the latest version has bumped that to 57 fingerprint patches, covering signals like canvas, WebGL, audio, fonts, GPU, screen, WebRTC, network timing, and automation signals.

I paused.

Because this isn’t the same kind of thing as your typical stealth plugin.

Many automation solutions slap on a disguise after the page loads—tweaking navigator, modifying webdriver, injecting a snippet of JS. It can pass some detection, but when faced with…