MS-M

Hacked WooCommerce Store: What to Do Step by Step in the First Hour and the First Week

Your store is doing something it shouldn't. It redirects visitors to foreign websites, fills up with strange orders, or Google warns customers that the site may be hacked. You have one question: what do I do first?

The answer matters, because most of the damage (lost sales, blacklisting, lost customer trust) grows with every hour of delay, or with a panicked reaction: deleting files at random, or restoring an old backup that still contains the same hole.

This post is a plan for a store owner, not for an administrator. Symptoms, the first 60 minutes, who cleans up and how, how to stop it coming back, and when what you're seeing isn't a hack at all.

A dark metal strongbox with a hairline crack and a thread of navy blue light leaking out - an online store after a breach

How do you know it's a hack: the most common symptoms

Any one of these can be harmless. Several at once rarely are.

  • Your site redirects visitors to foreign addresses, especially people coming from Google, and especially on phones.
  • The browser or Google shows "This site may be hacked" or "The site ahead contains harmful programs".
  • There are new administrator accounts you didn't create.
  • Ghost orders and accounts with random email addresses keep appearing.
  • Your hosting provider suspended the account or emailed you about malicious code.
  • Google shows foreign pages or odd keywords under your domain.
  • Traffic and sales dropped suddenly, with no change in your advertising.
  • Your payment is being swapped. The order page looks correct, but after clicking "pay" the customer lands with a different payment provider than the one configured in your store. This is the easiest symptom to miss, because the cart and checkout look perfectly normal. More on it below.

The first 60 minutes: what to do and what not to do

This is the section worth printing. The order matters.

A dark stopwatch with a glowing blue hand - the first 60 minutes after discovering a store breach
  1. Secure access. Change passwords for WordPress, hosting or FTP, the database, and the email tied to the store. Do it from a clean computer.
  2. Take the store out of the line of fire. Switch on a maintenance page, or block traffic at the hosting level. If the store sends customers to malicious sites, every hour costs you trust.
  3. Write to your hosting provider. They often have their own scanners and logs, and some will take an evidence copy.
  4. Make a copy of the infected store and label it as infected. It's material for whoever cleans it up, not something to restore from.
  5. Check payments and integrations. Place a test order and see where the payment button really leads: is it the gateway you configured? Rotate the API keys for your payment gateway and couriers on the provider's side.
  6. Write down the symptoms and dates. Screenshots are enough. They help the contractor, and you'll need them if you report anything.

What not to do:

  • Don't delete files "by eye".
  • Don't restore an old backup before you know when the problem started and how the attacker got in. The same thing will come back.
  • Don't reply to emails with threats or demands.
  • Don't install three security plugins at once.
  • Don't leave the store taking payments if someone could have swapped the gateway or the payment link.

If you want a generic, step-by-step reference for any WordPress site, WPBeginner has an eight-step guide. Mine differs in one thing: it's written for someone who sells through the store and loses money for every hour of downtime.

Who cleans the store up and what it looks like

You have three options.

A scanner or your hosting provider. Often removes the symptom, not the cause.

A contractor. An audit, cleanup and hardening in one.

Rebuilding the store from scratch on clean sources, keeping your products and orders. This is a bigger job, and I describe the data side of it in rebuilding a WooCommerce store without losing SEO.

A magnifying glass over a dark circuit board with a chip glowing blue - auditing and cleaning up an infected store

A decent audit by a contractor, explained without jargon, goes like this: secure the evidence, look for hidden files and accounts, find how the attacker got in, clean up or rebuild the core, theme and plugins from clean sources, rotate passwords and keys, test the cart and payments, and watch the store after it goes back live.

Why isn't "I cleaned it and it works" enough? Because without finding the way in (say, an outdated plugin), the store gets infected again.

My terms: I take on post-hack cleanups as a one-off job, billed hourly at €44 net per hour plus VAT, with an hours estimate before I start. I don't give a total price in advance, because it depends on the scale of the infection. Ongoing care is a separate thing and is about prevention, not a condition for cleanup.

Beware of the cheap "virus removal" offer: no root cause, no report, no change of passwords and keys.

How did it get in: the most common ways

Outdated plugins and themes. The main source. According to the State of WordPress Security in 2026 report by Patchstack, 11,334 new vulnerabilities were found in the WordPress ecosystem in 2025, 91% of them in plugins. I wrote about what that means for the plugin-heavy choice in template vs custom theme.

Pirated ("nulled") plugins and themes. A ready-made back door, and a common cause.

Weak or reused passwords, no two-factor authentication, and accounts of former contractors that nobody ever switched off.

Shared hosting with weak isolation between accounts.

Neglected updates. A store that hasn't been updated for months.

Two cases from my own practice, both anonymous.

Case 1: the payment that went to a different provider

