Technical forensic specification explaining how BotRefund analyzes browser environments and network invariants to distinguish novel retail browsers from server-side automation.
Retail distributions of Google Chrome, Apple Safari, and Microsoft Edge run uninstrumented Blink/WebKit engines. The accessibility tree (AXTree) is lazy-loaded, prototype methods serialize strictly with native C++ code strings, and isolated execution contexts prevent DOM interception.
Headless test harnesses (Playwright, Puppeteer, Selenium, Rebrowser) control browsers via the Chrome DevTools Protocol (CDP). This attaches debugger listeners, forces Blink AXObjectCacheImpl instantiation, injects __pwInitScripts globals, or proxies native prototypes.
Iframe Cross-Window Prototype & Property Desynchronization (Kasada p.js VM fn_72800): An ephemeral `about:blank` iframe probe revealed state desynchronization between the top-level window and the child iframe context across `navigator.webdriver`, `window.chrome`, `window.clientInformation`, or `navigator.plugins`. Anti-detect browsers and stealth evasion plugins hook properties on the top `window` object but fail to patch freshly attached iframe execution contexts, providing mathematically unassailable proof of automated stealth evasion.
Ad Platform Fraud Classification: Under Google Ads Invalid Traffic guidelines (Automated Click Activity) and Meta Advertising Integrity standards, sessions exhibiting Iframe Cross-Window Desync violate fundamental consumer hardware invariants. They fail deterministic silicon rasterization, protocol compliance, or neuromuscular biometrics.
Why This Proves Non-Human Origin: Genuine consumer browsers on retail operating systems execute this API natively with verified hardware backing. Server software (headless cloud containers, unpatched automation harnesses, and proxy tunnels) cannot replicate this execution environment without incurring prohibitive server hardware costs.
Evidence Dossier Invariants: Each disputed click in our export packet matches an immutable server-side timestamp, landing URL, GCLID/fbclid, and observed IP address with zero client-side tamperability.
Human Baseline & Exception Scenario: None. Genuine Chromium engines maintain identical prototype structures between top-level windows and clean child frames.
BotRefund operates a multi-vector ensemble model. This signal adds objective forensic weight to the session dossier but never acts in isolation. Positive verdicts require corroboration across network routing, hardware silicon, and cursor kinematics to guarantee 99% precision.
This signal registers an objective, mathematically verifiable anomaly on the session ledger.
BotRefund correlates L4 packet timing, GPU silicon, and cursor jerk before finalizing risk.
Compiled directly into Google Ads and Meta refund packets with verified click IDs and server logs.