← Stef Development

Fake customer accounts on PrestaShop: stop bot sign-ups without a captcha

Dozens of customer accounts created overnight, no orders, odd names? Here is how to spot them, what PrestaShop already does, the manual fixes and their limits, then a protection that needs no captcha.

Updated on November 4, 2026 · Mustapha EL ATRASSI, Stef Development

Key points

  • Typical sign: bursts of sign-ups with no cart and no order, often from the same IPs, with random names or throwaway addresses.
  • PrestaShop 8 and 9 already reject digits, “@”, “/” and most dots in first and last names, but have no captcha, no honeypot and no per-IP account limit.
  • No captcha needed: an invisible honeypot field stops bots that fill in every field, and asks nothing of real customers.
  • Combine: honeypot + per-IP account limit + suspicious-name filter + (optional) disposable mailbox filter.
  • Clean-up: delete fake accounts while allowing the same address to register again: it often belongs to a real person.

How do you recognise fake customer accounts?

Short answer: a fake account never buys. Fake accounts arrive in batches, at quiet hours, often from the same IP address or network, and their fields look mechanical.

SignWhere to see it in PrestaShopWhat it suggests
Several accounts created within minutesCustomers › Customers, sorted by registration dateAutomated sign-up
First or last name with a link, digits or random lettersCustomer list, First name and Last name columnsSpam bot or form testing
Disposable e-mail addresses (yopmail, mailinator…)E-mail columnNo intention to buy
No cart, no address, no orderCustomer pageAccount created for something other than buying
Welcome e-mails bouncingThe shop sender’s mailboxInvented or stolen addresses

One sign alone proves nothing: a real customer may register without ordering. It is the combination, in bursts, that should raise a flag.

Why do bots create accounts on an online shop?

Short answer: the sign-up form makes your shop send an e-mail and unlocks customer-only features. That is what bots are after.

  • Getting your shop to send a message. The first name is repeated in the welcome e-mail. A bot that registers a victim’s address with an advert in the first-name field gets your mail server to deliver it.
  • Testing forms at scale. Bots crawl the web and submit every form they find. OWASP lists this among automated threats (“OAT-019 Account Creation”: bulk account creation through the sign-up process).
  • Preparing other abuse. An account opens pages and forms reserved for logged-in customers.

For the merchant: a polluted customer base, skewed statistics, and e-mails sent to people who never asked for them, which can hurt your domain’s sending reputation.

What does PrestaShop do natively against fake accounts?

Short answer: PrestaShop checks the format of first and last names and lets you turn off the welcome e-mail. It has no captcha, no honeypot and no per-IP sign-up limit.

Native featureWhereEffect on bots
First/last name validation (CustomerName constraint)Automatic (checked in the PrestaShop 8.2 and 9.0 code)Rejects digits, “@”, “/”, “:” and a dot not followed by a space, so a link such as www.site.com no longer passes. An invented but “clean” name still passes.
“Send an email after registration”Shop Parameters › Customer SettingsWhen off, the shop sends no welcome message, so no relayed spam. Real customers lose that summary too.
Deleting customers with a re-registration choiceCustomers › Customers, bulk actionsCleans up afterwards; does not stop the next sign-ups.
Captcha, honeypot, per-IP limitNot in the coreNeed a module or a server rule.
On PrestaShop 1.6 or 1.7, name validation is older and more permissive. Updating also fixes published vulnerabilities: PrestaShop’s security policy says security fixes are usually applied to the latest release only.

Manual methods and their limits

Short answer: you can clean up by hand, block IPs in .htaccess or add a captcha, but each has a cost: time, an IP list that always lags behind, or friction for real customers.

1. Delete fake accounts the right way

  1. Back up the database.
  2. Open Customers › Customers and sort by registration date.
  3. Filter suspicious names or domains; check that no selected account has an order.
  4. Tick the accounts, then Bulk actions › Delete selected.
  5. Choose the option that allows the customer to register again with the same address: bots often use a real person’s address, and that person may become a customer later.

2. Refuse IPs in .htaccess (Apache 2.4)

If sign-ups keep coming from the same addresses, refuse them at server level. PrestaShop keeps any code placed above the # ~~start~~ line when it regenerates the file.

# Fake accounts: refused IPs (put this ABOVE the "# ~~start~~" line)
<RequireAll>
  Require all granted
  Require not ip 203.0.113.45
  Require not ip 198.51.100.0/24
</RequireAll>

Limits: bots change IPs; a wide range can shut out real customers; behind Cloudflare or another proxy, the server sees the proxy’s IP and this rule does not work without extra setup (for example mod_remoteip).

3. Add a captcha

