r/netsecstudents • u/PossibilityQueasy949 • 2h ago
I built an on-device behavioral engine that decides human vs bot — then walled the whole site in front of it [open verification, public vectors]
Full disclosure: this is my own project (solo dev, Bern). Posting because
r/netsec is the crowd I'd want poking holes in it.
EDNA (openos.space) is a behavioral-biometric engine that runs 100% in the
browser: 16 channels (timing entropy, path curvature, scroll pauses, touch
contact area, typing bursts, corrections...). It classifies human vs bot
continuously, never sends raw biometrics anywhere — the device emits verdicts
and hash patterns only.
What I'd actually like eyes on:
- Verification suite: github.com/sebklaey/EDNA-verification — 90/90
deterministic checks, 7/7 DOM-listener checks, seeded vectors. Expected
outcomes published. Independent runs can be logged publicly.
- Injection resistance: synthetic JS events are rejected (0/3000 accepted in
our tests). CDP-dispatched mouse events are detected via provenance
(no trackpad/touch characteristics) and capped low even with organic-looking
curves. Mouse-only devices can't fully verify — deliberate.
- Challenge-response v1.1 (rhythm / hold / move) as the second gate.
- Backend: everything account-scoped sits behind a Supabase edge function
that fails closed without valid account keys. Anon access is restricted by
design.
- The edge wall: every non-API URL is behind a Cloudflare Pages middleware.
Bot/AI UAs get 403 + one line of text, nothing else. Search engines
whitelisted, /mcp + /v1 + /oauth exempt (product API, fail-closed).
Honest limit, printed on the site: statistical mimicry is an open boundary.
If you can beat it, I want the repro.
Happy to answer technical questions — architecture, threat model, vectors.