A skimmer is a small piece of code added to your shop that copies your customers' card details as they type them, then sends them to a server run by the attacker. The order goes through normally, and so does the payment. Nothing warns you, and your customers find out about the fraud weeks later on their statement.
This article explains where this code hides on a PrestaShop store, how to look for it yourself, what to do if you find one, and how our anti-skimmer tool detects it.
Why a file scan is not enough
In most of the cases we see, the code that steals the cards is not stored on your server. The shop only contains one line that fetches a script from another domain, and that script runs in your customers' browsers. An antivirus that only reads the files on the server misses it.
On PrestaShop, that line often sits outside the files:
- in the database: a "custom code" field of the theme, the content of a CMS page, a product description, a module setting;
- in a theme or module file, after an exploited vulnerability or a stolen login;
- after the page has loaded: some scripts only appear once the page is displayed, added by another script. They do not exist in the source code the server sends back.
We have come across all three on real shops: a payment script hidden in a theme's custom code field, a loader that only appeared after the page was displayed, and hundreds of booby-trapped customer messages designed to run a script in the back office.
Signs that should alert you
A skimmer tries to stay unnoticed, so the signs are often indirect:
- customers report fraud on their card after buying from you;
- your bank or payment provider contacts you about compromised cards;
- the checkout page shows a card form twice, or shows a card form when your payment module normally redirects to the bank's page;
- your pages call domains you do not recognise.
How to check yourself
- Open the checkout page in your browser with the developer tools (F12 key), Network tab. Go through the steps up to payment without paying, and look at the list of domains called. Each domain should match a service you installed: payment, analytics, customer reviews, chat.
- Look at the custom code fields of your theme and of the modules that offer them (often "custom JavaScript" or "header code"). You should recognise everything in them.
- Be wary of unreadable code: a long block of letters and digits with no spaces, or an
atob(function followed by a long string, is a classic sign of hidden code. - Review the employee accounts and the modules installed recently.
A manual check gives you a snapshot at one point in time. A skimmer may only appear on some pages, for some visitors, or be added tomorrow.
If you find a skimmer
- Do not just delete the line. It was added by someone who had access: until the way in is found and closed, it will come back.
- Change every login from a clean computer: back office, database, FTP or SSH, hosting account.
- Inform your payment provider.
- Card theft is a personal data breach: in the European Union, if it poses a risk to your customers, it must be reported to your data protection authority within 72 hours of becoming aware of it (the CNIL in France).
- Our guide PrestaShop website hacked: what to do covers the first steps.
How the PrestaSecure anti-skimmer works
We look for skimmers in three places, because no single method sees them all.
1. Files and database
The shop analysis reads the PHP and JavaScript files, and also the database content where a script can hide: settings, CMS pages, product and category descriptions, customer notes and messages. It recognises known skimmer families and domains already used by attackers.
2. Pages as they are served
We regularly load public pages of your shop, the way a visitor would, and examine the scripts they call. A script pointing to an unknown domain is reported, and becomes critical if it appeared since the previous check.
3. The Observer, in your customers' browsers
This is the part that sees what the other two cannot. Since version 2.1 of the module, a small script records the domains and code your pages actually load in your customers' browsers, all the way to the payment page, including what is added after the page is displayed.
- This script is served from your shop's own domain and its code is readable. It records domains and scripts. It never reads the value of a field or a cookie, never contacts any domain other than your shop, and its reports are limited so it does not slow your pages down.
- Every unknown domain is checked by our team. A single list serves the whole network: a validated domain is accepted on every shop, a refused domain is treated as dangerous everywhere and triggers a critical alert on every shop where it was seen.
- A refused script is removed from your pages by the module, even if it was added in the database. If it is added after the page is displayed, it is neutralised before it runs, and data sent to a refused domain does not get through.
- Each item is shown with its reasons: "Reads payment card fields", "Obfuscated code", "Calls a known malicious domain", "Inserted by a visitor's browser extension"…
- Anything seen on the checkout page, or that looks like a skimmer, is handled immediately. Everything else waits to be confirmed by a second report, which stops a third party from filling the list with fake reports.
Between 6 and 21 November 2026, the Observer submitted 527 domains to our team: 401 were validated (payment, analytics and advertising services), 76 refused, and 50 were still being checked.
Who decides
- Essentials and Advance plans: recognised services are accepted automatically. For the others, you validate what you know and refuse what you never installed, helped by the reasons shown.
- Serenity plan: our team checks every new domain and blocks what is dangerous. You have nothing to do.
The anti-skimmer is included in every plan, for PrestaShop 1.6 to 9. The plans are described on the Pricing page.