A captcha slows down simple bots, but adds a step for every real customer at the exact moment they sign up or check out. Third-party captchas also involve data processing that your privacy policy must mention.

MethodEffect on botsFriction for customersUpkeep
Manual deletionNone as preventionNoneRepeat after every wave
IPs refused in .htaccessGood against a fixed sourceRisky if the range is wideList to maintain
CaptchaGood against simple botsOne more stepKeys and module to maintain
Honeypot + per-IP limitGood against form-filling bots and burstsNo visible stepLow

What is a honeypot field and why can it replace a captcha?

Short answer: it is a form field hidden from visitors. A human does not see it and leaves it empty; a bot that fills in every field fills it too, and the sign-up is refused.

Two benefits: no extra step for the customer, no external service. The known limit: a bot that renders the page, or a person paid to sign up, will not fall into the trap. That is why it is combined with a per-IP account limit, which stops bursts, and a name filter.

Stop fake accounts with Block IPs, without a captcha

Short answer: the Block IPs module adds an invisible honeypot, a suspicious-name filter, a per-IP account limit and, as an option, a disposable mailbox filter to the sign-up form. The first three are on as soon as it is installed.

ProtectionDefaultWhat happens
Invisible honeypotOnSign-up refused if the field is filled; the bot’s IP is blocked (unless it is on your white list).
Suspicious namesOnRefuses a first or last name containing a link, an e-mail address, 3 or more digits in a row, more than 40 characters or two or more full stops. The customer sees a clear message.
Accounts per IP3 per rolling hourBeyond that: “too many accounts were created from your connection, please try again later”.
Disposable mailboxesOption, offRefuses a list of 69 known domains (yopmail, mailinator, guerrillamail…).
Refused sign-up logOnE-mail, IP, reason and date of each refusal, plus 30-day counters.

Set-up, step by step

  1. Install the module from the Module Manager (PrestaShop 1.7 to 9 for the fake-account protection).
  2. Open the Registrations section: check that the honeypot, blocking of the trapped IP and the name filter are on.
  3. Adjust the per-IP limit (3 per hour by default). A shop whose customers share one connection, such as a company or a school, can raise it.
  4. Turn on the disposable mailbox filter if you do not want throwaway accounts.
  5. Make a real test sign-up, then check the refused sign-up log after a few days.

The same module protects the rest of the shop: IP, country and bot blocking, request limits and two-factor authentication for the back office. Full overview on the Block IPs module page.

The check applies to the account creation form. If you lose access or a setting gets in your customers’ way, an empty BLOCKIPS-RESCUE file uploaded by FTP to modules/blockips/ suspends the sign-up and back-office protections; remove it afterwards.

A 6-step action plan

  1. Measure: how many accounts without orders in the last 30 days, and from which IPs?
  2. Update PrestaShop and your modules.
  3. Delete existing fake accounts while allowing those addresses to register again.
  4. Add friction-free protection: honeypot, name filter and per-IP limit.
  5. If a fixed source persists, refuse its IP or range (module or .htaccess).
  6. Check the refusal log weekly for a month, then monthly.

Stop fake accounts with Block IPs

Invisible honeypot, name filter, per-IP account limit and disposable mailbox filter: no captcha, on PrestaShop 1.7 to 9. The module also protects the shop and the back office (€69.99 excl. VAT on PrestaShop Addons). See the module overview.

See Block IPs on PrestaShop Addons

Frequently asked questions

How do I stop fake accounts on PrestaShop without a captcha?

With an invisible honeypot field (bots fill it in, humans do not), a per-IP account limit and a suspicious-name filter. Block IPs combines all three, on from installation, on PrestaShop 1.7 to 9.

Why do fake accounts have links in the first name?

The first name is repeated in the welcome e-mail. By registering a victim’s address with a link as first name, the bot gets your shop to send its advert. PrestaShop 8 and 9 already reject most of these links; older versions are more permissive.

Should I delete fake customer accounts?

Yes, after a backup and after checking they have no orders. Choose the option that lets the same address register again: it often belongs to a real person.

Does a honeypot bother customers or hurt SEO?

No. It is invisible, asks for nothing and only concerns the sign-up form, which is not a page you need in search results.

Can a real customer be refused?

Possibly, if several accounts are created from the same connection within an hour, or if a name is longer than 40 characters or contains 3 or more digits. The customer sees a clear message; you can raise the limit or turn off the name filter.

Is IP blocking enough?

Rarely on its own: bots change addresses often. It complements a honeypot and a per-IP account limit.

Official sources

This guide is for information only. Test every change (login, sign-up, checkout) and keep a backup before editing .htaccess or robots.txt.