We look after a WooCommerce store that’s been selling online for over ten years. Around 34,000 orders, steady business, nothing dramatic. This week we went in to look at some fake orders and found 44,000 fake customer accounts.
They’d been arriving since January, about 25 an hour, every hour.
It turned out to be two separate problems with two separate fixes. Here’s how to spot each one on your own store, and what we did about them.
Why the usual fix doesn’t work
The standard advice is to add a CAPTCHA to your forms. We’ve installed Google’s reCAPTCHA on a lot of stores over the years, including this one. It was running the whole time, and it didn’t stop any of this.
The reason is that the bots never look at your forms. Behind every checkout page and signup form is an address that accepts the data. Bots skip the page and send their junk straight to that address. A CAPTCHA that only checks visitors on the page never sees them.
Problem 1: fake accounts
On this store, every one of them looked the same. A username of random letters and numbers, a Gmail or Outlook address, no name, no shipping address, and no orders. Ever.
It’s tempting to ignore them, since they don’t buy anything. But they don’t stay put. This store syncs its customers to Mailchimp, and about 12,000 of its 13,500 contacts turned out to be fake. Mailing list services charge by the contact. And every new account can send a welcome email from your domain to an address a bot picked, which is not the kind of mail you want your name on.
Check your store: go to WooCommerce → Customers and sort by date registered, newest first. If the first page is all nameless accounts with zero orders, you have this problem. This store had 87,000 customer accounts and 34,000 orders.
Problem 2: fake orders
These show up as failed orders, usually in a burst. They’re called card testing: someone has a list of stolen card numbers and uses your checkout to find out which ones still work. They pick the cheapest thing you sell so the charge goes unnoticed.
This store had been hit three holiday seasons in a row. 327 failed orders one December, 566 the next November, 1,548 the December after that. Nearly every order in the last wave was the same: one $1 add-on item, which came to $5.35 with shipping. A few dozen went through, and each of those had to be refunded before it became a chargeback.
Two weeks before we looked, seven more had come in. Same item, same $5.35. All seven were declined. It looked like somebody checking whether the door was still open.
Check your store: go to WooCommerce → Orders → Failed. A handful a month is normal, since real cards get declined. Dozens in a day for the same small amount is card testing. If your orders list shows an Origin column, the fake ones say “Unknown,” because the bot never visited the site.
What stops it
In the order we’d do them.
1. Close the doors you don’t use
In WooCommerce → Settings → Accounts & Privacy, turn off “Allow customers to create an account on the My account page.” Customers can still create an account when they check out. This is one checkbox. On this store, signups went from 25 an hour to one in the next 20 hours.
2. Turn on rate limiting
WooCommerce has a setting that limits how fast anyone can submit the checkout. It’s in Settings → Advanced → Features, called “Rate limit Checkout,” and it’s off by default. Turn it on. It won’t stop a patient attacker, but it turns a flood into a trickle.
3. Take away the cheap target
If you sell a $1 add-on, a sample, or a pay-what-you-want donation, that’s what the bots will buy. Set a minimum order amount, or make the cheap item something that can only be added to a cart with a real product in it. That’s what we did here: a cart with nothing but the $1 item can’t check out.
4. Use a check that happens on the server
We replaced reCAPTCHA with Cloudflare Turnstile. It’s free and most customers never see it. What matters more than the brand is where the check happens: it has to run when the order arrives at the server, not only on the page. Older CAPTCHA plugins didn’t do that for WooCommerce’s newer checkout. Whatever you use, make sure it’s current, and that it covers checkout and login, not just your contact form.
5. Fewer ways to pay
Every payment option is its own door. The big waves on this store all came through one payment plugin’s card form, while a second card form sat right beside it doing the same job. If you take cards through Stripe, you don’t need another plugin taking cards too.
6. Clean up
Refund any small test charges that went through. Turn off the “Failed order” email under Settings → Emails so a wave doesn’t bury your inbox. Then delete the fake accounts, after taking a backup: only the ones with no name, no address and no orders. On this store that was 43,992 accounts, and it took an afternoon to run.
One thing we’d skip: the heavyweight anti-fraud plugins with a risk score for every order. We’ve watched one block more real customers than bots.
A note on timing
All three waves on this store landed between mid-November and the end of December. The biggest day was December 29th. If you’re going to do the first three fixes, do them before Black Friday.
Then watch it
Check the customer count the next morning. It should have stopped moving, apart from people who actually bought something. Check Failed orders once a week through December. And after any change, place a real order yourself, as a guest, on your phone, to make sure customers can still buy.
Don’t want to spend your December watching for bots?
On a Cinch plan, this is our job. We watch the failed orders, keep the doors closed, and fix it when something gets through.