WooCommerce Malware Removal: Checkout Skimmers and Cleanup

unflagdomain Team·UPDATED November 13, 2026

On a WooCommerce store the infection that matters most sits in the checkout: a card skimmer injected into the scripts that render it. The other common one is hidden spam pages. The fix order: confirm the symptom, remove the injection, close the way in, rotate credentials, then ask the vendors flagging the store to re-check it.

TL;DR: The two common WooCommerce infections are a card skimmer injected into the checkout scripts, which captures payment details as customers type them, and spam or redirect content hidden in the install. Both usually arrive through an outdated or nulled plugin or theme, not through WooCommerce itself. Clean the store first — that part is yours — then ask every vendor flagging the domain to re-check it: blocklist flags outlive the malware.

WooCommerce runs inside WordPress, so the general cleanup in WordPress malware removal applies to the whole install. This guide covers what a store adds on top — the checkout, where the highest-value infection lives — and is written for store owners, not developers: how to tell you are infected, how the infection got in, how to clean it, and what still has to happen afterwards.

How do I know my WooCommerce store is infected?

WooCommerce infections usually announce themselves through the storefront, not the dashboard: odd checkout behavior, payment errors, redirects, spam pages in search, admin users you never created — or a Google or antivirus warning.

  • Checkout behaving oddly. Errors on submit, a payment step that reloads, or a form that looks subtly different.
  • Failed or duplicated payment messages. Customers report failed charges, double payments, or a confirmation that never arrived.
  • Unexpected redirects. Search or mobile visitors land on a different site — often only some of them, which is easy to miss.
  • Spam pages in your search results. Pages you never published — pharma, casino, foreign-language content — showing as yours.
  • Unknown admin users. Open the WordPress Users screen and look for accounts you did not create — the classic leftover of a compromise.
  • A sudden Google or antivirus warning. A red full-page screen in Chrome, or a visitor's antivirus or company firewall blocking the store.

One store-specific quirk: some payloads show a clean site to a logged-in admin and the injected version to everyone else, or fire only on the checkout. Check it in an incognito window from a phone, and check the checkout, not just the homepage.

How WooCommerce malware gets in

A WooCommerce store is a WordPress site with a checkout, so it is attacked the way WordPress sites are — through the extensions around the platform, not the platform itself. Patchstack reported that 97% of the vulnerabilities it added in 2023 came from plugins, with themes adding more and core under 1% (Patchstack, 2024). On a store, "plugins" means the whole sales stack: checkout builders, payment add-ons, shipping and discount extensions.

The common ways in:

  • Outdated plugins and themes. A known vulnerability in an extension is the most common door; anything touching the checkout is the most attractive target.
  • Nulled (pirated) plugins and themes. Cracks and nulled premium extensions can carry bundled backdoors and never receive updates.
  • Weak admin logins. A reused password, no two-factor authentication, an old admin account nobody watches.
  • A compromised third-party script. Every script your store loads — chat widgets, analytics, email tools — is code you serve and can be flagged for. That supply-chain model, including the Brevo incident, is covered in Third-Party Script Got Your Site Blacklisted.

Card skimmers at checkout: the Magecart pattern

The infection to worry about most is a card skimmer, grouped by researchers under the name Magecart: a small piece of JavaScript on a page rendering your checkout — a theme's copy of the WooCommerce checkout templates, a plugin's script, or a setting that prints a tag onto every checkout page. While a shopper types, it reads the card fields or hooks the form's submit handler and posts what it collects to a server the attacker controls. It stays quiet by design: the store keeps selling and the skimmer keeps collecting.

A documented WooCommerce case shows how current this is. In May 2026, Sansec reported active exploitation of CVE-2026-47100 in Funnel Builder by FunnelKit, a checkout plugin used on more than 40,000 WooCommerce checkouts. All versions before 3.15.0.3 let an unauthenticated attacker write arbitrary JavaScript into the setting that prints scripts onto every checkout page; attackers planted a loader disguised as a Google Tag Manager script that fetched a skimmer stealing card numbers, CVVs and billing addresses (Sansec, 2026). FunnelKit reportedly shipped a fix within 36 hours of the first report (Sansec, 2026).

Two lessons. If you run that plugin, update it — and treat everything in the sales stack as needing the fastest patch cadence you can manage. Note too where the malicious code lived: not in an obscure file but in a legitimate setting that prints scripts onto the checkout. "The checkout looks fine" is not the same as "the checkout is clean".

How to clean a WooCommerce store, step by step

