xt26: honeypot to block bot form spam into Orbit#260
Open
jonpither wants to merge 1 commit into
Open
Conversation
Bots have been POSTing gibberish registrations straight to the public /.netlify/functions/xt26-register endpoint (gibberish names/company, dot-stuffed gmail addresses), which forwarded them into Orbit as prospect rows. The Orbit token isn't browser-exposed — it lives in this function's env — so the function endpoint itself is the gate. Adds a hidden off-screen `website` honeypot input to the shared contact form (off-screen rather than display:none so bots that skip hidden fields still trip it; removed from tab order so humans never focus it). The Netlify function silently drops any submission where it's non-empty — 200 OK, no forward to Orbit — so the bot can't detect the trap. Orbit's POST /api/people carries the same check as a backstop (juxt/orbit). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
✅ Deploy Preview for juxt-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Bots have been POSTing gibberish registrations straight to the public
/.netlify/functions/xt26-registerendpoint — gibberish names/company,dot-stuffed throwaway gmail addresses — which the function forwarded
into Orbit as prospect rows (
🎉 …gibberish… signed up via the website!pings in #orbit, ~8 junk rows as of 2026-05-21).
The Orbit API token isn't browser-exposed — it lives in this function's
env — so the function endpoint itself is the gate, not the token.
What
Two-layer honeypot:
src/components/ContactUsForm.tsx) — a hidden, off-screenwebsiteinput. Off-screen (notdisplay:none, which sophisticatedbots skip) and removed from the tab order, so a human never sees or
focuses it and it stays empty; a bot that auto-fills every input
trips it.
netlify/functions/xt26-register.ts) — silentlydrops any submission where
websiteis non-empty: returns200 OKand does not forward to Orbit, so the bot can't detect the trap
(a 4xx would let it tune around it).
Orbit's
POST /api/peoplecarries the same check as a backstop(already merged to
juxt/orbitmain, commit6b69678).Notes
website, so humans areunaffected.
🎉 …signed upSlack pingsfor a day or two to confirm the spam stops.
🤖 Generated with Claude Code