Guide · Security · 10 min read
Hacked online store: the signs of card theft, and what to do right away
In short: when an online store is hacked, its customers’ card details can be copied for weeks with no visible sign on the site. The first warning often comes from outside: customers hit by fraud shortly after ordering from you, or a call from your bank. If in any doubt, switch off card payments, copy everything before you clean anything, alert your bank, then notify the data protection authority within 72 hours of finding out. Every hour counts: while the malicious code stays online, each new order hands the attackers another card.
How card details get stolen from an online store
The theft does not happen at your bank: it happens on your website. An attacker adds a small program to your pages that copies what your customers type, then quietly sends it to a server of their own. Specialists call it a “skimmer”, like the fake card readers fitted to cash machines.
The program works in one of two ways, depending on where your customers type their card details:
- Reading the real form: if your customers type their card details straight into your page, the program copies each digit as it is entered.
- Showing a fake form: if payment takes place on your bank’s page, the attacker shows a fake form before it, in your store’s colours. The customer fills it in, sees “payment cancelled”, then reaches the bank’s real page and pays as normal. They receive their order and suspect nothing.
This is not a theoretical threat. In July 2022, a PrestaShop flaw let fraudsters plant fake payment forms on stores that were not up to date; it was fixed in version 1.7.8.7. In 2024, a paid “log in with Facebook” module served as the way in for the same kind of attack. And in February 2026, the PrestaShop store of one of the world’s ten largest supermarket chains was still showing a fake form four days after being warned.
Attackers most often get in through a forgotten module, or a PrestaShop version that has not been updated. And according to the Sansec researchers who uncovered that last attack, generative AI now helps attackers quickly produce very convincing forms, in each store’s language and colours.
The signs that should alert you
Card theft rarely shows on the website itself. The signs come mainly from your customers, your bank, and small details in the back office:
- Customers defrauded after ordering: several customers report payments they did not make, shortly after buying from you. Banks cross-check fraud cases: when several stolen cards were all used at your store shortly before, your store eventually stands out.
- A call from your bank or payment provider: this is often how it all starts. Take it very seriously, even if your website looks normal.
- Customers typing their card in twice: a customer says they saw “payment declined” or “payment cancelled”, then typed their card in again on the bank’s page.
- A card form on your own page: if your customers normally pay on your bank’s page and a card form appears before it, on your own website, it is almost always a fake.
- Traces in the back office: an employee account you do not recognise, a module installed without your knowledge, code added in the theme settings.
- A warning from the browser or your host: Google Chrome says the website is dangerous, or your hosting company reports a suspicious file.
What to do right away
The first instinct is often to delete the suspicious code as fast as possible. That is a mistake: you lose the evidence, and the attacker comes back through the same door. Follow this order instead, which protects your customers first:
- Switch off card payments. The safest option is to put the store into maintenance mode while you work out what happened: a fake form can stay on screen even if you disable your payment module. As long as the fake form is online, every order hands the attackers one more card.
- Keep the evidence. Make a full copy of the files, the database and the server logs (the record of its connections) before touching anything. They will show how the attackers got in, and how long card details have been leaking. When I step in on a hacked store, this is always my first move.
- Alert your bank or payment provider. Do it within the first few hours: they know these situations and will tell you what to do. They may also ask you to bring in, at your expense, an investigator approved by the card networks.
- Notify the data protection authority within 72 hours. That is the CNIL in France and the APDP in Monaco. Card theft poses a high risk to your customers: as a rule, they must be told as well, so they can block their cards without delay. Your message should say plainly what happened and over what period, which information is affected, the likely consequences, what you have done about it, what they should do (block their card, check their statements) and who to contact at your company.
- Report it to the police. In France, the official 17Cyber platform guides you step by step, and if you are insured against cyberattacks, your insurer only pays out if you report the attack to the police within 72 hours of discovering it. In Monaco, reports go to the police (Direction de la Sûreté Publique), and Cybermalveillance.gouv.mc, Monaco’s public cyber assistance service, helps businesses that have been attacked.
Cleaning up without leaving the door open
On a PrestaShop store, malicious code rarely hides in just one place. It has to be looked for everywhere:
- In the theme files: attackers add their code at the end of existing files. A file that suddenly grew, or was recently changed for no reason, must be checked.
- In the modules: especially those their developer no longer updates. This is one of the most common ways in.
- In the database: many themes let you add code from the back office, and that setting makes an ideal hiding place.
- In the cache: PrestaShop assembles the theme files and keeps a ready-made copy. As long as that cache is not cleared, the malicious code can keep showing, even after the files have been cleaned.
- In a backdoor: an attacker almost always leaves a small hidden file so they can come back. As long as it stays in place, no clean-up will last.
Then the door has to be closed: update PrestaShop and every module, remove those you no longer use, then change every password and key, without exception (back office, hosting, database, payment modules). The full method, step by step, is the same as for a WordPress site: see my guide to hacked websites.
Stopping it from happening again
Not all protections are equal: some really protect, others reassure without stopping anything.
| Protection | How much it helps | Why |
|---|---|---|
| The HTTPS padlock | Not enough | It protects the data on its way, not your page: the malicious code is part of the page itself. |
| Payment on the bank’s page | Reduces the risk | Attackers can no longer read the real card, but they can still show a fake form just before. |
| Updates to PrestaShop and its modules | Real protection | Many attacks go through a flaw that is already known, and already fixed. |
| Following security alerts | Gives early warning | The Friends-Of-Presta association publishes flaws found in PrestaShop modules: check whether yours are affected. |
| Monitoring of the payment page | Gives early warning | A tool alerts you as soon as a program appears or changes on the payment page. |
| Antivirus on your computer | Not enough | The malicious code sits on the store’s server, not on your computer. |
The card industry’s security rules, set out in the PCI DSS standard, point the same way. Since 31 March 2025, even a store whose customers pay on the bank’s page must confirm, in the security questionnaire it completes for its bank, that its website is protected against these small programs slipped into its pages.
Worried about your store?
If you think your store is affected right now, switch off card payments first, then get in touch. I start the way this guide recommends: a full copy of the store, before touching anything.
Then I look for the malicious code, the flaw it came through and, as far as the traces allow, the day it all began, before cleaning up, updating and changing every password and key.
I also help you gather what your bank and the data protection authority will ask for: what happened, for how long, and which customers to warn. You talk directly to the person who writes the code.
Let’s talk about your store See takeover and maintenance
Reply within one business day
Frequently asked questions
Doesn’t the HTTPS padlock protect my customers?
Not against this kind of attack. The padlock guarantees that nobody is spying on the connection between your customer and your website. But the malicious code is part of your page: it reads the card before it leaves, then sends it over an equally secure connection.
My customers pay on my bank’s page: am I safe?
You are less exposed, but not safe. Attackers cannot read what is typed on the bank’s page, so they show a fake form just before it. It is a very widespread technique today.
Will my customers be refunded?
A customer hit by a payment they did not authorise is, as a rule, refunded by their bank if they report it quickly. That is why you should warn your customers without waiting: they can block their card before it gets used.
What does my store risk?
Your bank may ask you to bring in an investigator approved by the card networks, at your expense, and pass penalties on to you. It may also suspend card payments until the store is secure. Acting fast, and openly, limits the damage, including to your customers’ trust.
How can I tell when the theft began?
From the server logs and the dates files were changed, which is why they must be copied before any clean-up. That date matters: it tells you which customers to warn, and the data protection authority will ask for it.
How much does it cost to fix?
It depends on the scale of the attack and the state of the store. I never quote without looking first. Describe the situation: I will send you a clear, itemised quote. Reply within one business day.
Sources
- PrestaShop security alert, July 2022 (official PrestaShop blog)
- Fake payment form on a major supermarket chain’s store, 2026 (CyberInsider)
- PCI DSS: what changed for online stores in 2025 (Jscrambler)
- When to notify a data breach (CNIL)
- 17Cyber, official help for cyberattack victims (French Gendarmerie)
Keep reading

Preparing your website for holiday traffic peaks: the method for Black Friday and Christmas
From Black Friday to Christmas, your online store gets far more visitors. The timeline and the method to keep it fast, stable and ready to sell.

PrestaShop 9.2: what’s new, and should you update?
One-page checkout, custom fields, an AI assistant: what PrestaShop 9.2 changes for your store, whether you should update, and how to do it safely.

An update broke my website: what should I do?
What to do when an update breaks your WordPress or PrestaShop website: the first moves, the steps to fix it and the routine to avoid the next failure.