Clean a store in this order: back up, scan, remove the injection, reinstall compromised code from clean sources, close the entry point, rotate every credential. The WordPress-wide detail lives in WordPress Malware Removal; below is what changes on a store.

  1. Back up first, even the infected version. You will want it if a cleanup step goes wrong.
  2. Scan from the server side. Use your host's malware tools or a reputable security plugin on the files, and inspect the database directly — including the checkout surface: theme template overrides and anything printing scripts onto checkout pages.
  3. Remove what was injected. Delete injected files. In the database, check wp_options and wp_posts, where injected scripts and spam pages hide, and check wp-content/mu-plugins — files there load automatically and cannot be deactivated from the dashboard.
  4. Reinstall from clean sources. Replace WordPress core, WooCommerce and every plugin and theme with fresh copies from official sources. Delete what you do not recognize and no longer use.
  5. Rotate every credential. WordPress admin passwords, hosting, FTP and database credentials, payment provider logins and API keys — then force all sessions to log out. Rotating credentials locks out anyone using stolen logins, but it does not remove a backdoor file; that is the next step.
  6. Re-scan and confirm clean. Look for unknown admin users, files that reappear after deletion, and outbound traffic to domains you do not recognize. If anything comes back, find the copy rebuilding it.

What a security plugin can and cannot do

Security plugins and server-side scanners are good at the file half of this: they compare your files against known-good copies, flag injected code and quarantine what they find — the right starting point for a cleanup pass.

What no scanner can do is change a vendor flag. A scanner reads your files; a blocklist records what a security vendor's systems saw in the past. Removing the injected file does not update that record — only the vendor re-checking the domain does. Two more limits:

  • Scanners have blind spots. Malicious code planted in a database setting, or printed onto the checkout by a legitimate script, may never exist as a file a scan can match.
  • Our scan checks flags, not files. The free blocklist check shows which vendors list your domain; it cannot tell you whether your store is clean. Use it for the half it covers, with a file scan for the other half.

Why your store is still flagged after cleanup

A blocklist flag is a record, not a sensor — records do not update themselves. Your store can be genuinely clean and still carry every flag the infection earned it. Three facts explain almost all of it.

  • A vendor's list changes only when that vendor re-checks the domain. Reputation systems do not watch your site; they hold what their scanners last saw, and listings sit there until a review is requested.
  • One hack trips several engines at once. In our November 2026 blocklist report, only 27% of flagged domains were listed by a single vendor, and the median domain carried 3 listings. Fix the warning you can see and the quieter ones remain, blocking visitors through products and filters you never hear about.
  • Nothing on-site changes a third-party list. New code, new passwords, a fresh install — none of it reaches the vendor's database. Only the vendor re-checking can change what the vendor holds.

If vendors still flag the store after cleanup

After the cleanup, if vendors still list the store, the removal service costs a one-time €49 per domain; details and limits are on the pricing page. 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.

Stopping the next infection

The cheapest recovery is not needing this twice. A short hardening list:

  • Patch on a schedule, not on a hunch. Turn on automatic updates where you can, and review the plugin list monthly — update what you keep, delete what you do not. An inactive plugin is still exploitable.
  • No nulled code. Replace any pirated plugin or theme with a legitimate copy — the most common deliberately planted backdoor.
  • Two-factor authentication on every admin account, plus least privilege — a shop manager does not need administrator rights.
  • Clean, off-site backups you have tested restoring from. When something gets through anyway, the backup decides whether it is an hour or a week.

An infection is not a verdict on how you run the store. The path out is standard: find it, remove it, close the hole, rotate credentials — then handle the flags, because flags do not reliably clear on their own. If you are not sure what still lists you, run the free check: it names the vendors flagging the domain right now — the to-do list for the final step.

// FAQ
  • The two common patterns are a card skimmer injected into checkout scripts, which captures payment details as customers type them, and spam or redirect content hidden in the WordPress install. Both usually arrive through an outdated or nulled plugin or theme rather than through WooCommerce itself.

  • Yes, if you are comfortable with files and databases: back up the store, find the injection, replace compromised files with clean copies, close the entry point, then rotate every password and key. Our cleanup guide gives that order. Cleaning the site does not by itself change a vendor's list; that takes a re-check request to each vendor that flags you, which you can file yourself or have us send.

  • No. A vendor's list only changes when that vendor re-checks your domain, usually after it receives a removal or false-positive request. Each vendor keeps its own list, so this happens one request at a time — that is the job the €49 removal service does.

  • If an active skimmer is running on your checkout, card details entered on your site can be captured until it is removed. Take the store offline or pause checkout while you investigate, and check your payment provider's requirements for what to report and when.

  • Each vendor decides on its own schedule once a request reaches it, and we do not promise a date. 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).