Skip to Content
Platform.Ontology

Anti-spoof and lie detection

Detects when privacy tools or anti-detect browsers have replaced browser functions.

Used to track youGraphics and fingerprintingCompositeWeb browsersWhen the page loads

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

BrowserStatusFirst versionReleasedNote
ChromeSupported12008-12-11None
EdgeSupported792020-01-15None
FirefoxSupported12004-11-09None
SafariSupported12003-06-23None
Safari on iPhoneSupported12007-06-29None
Chrome on AndroidSupported1Not listedNone
Samsung InternetSupported5.02016-12-15None

How a site asks for it

APIFunction.prototype.toString; Object.getOwnPropertyDescriptor; iframe cross-realm checks
How access is grantednone
What the user seesNot listed
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsNot listed
How to take it backNot listed
Inside an iframeNot listed

Typical flow

  1. Compare function strings to native pattern
  2. Re-read the API in a fresh iframe or worker
  3. Flag mismatches

Data you get

What comes back: List of lie flags
Shape: boolean

FieldTypeUnitRangePrecision
lieslistNone0 to 50boolean 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

TypeExampleApps
securityA bank spots that a login came from a tool that replaces browser values, and requires video or ID checks.None named
paymentsA checkout sees a browser whose canvas function was replaced and routes the order to review.Stripe Radar, Sift
adsAn ad verifier finds bots that fake human browsers to click on ads, so the advertiser is not billed.Integral Ad Science, DoubleVerify
gamesA browser game finds players using tools that fake devices to farm bonuses.None named
shoppingA sneaker or ticket site finds scalpers using anti detect browsers with many fake profiles.None named
analyticsA fingerprint library flags visitors with tampered values, so counts are cleaner.FingerprintJS, CreepJS
datingA 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

ScoreValueMeaning
Sensitivity2 of 5How revealing the data is
Utility2 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bits3Rough identifying entropy, when known

History

  • 2021-01, github: CreepJS adds extensive lie detection

Sources

How well checked: Based on official documentation.

On this page