← All articles

Your WordPress Store Got Hacked: What to Do First

Shop owner checking his compromised WordPress store

A hacked WordPress store is more than a website problem. If you use WooCommerce, a compromised site can affect active orders, customer accounts, checkout, and the trust people place in your business.

Act quickly, but avoid rushing into changes that could destroy useful evidence or leave part of the hack behind. Here’s a practical order of steps to help contain the problem and start recovery.

Why a hacked store needs extra care

A brochure website might mainly display information. An online store also supports transactions and may hold customer details such as names, email addresses, shipping addresses, order histories, and account information.

Even if a payment provider processes card payments, that doesn’t mean every part of your store is outside the risk. WooCommerce explains that hosted payment fields or off-site processing can reduce how much card data your site handles, but the checkout page and wider store still matter for security. A compromised checkout could also be changed to load unauthorized scripts or redirect customers.

The key point: don’t assume payment-provider involvement means customer information is safe. Find out what systems and data may have been affected.

1. Stop the bleeding

Contact your hosting provider as soon as possible. Tell them you suspect a compromise and ask them to preserve relevant logs and help isolate the site if needed. Your host may also see suspicious activity or issues affecting the server.

If you can’t confirm that checkout is safe, disable it or take the store offline temporarily. A brief interruption is better than allowing more customers to use a potentially compromised payment flow. Ask your payment provider what immediate steps they recommend if you see unexpected transactions, checkout changes, or signs of payment information being collected.

Don’t test a suspicious checkout using a real payment card. Keep notes about what you observed and when, including your time zone.

Shop owner pausing a suspicious ecommerce checkout while investigating a security incident

2. Secure access to the store

From a trusted device, change passwords for the accounts that could control your website or payments. This may include WordPress administrators, hosting, control panel, database, FTP or SFTP, business email, and payment-provider accounts.

Use new, unique passwords, enable multi-factor authentication where available, and remove access for people who no longer need it. Review WordPress administrator accounts for unfamiliar users. If you suspect someone is still logged in, ask your host or technical support person how to invalidate active sessions safely.

If your store connects to payment services through API keys, webhooks, or other integrations, ask the provider how to review and rotate credentials. Don’t share passwords, secret keys, or full payment details in customer messages or public support forums.

3. Preserve a copy before cleaning

Before deleting files, reinstalling plugins, or restoring a backup, arrange a copy of the current site files and database. Ask your host for help if you’re unsure how to do this safely. Keep the copy somewhere separate from the live website and restrict access to it.

This copy may contain malicious code or sensitive information, so treat it carefully. It can help an investigator understand what changed and when. Also save relevant hosting notices, screenshots, suspicious URLs, order details, and a timeline of the steps you’ve taken.

A clean backup can be useful later, but don’t restore one over the current site before considering what evidence or order information might be lost. WordPress has a guide to recovering a hacked site with additional steps.

Website files, database records, and activity logs being examined during a store security investigation

4. Find out what was accessed

A malware scan can be a useful part of an investigation, but a scan alone may not tell you when the attacker got in, what they accessed, or whether they left a way back in.

Review available hosting and WordPress activity logs, recent file changes, plugin and theme changes, new administrator accounts, and unusual customer-account activity. Check orders for unexpected edits, suspicious patterns, or payment activity that your team doesn’t recognize. Ask your host and payment provider what information they can review.

Pay special attention to the checkout. Look for unfamiliar scripts or changes that load only on checkout or account pages, altered payment settings, and unexpected external connections. A visual check of the page is not enough: some malicious code can run in the background or appear only under certain conditions. If you find anything suspicious, avoid making conclusions from the code alone, get qualified technical help to investigate it.

5. Clean the site and fix the way in

Removing one suspicious file doesn’t necessarily remove the whole compromise. Malware can be hidden in plugin or theme files, the database, or other parts of the hosting account. Attackers may also leave a backdoor or use an outdated plugin or stolen account to regain access.

A thorough cleanup should identify and remove malicious code, review the database and accounts, and address the original entry point. That may mean updating WordPress, WooCommerce, plugins, and themes; removing unused or untrusted software; replacing affected files with clean copies; and strengthening access controls.

After the cleanup, run further checks before bringing checkout back. Confirm that payment settings and integrations are correct, and ask your payment provider whether it has specific checks or reporting steps for your situation. WooCommerce’s PCI-DSS guidance explains that using hosted payment processing can reduce the amount of cardholder data your site handles, but it does not remove every security responsibility.

The Hack Remover helps businesses with hacked WordPress sites investigate, clean, harden, and restore their websites.

6. Consider privacy and legal obligations

Once you have an initial picture of what happened, consider whether personal information may have been accessed. This could include customer names, email addresses, delivery details, order histories, account credentials, or other information, even if your payment provider processes card details.

Notification and reporting obligations depend on your jurisdiction, the type of data involved, and the circumstances of the incident. This article is not legal advice. Speak with a qualified privacy or legal professional, and consult your payment provider, insurer, or relevant authorities as appropriate. Keep a record of what you know, what remains uncertain, and when you learned it.

7. Address Google warnings

If Google Search Console or a browser is warning visitors about your site, first finish investigating and cleaning the issue across the site. Then review Google’s Security Issues report, fix the listed problems, test the changes, and request a review when you’re confident the site is clean.

Google notes that reviews can take several days or weeks. A review request is not a substitute for cleaning the site, and it does not guarantee that a warning will be removed immediately.

8. Tell customers clearly

If customers may be affected, communicate plainly and only share information you have confirmed. Follow professional advice about whether and how to notify people. Don’t speculate about what was accessed, and don’t ask customers to send payment card details by email.

What to say to customers

We recently identified a security issue affecting our online store. We have taken the store offline while we investigate and work to secure it. We are reviewing what information may have been involved and will share updates as we learn more. If you notice an unfamiliar transaction, contact your payment provider directly. We’re sorry for the concern and disruption.

Adapt this wording to the facts of your incident and any advice you receive. Use an official communication channel customers can verify, and provide a way to contact your business with questions.

Before reopening your store

Don’t reopen checkout just because the homepage looks normal. Confirm that the compromise has been addressed, administrator and customer accounts have been reviewed, payment settings are correct, and your technical support team has tested the store’s key flows. Set up ongoing updates, backups, access controls, and monitoring so you can spot suspicious changes sooner.

A hacked WooCommerce store is stressful, but a clear sequence helps: contain the issue, preserve a copy, investigate what was affected, clean and harden the site, address privacy responsibilities, and communicate carefully.

Talk with RachelAI receptionist · 613 706 8145