← How We Detect Bots (All 180+ Signals) REVERSE-ENGINEERED KASADA & ARKOSE LABS VECTORS • TIER 2 (WEIGHT: 45)

Autonomous AI Agent Artifact

Technical forensic specification explaining how BotRefund analyzes browser environments and network invariants to distinguish novel retail browsers from server-side automation.

Authentic Consumer Baseline

Normal Consumer Browser

Authentic consumer browsers maintain strict internal coherence across operating system APIs, physical hardware constraints, and userland execution environments.

Automated Server Fingerprint

Automated Bot & Novel Browser

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.

CHROMIUM & NETWORK PROTOCOL BLUEPRINT

Technical Forensic Specification

Autonomous AI Agent Injection & Custom CSS Artifacts (Arkose Labs BDA): Runtime DOM analysis detected artifacts of autonomous AI browser operators (such as Perplexity Comet overlay CSS custom properties `--dark-super-color` and `--base-shadow`, Sigma browser flags, or Genspark AI automation properties). Autonomous agent execution lacks direct human agency, operating as automated background task runners.

FORENSIC SIGNATURE: `ai_agent_injection_artifact` / `Autonomous AI Agent Artifact`
ENGINE DISCREPANCY: Clustered LLM reasoning pause (2000-6500ms, CV < 0.2) + bounding-box geometric centroid click
CORROBORATION RULE: Multi-layer voting engine evaluates alongside hardware entropy & L4 netprobe

DISPUTE DOSSIER VERIFICATION // AD PLATFORM REVIEWERS

For Google Ads & Meta Click Quality Reviewers

Ad Platform Fraud Classification: Under Google Ads Invalid Traffic guidelines (Automated Click Activity) and Meta Advertising Integrity standards, sessions exhibiting Autonomous AI Agent Artifact 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.

FALSE-POSITIVE MITIGATION

Multi-Dimensional Corroboration Engine

Human Baseline & Exception Scenario: Legitimate users who installed assistive AI browser extensions while actively browsing manually. 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.

Independent Evidence

This signal registers an objective, mathematically verifiable anomaly on the session ledger.

Cross-Checked Context

BotRefund correlates L4 packet timing, GPU silicon, and cursor jerk before finalizing risk.

Carrier-Ready Dossier

Compiled directly into Google Ads and Meta refund packets with verified click IDs and server logs.