---
title: "Discussion on \"WebKit vs Chromium through the eyes of anti-fraud: why an engine swap shows\" | Hashnode"
description: "Discussion on \"WebKit vs Chromium through the eyes of anti-fraud: why an engine swap shows\". How anti-fraud spots Chromium posing as an iPhone: TLS, client hints, JS engine and GPU checks, and what WebKit doesn't fix."
url: "https://hashnode.com/posts/webkit-vs-chromium-through-the-eyes-of-anti-fraud-why-an-engine-swap-shows/6ab4b315a3575e88d651c96a"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [WebKit vs Chromium through the eyes of anti-fraud: why an engine swap shows](https://exitanty.hashnode.dev/webkit-vs-chromium-through-the-eyes-of-anti-fraud-why-an-engine-swap-shows?utm_source=hashnode&utm_medium=feed)

How anti-fraud spots Chromium posing as an iPhone: TLS, client hints, JS engine and GPU checks, and what WebKit doesn't fix.

Sep 24 · 7 min read · exitanty.hashnode.dev  
Read the article

-   [#webkit](https://hashnode.com/tag/webkit)
-   [#chromium](https://hashnode.com/tag/chromium)
-   [#security](https://hashnode.com/tag/security)
-   [#browsers](https://hashnode.com/tag/browsers)
-   [#privacy](https://hashnode.com/tag/privacy)

## Written by

[Georgy](https://hashnode.com/@exitanty)

@exitanty · Dubai, UAE

  
[View profile](https://hashnode.com/@exitanty)

Antidetect browser dev

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
