Anti-spoof and lie detection
Detects when privacy tools or anti-detect browsers have replaced browser functions.
In one line
Can tell when a privacy tool or anti detect browser changed your browser's answers
Detects when privacy tools or anti-detect browsers have replaced browser functions.
Checks native toString, prototype descriptors and cross-signal consistency (WebGL renderer versus user agent). Finds noise injection, so being protected becomes a fingerprint of its own.
What it can and can't do
What the user does: Nothing. It happens when the page loads
It can
- Check if built in browser functions were replaced
- Compare answers across signals to spot a mismatch, such as graphics card versus browser label
- Spot random noise added by privacy tools
- Treat being protected as another trait that sets you apart
It cannot
- Remove your protections
- Ask permission first
- See your files or messages
- Know your name by itself
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 1 | 2008-12-11 | None |
| Edge | Supported | 79 | 2020-01-15 | None |
| Firefox | Supported | 1 | 2004-11-09 | None |
| Safari | Supported | 1 | 2003-06-23 | None |
| Safari on iPhone | Supported | 1 | 2007-06-29 | None |
| Chrome on Android | Supported | 1 | Not listed | None |
| Samsung Internet | Supported | 5.0 | 2016-12-15 | None |
How a site asks for it
| API | Function.prototype.toString; Object.getOwnPropertyDescriptor; iframe cross-realm checks |
| How access is granted | none |
| What the user sees | Not listed |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | Not listed |
| How to take it back | Not listed |
| Inside an iframe | Not listed |
Typical flow
- Compare function strings to native pattern
- Re-read the API in a fresh iframe or worker
- Flag mismatches
Data you get
What comes back: List of lie flags
Shape: boolean
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
lies | list | None | 0 to 50 | boolean per API |
Technical limits
- Arms race, advanced tools hide well
The story
What it is
A script detects when privacy tools or special browsers have replaced built in browser functions.
For you
You never see it. The page tests whether normal browser functions have been swapped out by an add on, a privacy tool or an anti detect browser. If so, you may face more checks or be blocked.
For makers
Fraud teams use it to spot people hiding their identity. Fingerprint vendors use it to find users who use privacy tools. It lets a site treat a spoofer as higher risk, or target them anyway.
Where you see it
| Type | Example | Apps |
|---|---|---|
| security | A bank spots that a login came from a tool that replaces browser values, and requires video or ID checks. | None named |
| payments | A checkout sees a browser whose canvas function was replaced and routes the order to review. | Stripe Radar, Sift |
| ads | An ad verifier finds bots that fake human browsers to click on ads, so the advertiser is not billed. | Integral Ad Science, DoubleVerify |
| games | A browser game finds players using tools that fake devices to farm bonuses. | None named |
| shopping | A sneaker or ticket site finds scalpers using anti detect browsers with many fake profiles. | None named |
| analytics | A fingerprint library flags visitors with tampered values, so counts are cleaner. | FingerprintJS, CreepJS |
| dating | A dating site blocks fake profile farms that use anti detect browsers. | None named |
Risks
- Privacy tools get flagged
- False alarms
- Arms race with spoofers
Good uses and abuse
Legitimate uses
- Fraud detection
Known abuse
- Defeat protection tools, label privacy users
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 2 of 5 | How revealing the data is |
| Utility | 2 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 3 | Rough identifying entropy, when known |
History
- 2021-01, github: CreepJS adds extensive lie detection
Related capabilities
Related
- Brave farbling. Can't track you across sites by device traits when Brave adds random noise
- Composite fingerprint (FingerprintJS, CreepJS). Can combine many device traits into one visitor ID that survives cleared cookies
Sources
How well checked: Based on official documentation.