Reverse-engineering Claude's client-side anti-fraud: Android binds hardware IDs, a China SIM card gives you away

dotey · x · 2026-10-21

A static reverse-engineering of Claude Code (Mac CLI, Mac App, Android) maps out its risk-control stack: Android is the strictest, using Sift fraud detection, SIM-country checks, and hardware-bound ANDROIDID + Play Integrity that survives reinstalls; Mac apps use randomized device IDs with Sentry/Datadog telemetry. The author lists eight classic mistakes that burn accounts: China SIM cards, wiping app data, sharing /.claude.json across accounts, switching accounts without rotating userData, routing only the main domain through residential IPs while telemetry goes through proxies, KYC-time IP checks (Turnstile, hCaptcha, Stripe 3DS, Persona), hammering requests after a restriction, and multi-accounting on one residential IP. Workflow used: DeepSeek Harness + flatkey.

Original post →

More from Safety

Safety channel →