Filled a hidden honeypot form field — a naive form-filling bot, never a human

bh.arena_honeypot_filled  ·  convicts

behaviorallayer
automationcategory

What it catches

Kitsune arena challenge-solve coherence (honeypot gate): the classic hidden-field honeypot. The arena mints a CAPTCHA whose prompt asks the client to submit WITHOUT filling a hidden trap field (arena/captcha.go MintCaptcha CaptchaHoneypot, Field: website_url); the page renders the field with display:none so a human never sees or fills it. A non-empty answer (the trap value) on a honeypot challenge is an unambiguous naive form-filling bot — the gate fails structurally, and the arena emits anomaly:honeypot_filled, which the detector's /arena/captcha/verify relay joins to ks_sid (shared _join_arena_anomaly map). FP-SAFE BY CONSTRUCTION: a real user CANNOT fill a field they are never shown, so nothing a human does trips it — precision 1.0 is load-bearing. Gated on known (the honeypot id was actually issued to this session), so a garbage or replayed id cannot synthesize the tell against a victim session. Convicting (w0.9 — a honeypot trip is one of the highest-precision bot signals; it needs no timing or biomechanics). This is the interaction-with-a-trap analog of the timing (superhuman-speed) and trajectory (forgery) solve-behaviour tells. GROUNDED LIVE 2026-07-03: a honeypot verify with a non-empty trap field through the detector convicts the session (label bot); an empty submission is silent. See docs/research-radar.md (arena-solve loop rung 8).

Signals it reads

behavioral.arena_honeypot_filled

How it fires

present

Bypassed by 10

Frontier evaders that reach the detector uncaught (scored only suspicious, defeating every convicting tell) — this check is not one that stops them. The red-team frontier this detection still has to convict.

← all detections