PrestaShop Malware Removal: Clean the Shop, Then Re-check
A PrestaShop infection almost always arrives through a module — most often a nulled or abandoned one — and the payload either skims checkout or hides spam pages your customers never see. Cleaning means finding the injected code, replacing the compromised module with a legitimate copy, patching, and rotating every credential. Clearing the blocklist flags is a separate job afterwards.
TL;DR: PrestaShop stores are usually compromised through a module, and the malicious code hides where a quick scan misses it — theme templates, overrides, the module folder itself. PrestaShop issued its own security alert about checkout skimmers in early 2026, and a skimmer Sansec found on a global retailer's PrestaShop store was still live when it published (Sansec, 2026). Clean in the right order, replace any cracked module, then request the vendor re-checks.
If a security vendor is warning shoppers away from your store right now, the emergency triage is here: what to do when your online store is blocked. This guide is the cleanup itself — how the infection gets in, where PrestaShop hides it, and the order to remove it in.
How PrestaShop stores get infected
PrestaShop infections are rarely exotic. The ways in are structural and repeat:
- A nulled module. A paid add-on downloaded from a "free download" site instead of the official marketplace. The crack removes the license check and often adds code the buyer never sees — a skimmer, a backdoor, or both.
- An abandoned add-on. A module the developer stopped maintaining years ago, still installed, with a flaw nobody will ever patch.
- An outdated core. The current PrestaShop release line is the 9.x series (9.2 at the time of writing) (PrestaShop); an old release misses the fixes shipped since.
- Weak back-office credentials. A short or reused admin password falls to automated attempts.
One more door, because an attacker opens it rather than a scanner finding it: theme template files. PrestaShop's security alert describes a script tag injected into the active theme's templates, replacing the payment buttons so the shopper is sent to a counterfeit payment form (PrestaShop Help Center, an article in French, 2026).
Signs your store is compromised
Watch for these — the first is what customers notice before you do:
- Checkout oddities. A payment step that looks different, an extra form field, or card details asked for twice. In the campaign PrestaShop describes, the payment buttons were replaced so the shopper landed on a counterfeit payment form.
- Redirects. Visitors land on pages you did not set up, sometimes only those arriving from search engines.
- Spam pages in search. Pharma, gambling or counterfeit pages indexed under your domain.
- Unknown admin users. Employee accounts you or your team did not create.
- Warnings from browsers or antivirus. A red full-page warning means a vendor has flagged the domain — usually the symptom that brings owners here.
One reason owners miss skimmers: they hide from logged-in admins. The toolkit Sansec described checks for an administrator session and switches itself off if you are signed in (Sansec, 2026). Check your checkout from a private window, logged out.
The nulled-module trap
A nulled module is a cracked paid add-on distributed outside the marketplace, and it is the most common delivery route for PrestaShop malware. Why you cannot trust one even after a clean scan:
- There is no honest baseline. With official software you diff your files against a fresh release. A nulled module has no release to diff against, so you cannot tell what was added.
- The payload is built to be missed. Injected code in nulled modules is usually obfuscated — encoded strings, hidden includes, code that wakes up only at checkout. A single-pass scan can report the store clean while it runs.
- There are no updates, ever. Legitimate modules get patched when a vulnerability is found; cracked copies do not. You stay on code with no security pipeline behind it.
- Cleaning the files is not enough. Even cleaned, the module stays unpatched and unverifiable — and the next payload can arrive with the next "update" from the same site.
The only safe move: uninstall and delete the nulled module, then replace it with a legitimate copy — from the official PrestaShop marketplace, the developer, or a different module doing the same job. The same applies to nulled themes: the same class of risk, with a template engine attached.
Clean a PrestaShop store, step by step
Work in this order — cleaning out of sequence is how stores get re-infected a day later. If files and databases are not your territory, involve a professional; the platform-agnostic version of this sequence is our step-by-step guide to cleaning a hacked website.
- Back up first. Files and database, before you change anything. The back office can generate a database backup (it lands in the admin folder's
backupsdirectory, per the official docs); your host's file backup covers the rest. - Take the store offline. Maintenance mode, so shoppers do not hit a half-cleaned checkout.
- Scan. Your host's malware tools plus a reputable site scanner; note every flagged file.
- Remove the injected code. Delete what the scan found, then hunt the places it did not check — the next section is the list.
- Replace module and theme files with official copies. Re-download clean versions and overwrite, and delete any file that is not in the official package. For the core, re-upload the matching files from the official release package (PrestaShop developer docs).
- Patch the core and every module — this closes the door the attacker used.
- Clear the cache. PrestaShop caches compiled templates under its
vardirectory; clear it from the back office so a tampered compiled template cannot keep serving. - Rotate every credential. Back-office passwords for every employee, the database password, FTP and SSH, and payment-provider API keys. Skip this and the attacker simply logs back in.
Check the usual hiding places
After any PrestaShop cleanup, walk these by hand — the folder map matches the official file-structure documentation:
modules/. Compare every module against its official release, and investigate folders that are not in your back-office module list. PrestaShop's security alert tells you to look for rogue modules namedmloaderorsimplefilemanagerunder/modules/(PrestaShop Help Center, an article in French, 2026).themes/, templates especially. PrestaShop's alert shows a script tag injected into_partials/head.tpl, a partial that loads on every page, with the Base64atob()function still in use in the injected code (PrestaShop Help Center, an article in French, 2026). Look for script tags you did not add, Base64-decoding calls such asatob(), and background requests to unfamiliar domains.override/. Class overrides load silently ahead of the original class. A store rarely has many; an unfamiliar file here deserves suspicion.upload/. This holds files customers upload for customizable products. Customer files, never PHP..htaccessin the web root. Check for rewrite and redirect rules you did not add.- The database. SEO spam and injected scripts can live in content records, not files. Search the tables for scripts and links you did not create.
- The back office. The employee list (unknown accounts) and the module list (modules you did not install).
Why the shop can still be flagged after cleanup
A clean store is not an unflagged store. Each vendor holds its own list, and a listed domain stays on it until that vendor re-checks — usually because someone asked. Nothing you do on the server clears a third-party list by itself.
- One hack trips several engines. A compromised checkout gets noticed by payment screening, antivirus URL filters and browser-protection feeds independently. In our November 2026 blocklist report, only 27% of flagged domains were listed by a single vendor.
- The biggest flag is manual. Google Safe Browsing — the feed behind Chrome and most browsers — has no API for review requests (Google). You clear it by requesting a review in Search Console yourself, then waiting.
Before calling the store recovered, confirm it: run a free multi-vendor blocklist check and see exactly who still flags the domain.
If vendors still flag the shop after cleanup
If the shop is clean and vendors still flag it, the removal service is a one-time €49 per domain; the pricing page has the rest. A correctly formatted removal request is sent to every flagging vendor that accepts one by email, within 48 hours of payment (in practice within the first hour). Vendors that only take a web form or manual review get a ready-to-paste request on the dashboard.
Hardening a PrestaShop shop
The cleanup removes today's infection; this list stops the next one:
- Update on a cadence. Core and modules, monthly at minimum — sooner when a security release lands. Stay on a supported release line.
- Module hygiene. Official marketplace or the developer only — every nulled module you keep is an unpatched backdoor candidate. Delete modules you do not use.
- Protect the back office. Installs from the official ZIP rename the admin folder automatically — keep that unguessable name and add
.htaccessor.htpasswdprotection (PrestaShop developer docs). Delete theinstalldirectory if it is still there; the docs require removing it after installation. Strong, unique passwords; no stray employee accounts. - Back up off-site, automatically. Files and database, stored somewhere other than the same server.
- Monitor. A weekly file-integrity check that flags new PHP files in module, theme, upload and cache directories helps catch injections early.
A clean store, then a clear reputation
A PrestaShop store recovers in two moves: code first, reputation second. Remove the injected code, replace whatever carried it — especially any nulled module — patch the core, rotate every credential, and clear the cache. Only then ask vendors to re-check the shop. Run the free blocklist check to see who still flags it, and once the store is clean, the removal service covers the requests.
A nulled module is a cracked paid add-on distributed outside the marketplace, often with injected code hidden in it. Attackers use exactly this channel to plant skimmers and backdoors on stores whose owners believe they installed a legitimate extension.
Look for the usual signs: unexpected checkout behavior, redirected pages, spam pages indexed by Google, and admin users you did not create. Compare module and theme files against their official releases, and scan the store with your host's tools — our scan checks vendor flags, not files.
It is possible, but more involved than WordPress: back up, find the injected code, replace compromised modules with legitimate versions, patch the core, then rotate credentials. If you are not confident with files and the database, a cleanup service is the safer route — the delisting request is still a separate job afterwards.
No. Vendors re-check only when they receive a request or on their own cycle, and each vendor is separate. That request work is what the €49 removal service covers.
Each vendor decides on its own schedule after a request arrives. A correctly formatted removal request is sent to every flagging vendor that accepts one by email, within 48 hours of payment (in practice within the first hour).