An outdated payment plugin had JavaScript saved in the database. It ran on the order and checkout page and swapped the payment link. On the order page everything looked fine. Only after clicking "pay" did the customer end up with a different payment provider than the one set up in the store, and which one was random.

It's a hard case to catch, because very few plugins save JavaScript in the database, and the symptom didn't appear every time. It ran from Friday until Sunday, when I sat down to fix it. The loss came to about €1,200 (around 3,000 PLN).

I started by verifying the files, which were clean. Only then did I analyse the database, looking for links pointing outside the store's domain. The client herself sped things up: during her own tests she noticed one odd link, and I knew where to look.

The cleanup: I removed the old plugin, wiped its settings from the database (they stay behind after uninstalling), and deleted unused accounts with no orders.

Two lessons. First, test the payment along the whole path, not just by looking at the checkout. Second, a report from a customer or a client is a valuable lead, so take it seriously.

Case 2: a redirect after an unpatched WordPress core

On a B2B store, the client hadn't updated the WordPress core, which contained a very serious vulnerability. There was no break-in to the store itself: visitors were being redirected to gambling sites. The store wasn't under my ongoing care. I'm telling this story as the effect of a neglected update, not as a story about hackers.

Spam orders and bot accounts

These don't always mean a break-in. Bots probe forms and flaws. The official WooCommerce developer advisory on spam orders and accounts from bots (2020) describes one such flaw in createaccount, fixed in WooCommerce 4.6.2. It's an older advisory, but the point still holds: what matters today is an up-to-date core and protected forms.

How to stop it happening again (the store owner's part)

A short list. What you do and what the contractor does.

  • Updates with a test on a copy of the store, and a backup before each one. I describe what that costs in the post on the cost of maintaining a WooCommerce store.
  • Backups stored off the store's server, and a tested restore. "We do backups" isn't enough.
  • Fewer plugins, only from official sources or trusted vendors, and never nulled ones. That's the number of risk dials in your store.
  • Accounts: separate for each person, two-factor authentication for administrators, and switching off accounts when a collaboration ends.
  • A firewall and form protection at the DNS level: I recommend Cloudflare, and in my view it's one of the first things worth setting up for security. The free plan is enough to start.

No one honestly promises "zero breaches". The real goal is quick detection and short downtime.

When it isn't a hack (and what this post won't solve)

Before you panic, rule out these cases.

  • Spam orders with no trace in your files and no new admin accounts. Often bots testing the cart, or forms with no CAPTCHA or limits. Protecting the forms is enough, with no need to "rebuild the store".
  • A Google warning may come from an external script (ads, a chat widget) or a certificate error, not from a hack.
  • A slow store and odd behaviour after an update is usually a plugin conflict, not malware. See a slow WooCommerce store.
  • Redirects on one device or in one browser only: a browser extension, or an infected computer on your side.

What this post won't do for you: it doesn't replace a contractor's audit, and it doesn't promise that nothing will ever happen to your store.

If you're in doubt, one rule is safe in both cases: secure first and make a copy, diagnose later.

FAQ

Look at the symptoms above: redirects, a Google warning, new admin accounts, ghost orders, and a payment leading somewhere other than the configured gateway. The diagnosis is confirmed by scanning and by a contractor reviewing the files and the database.

Secure access (passwords), take the store out of the line of fire (maintenance page), write to your hosting provider, make a copy labelled "infected", place a test order and check where the payment leads, and write down the symptoms. Don't delete anything at random and don't restore an old backup.

In simple cases, yes. But without finding how the attacker got in, the infection comes back. If payments could be affected, or you don't know where the problem is, it's better to hand it over.

With me it's €44 net per hour plus VAT, with an hours estimate before I start the work. The total depends on the scale of the infection. Ongoing care is a separate subject, covered in the post on the cost of maintaining a WooCommerce store.

Most often from bots probing forms and flaws, or testing the cart. It's not always a break-in. It's worth updating the core and securing the forms.

Yes, for example through code that changes the payment link. You check it with a test order, following the whole path to the payment provider's page.

From a few hours to several days, depending on the scale of the infection.

Updates tested on a copy of the store, backups kept off the server, fewer plugins from reliable sources, separate accounts with two-factor authentication, and form protection (for example Cloudflare).

Summary

The rule is simple: secure first and make a copy, diagnose later. Cleaning without finding the cause only postpones the problem. A breach is rarely bad luck. More often it's an outdated plugin or an unpatched core that nobody was watching.

Is your store behaving strangely? Write to me and I'll check whether it's a hack and what to do about it. If you'd rather not go through this again, there is also ongoing technical care for WooCommerce stores: updates with a backup and a check of the cart and payments.

Back to blog

Want to start a project?

Let's Talk

Get in touch

Your data is controlled by Marcin Siemieniuk-Morawski and used solely to reply to your message. Details in the privacy policy.

You can also email me directly at: kontakt@ms-m.pl