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.
| Sign | Where to see it in PrestaShop | What it suggests |
|---|---|---|
| Several accounts created within minutes | Customers › Customers, sorted by registration date | Automated sign-up |
| First or last name with a link, digits or random letters | Customer list, First name and Last name columns | Spam bot or form testing |
| Disposable e-mail addresses (yopmail, mailinator…) | E-mail column | No intention to buy |
| No cart, no address, no order | Customer page | Account created for something other than buying |
| Welcome e-mails bouncing | The shop sender’s mailbox | Invented 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 feature | Where | Effect 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 Settings | When off, the shop sends no welcome message, so no relayed spam. Real customers lose that summary too. |
| Deleting customers with a re-registration choice | Customers › Customers, bulk actions | Cleans up afterwards; does not stop the next sign-ups. |
| Captcha, honeypot, per-IP limit | Not in the core | Need a module or a server rule. |
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
- Back up the database.
- Open Customers › Customers and sort by registration date.
- Filter suspicious names or domains; check that no selected account has an order.
- Tick the accounts, then Bulk actions › Delete selected.
- 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.
| Method | Effect on bots | Friction for customers | Upkeep |
|---|---|---|---|
| Manual deletion | None as prevention | None | Repeat after every wave |
| IPs refused in .htaccess | Good against a fixed source | Risky if the range is wide | List to maintain |
| Captcha | Good against simple bots | One more step | Keys and module to maintain |
| Honeypot + per-IP limit | Good against form-filling bots and bursts | No visible step | Low |
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.
| Protection | Default | What happens |
|---|---|---|
| Invisible honeypot | On | Sign-up refused if the field is filled; the bot’s IP is blocked (unless it is on your white list). |
| Suspicious names | On | Refuses 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 IP | 3 per rolling hour | Beyond that: “too many accounts were created from your connection, please try again later”. |
| Disposable mailboxes | Option, off | Refuses a list of 69 known domains (yopmail, mailinator, guerrillamail…). |
| Refused sign-up log | On | E-mail, IP, reason and date of each refusal, plus 30-day counters. |
Set-up, step by step
- Install the module from the Module Manager (PrestaShop 1.7 to 9 for the fake-account protection).
- Open the Registrations section: check that the honeypot, blocking of the trapped IP and the name filter are on.
- 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.
- Turn on the disposable mailbox filter if you do not want throwaway accounts.
- 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.
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
- Measure: how many accounts without orders in the last 30 days, and from which IPs?
- Update PrestaShop and your modules.
- Delete existing fake accounts while allowing those addresses to register again.
- Add friction-free protection: honeypot, name filter and per-IP limit.
- If a fixed source persists, refuse its IP or range (module or
.htaccess). - Check the refusal log weekly for a month, then monthly.