A client asked me to look at their WooCommerce store because the database had grown to several gigabytes even though they only sold a few hundred products. The culprit turned out to be the users table. The store had more than 60,000 customer accounts, and fewer than 2,000 had ever placed an order. The rest were fake user registrations created by bots over three years, each with a random username and a throwaway email address. Every one of them had triggered a welcome email, which had quietly been eating into the store’s email sending limit and hurting its sender reputation.
Spam signups are one of those problems that grow silently. Nobody notices a few dozen fake accounts a day until there are tens of thousands. This article explains why bots register on WordPress sites, the damage they do and how to stop them, without making registration harder for real customers.
Why bots register accounts
It can seem pointless for a bot to create an account on a small business site. But there are several reasons it happens:
- Comment and forum spam. On sites where registered users can comment, post in forums or create profiles, an account is the first step to posting spam.
- Profile link spam. Some sites display user profiles publicly. Bots fill profile fields with links, hoping for search engine value.
- Testing stolen cards. On WooCommerce stores, card testing bots sometimes create accounts before attempting small transactions.
- Exploiting vulnerabilities. Some plugin vulnerabilities require a subscriber or customer account. Bots create accounts in bulk so they’re ready when a new vulnerability appears.
- Email abuse. Registration emails can be abused to send unwanted messages to victims whose address the bot enters.
- Simple automation. Many bots just fill in every form they find, registration included.
The damage fake accounts do
Even if the accounts never do anything, they cost you:
- Database bloat, which slows queries and backups
- Wasted email sends and damaged email reputation from welcome emails to fake or invalid addresses
- Skewed customer numbers and marketing lists
- A larger pool of accounts that could exploit privilege-escalation vulnerabilities
- Privacy and compliance burden, because you’re storing personal data you don’t need
- Admin noise, especially if you receive a notification for every new user
Step 1: Do you need registration at all?
The simplest fix is often to turn registration off. In WordPress, go to Settings, General and check the “Membership: Anyone can register” box. If it’s ticked and you don’t run a membership site, forum or community, untick it. Many sites have it enabled by accident, sometimes left over from a theme demo import.
Also check the “New User Default Role”. It should be Subscriber, or Customer for stores, never anything higher. Attackers look for sites where the default role was accidentally set to Author or Administrator.
For WooCommerce, the settings are under WooCommerce, Settings, Accounts and Privacy:
- Allow customers to create an account during checkout
- Allow customers to create an account on the My Account page
- Allow customers to place orders without an account
Guest checkout reduces friction for genuine customers and removes the need for many accounts. If you don’t offer customer benefits that require an account, such as order history, subscriptions or saved addresses, consider allowing guest checkout and disabling account creation on the My Account page. Bots mostly target that standalone registration form, not the checkout.
Step 2: Add invisible bot protection
If you need registration, protect the form the same way you’d protect a contact form. Layered, low-friction protection works best:
- Honeypot fields that humans don’t see but bots fill in
- Timing checks that reject forms submitted too quickly after the page loads
- Invisible challenges such as Cloudflare Turnstile, reCAPTCHA v3 or hCaptcha in invisible mode
Several security plugins and dedicated anti-spam plugins add these protections to the WordPress registration form and the WooCommerce My Account form. Make sure the plugin you choose covers the specific forms your site uses, because WooCommerce registration, the default WordPress form and custom membership forms are all different.
Step 3: Validate email addresses
Fake registrations rely on disposable or invalid email addresses. Several checks help:
- Block disposable email domains. Lists of throwaway email providers are widely maintained, and some plugins check against them automatically.
- Check that the domain can receive mail. A domain without MX records can’t receive email. That catches many invented addresses.
- Require email verification. Don’t activate the account until the user clicks a link in a confirmation email. Bots rarely complete this step, so unverified accounts can be deleted automatically after a few days.
Email verification adds a step for real users, so it suits membership sites and communities more than stores. For stores, a lighter approach is to let customers buy immediately but only send marketing emails after verification.
Step 4: Rate limit and block at the edge
High-volume registration attacks come from automated tools that submit the form repeatedly. Rate limiting at the server, firewall or CDN stops a single source from creating dozens of accounts per minute.
In Cloudflare, a rate-limiting rule on the registration URL, such as /my-account/ with POST requests or /wp-login.php?action=register, is very effective. A web application firewall can also block known bad IP addresses and data centre traffic that rarely belongs to real shoppers.
Step 5: Reduce what an account can do
Limit the value of a fake account so even if some get through, they cause no harm:
- Keep the default role at Subscriber or Customer.
- Require approval for comments from new users, or close comments entirely if you don’t use them.
- Don’t display public profile pages with links unless your community needs them, and add nofollow to any user-submitted links.
- On forums and communities, require manual approval or a minimum account age before posting.
Step 6: Watch the right signals
Add simple monitoring so you notice spikes early:
- Turn off admin emails for each new user registration if they’re overwhelming, but replace them with a daily summary or a dashboard widget showing new accounts.
- Track registrations versus first orders for stores. A sudden jump in accounts without a jump in orders is a clear sign of bot activity.
- Use an activity log to record registrations with IP addresses, so you can spot patterns.
Cleaning up existing fake accounts
If your site already has thousands of fake accounts, clean them up carefully. Deleting real customers is far worse than leaving a few fake ones.
First, take a full backup.
Then identify candidates. For WooCommerce, a good starting point is customers who have never placed an order, registered more than a few months ago and have never logged in since registering. You can list users with no orders using WP-CLI and a small script, or use a cleanup plugin that offers filters like “no orders”, “no posts” and “registered before”.
Look at a sample before deleting. Real customers sometimes create accounts and buy later, and some placed orders as guests with the same email. Check whether any guest orders share their email address before removing an account.
Patterns that usually indicate fake accounts:
- Random strings as usernames, like xkqzlbw482
- Disposable or nonsense email domains
- Many accounts registered from the same IP within minutes
- Display names stuffed with keywords or links
Delete in batches, and attribute any content they created to an admin account if needed. With WP-CLI:
After a large cleanup, optimise the users and usermeta tables, because deleted rows leave space that the database doesn’t reclaim automatically.
A sensible default setup
For most business sites:
- Registration off unless you genuinely need it.
- For stores, guest checkout on and the standalone My Account registration form off, unless accounts provide real customer value.
- Where registration is needed, a honeypot plus an invisible challenge on every registration form.
- Disposable email blocking, and email verification for communities and memberships.
- Rate limiting on registration endpoints.
- A periodic review of new accounts versus real activity.
That stops nearly all fake user registrations while keeping signup easy for the people you actually want.
Frequently asked questions
Will disabling registration affect existing customers?
No. Existing accounts keep working. Disabling registration only stops new accounts from being created through that form.
Do fake accounts affect my site’s security?
They can. If a vulnerability is discovered that lets subscribers or customers escalate privileges, every fake account is a potential attacker. Fewer accounts means less exposure.
Can I delete accounts automatically?
Some plugins delete unverified accounts after a set period. That works well with email verification. Be cautious with automatic deletion based on other criteria.
Why do bots register even when I have a CAPTCHA?
Some bots solve simple CAPTCHAs or use paid solving services. Combining several layers, including email validation and rate limiting, is far more effective than any single check.




