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.
Automated scraping rings route clicks through commercial datacenter servers or residential proxy tunnels. Tunnel encapsulation (WireGuard/SOCKS5) clamps TCP SYN MSS to <= 1420 bytes, leaks residential IPs via WebRTC, or routes DNS queries through discordant overseas resolvers.
Blink AXTree Forced Instantiation Detected: Micro DOM attribute mutation benchmarks revealed abnormal accessibility tree cache invalidation latency (ratio > 2.8x vs baseline). In standard Chromium browsers, the accessibility object model (AXTree) is lazy-loaded and uninstantiated. However, Chrome DevTools Protocol commands (e.g. Accessibility.getFullAXTree) or automation driver role queries (e.g. Playwright getByRole) force the Blink C++ engine to instantiate AXObjectCacheImpl. Because this can also be triggered by assistive screen readers (NVDA, VoiceOver), this factor is classified as a Tier 2 supporting signal and is fully neutralized whenever human interaction is present.
Ad Platform Fraud Classification: Under Google Ads Invalid Traffic guidelines (Automated Click Activity) and Meta Advertising Integrity standards, sessions exhibiting Blink AXTree Cache 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: Assistive screen readers (NVDA, JAWS, VoiceOver) run by legitimate visually impaired human users. Completely neutralized by human verification factors.
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.