All posts

Bots are signing up to your app: how to stop fake sign-ups

You open your user list and see hundreds of new accounts with gibberish names that nobody confirmed. Or your form inbox fills with spam, or your email provider warns about bounces. Bots found your sign-up form. Here is how I would spot them and stop them, in order of effort. Each vendor fact comes from the vendor's own docs. Limits and plans change, so open the linked page before you rely on a number.

Short answer: require email confirmation, turn on rate limits, add a CAPTCHA that your server checks, and use a honeypot on plain forms. Then clean out the junk accounts and stop emailing them.

1. How to tell it is bots

One odd sign-up means nothing. A pattern does. Look for these:

  • Bursts. Dozens of sign-ups within minutes, then nothing for hours.
  • Gibberish. Names like "xkqjw" and emails with random strings.
  • Disposable domains. The same few unfamiliar email domains again and again.
  • Unconfirmed accounts piling up. Real users click the link. Bots using fake addresses cannot.
  • Bounces rising. Your email provider's dashboard shows more bounced mail than usual.

Sort your users table by creation time. Bots show up fast.

2. Why it matters

Email reputation. Each confirmation email to a fake address that does not exist bounces. Many bounces can hurt how mailbox providers treat your domain, and then real users may stop receiving your emails. See SPF, DKIM and DMARC for app emails for the base setup.

Costs and limits. Some auth plans limit monthly active users. Junk accounts that log in can use up that allowance. Check your plan page. Free credits, trials and free-tier features also attract abuse, because a bot can create a new account for each one.

3. Defenses, from cheap to more work

Step 1: Require email confirmation

The simplest filter: no confirmed email, no access. Supabase's password auth docs say hosted projects require email verification by default, while self-hosted and local setups do not. Check that it is on in production.

Confirmation does not stop every bot, because some use real or disposable inboxes. But fake addresses cannot get in.

Step 2: Rate limits on sign-up

Supabase. The rate limits page says you set auth limits in the dashboard under Authentication, then Rate Limits, or through the Management API. The documented defaults:

  • Sign-ups and sign-ins: 30 requests per 5 minutes, per IP address.
  • Emails sent: 2 per hour with the built-in email provider. With custom SMTP you configure this limit yourself.
  • The same user must wait 60 seconds between confirmation or reset emails.

Limits per IP address slow a single bot, but not one that rotates addresses.

Firebase. Firebase's Auth limits page says new accounts are limited to 100 per hour for each IP address, and that you can schedule a temporary increase in the console. It lists address verification emails at 1,000 per day on the Spark plan and 100,000 per day on Blaze. It also warns that abuse protections may be enabled without warning on accounts with suspicious traffic. Those limits are high, so add your own checks.

Step 3: A honeypot for plain forms

A honeypot is an extra form field hidden from people with CSS. Humans leave it empty. Many bots fill every field. If the field has a value, you drop the submission. It costs nothing and your users never see it.

Netlify Forms has this built in. Netlify's spam filter docs say you add a netlify-honeypot attribute to the form with the name of your hidden field, and keep that field in the form but hidden. Netlify then quietly rejects a submission where that field is filled. The same page says every submission is also filtered with Akismet, and that flagged ones go to a Spam list you can review.

Step 4: A CAPTCHA

A CAPTCHA asks the browser to prove it is a real visitor. Two common choices:

  • Cloudflare Turnstile. Cloudflare's plans page lists it on the Free plan, with up to 20 widgets and no stated cap on verifications. Its docs list three widget modes: Managed, which decides whether to show a checkbox based on visitor risk; Non-interactive, where the visitor never needs to interact; and Invisible, where the widget is hidden.
  • hCaptcha. Its developer docs describe an invisible mode in code, but say passive modes are an Enterprise feature. Check its plans for what is free.

Supabase supports both. Its CAPTCHA guide says you enable it in the dashboard under Bot and Abuse Protection, choose hCaptcha or Turnstile, and enter the provider's secret key. Your front end shows the widget and passes its token as captchaToken in the options of the auth call, such as signUp. It says CAPTCHA can guard sign-in, sign-up and password reset forms.

Firebase. The route is App Check. Firebase's App Check overview says it rejects requests without valid attestation once enforcement is on, and lists Firebase Authentication as protected, marked Preview. For web, the built-in provider is reCAPTCHA Enterprise. The setup page says each token refresh creates a reCAPTCHA assessment, and that assessments above the no-cost quota are charged, so read it before you turn it on. It also warns that apps not yet registered lose access once enforcement is on.

Check the token on the server

This step is easy to miss. A widget in the browser protects nothing by itself. Cloudflare's server-side validation docs say you must call the Siteverify API, that the widget alone does not protect your forms, and that attackers can send any string to your endpoint. A token is valid for 300 seconds and can be validated once. hCaptcha's docs describe the same pattern with a siteverify endpoint, and say tokens are single-use.

If you use Supabase or Firebase's own CAPTCHA settings, they do the check for you. If you wrote your own form handler or function, verify the token there, and reject the request when it fails. Keep the secret key in server settings, never in code the browser can read. See database security checks for AI-built apps for how that goes wrong.

Step 5: Block disposable email domains (optional)

You can refuse sign-ups from known throwaway domains. The trade-off: lists go out of date, bots move to new domains, and you may block a real user, such as someone who hides their address on purpose. I would use it only if the other steps are not enough. I did not find vendor documentation to cite for this, so check the current docs of your auth tool.

4. Cleanup

Delete old unconfirmed accounts. A simple practice: once a week, delete accounts that never confirmed and are older than, say, 7 days. Supabase's docs do not describe an automatic cleanup that I could find. To delete in code, auth.admin.deleteUser needs the service role key and must only run on a server. Back up first. For Firebase, check the current Admin SDK docs.

Stop emailing junk addresses. Do not send newsletters to unconfirmed users. If an address bounced, suppress it. Check whether your email provider keeps a suppression list for you.

What I do on my own sites

The forms on my hire-me site run on Netlify Forms, and its spam filter catches most of the junk. On my job board, a new sign-in link for the same address goes out at most once every 2 minutes, so nobody can make the app flood an inbox, and the reply never says whether that address has an account.

A 20-minute checklist

  1. Look at the pattern (3 min). Sort users by creation time.
  2. Check confirmation is on (2 min). Production, not only your local setup.
  3. Check rate limits (3 min). Open the auth rate limit settings and lower sign-up and email limits if they are generous.
  4. Add a CAPTCHA (7 min). Turnstile in Supabase takes the site key, the secret key and one extra field in your sign-up call. Test a real sign-up after.
  5. Check your own endpoints (2 min). Any custom form or function must verify the token on the server.
  6. Add a honeypot (1 min) to plain forms.
  7. Clean up (2 min). Back up, then delete old unconfirmed accounts and suppress bounced addresses.

Then watch your sign-ups and bounce rate for a week. Add alerts for odd spikes if you want to hear sooner. The other login settings worth a look (rate limits, leaked passwords, MFA) are in securing the login of your app.

Want this fixed for you?

I finish and fix apps built with Lovable, Bolt, Cursor or Replit, including sign-up protection, rate limits, CAPTCHA checks on the server and cleanup of junk accounts. Or send me the details on the hire page and I'll reply within 24 hours.