My website was hacked

WordPress malware removal and hacked site repair

Google is warning people about your site, strange pages are showing up in search results, or visitors end up on casino sites? We’ll remove the infection along with its cause and help get the warnings lifted.

In short

Removing malware from WordPress takes more than a plugin scan. We start with a full backup of files and database, compare every file against the originals with WP-CLI, hunt for backdoors, rogue administrator accounts and spam in the database, then close the hole the attackers came in through. We clean up Google too: spam URLs return HTTP 410, and if your site has been flagged, we request a review in Search Console. It’s exactly what we did with our own site, orbitbuilder.pl, in November 2026. OrbitBuilder is a small studio that builds, secures and maintains WordPress sites.

of new vulnerabilities in the WordPress ecosystem in 2025 were in plugins Patchstack, State of WordPress Security in 2026
91%
is how fast attackers exploit roughly half of high-impact vulnerabilities after disclosure Patchstack, State of WordPress Security in 2026
24 h

Sound familiar?

How to tell this is your problem

Google says my site may be hacked

A warning in search results or a red screen in Chrome scares customers off before they even arrive. We start with the Security Issues report in Search Console, which lists sample infected URLs.

Visitors get redirected to casino or pharmacy sites

These redirects often fire only for visitors arriving from Google or on mobile, so the owner never sees them. We test the site from different devices and as Googlebot.

Google shows thousands of pages I never created

Japanese titles, fake designer goods, online pharmacies. That’s spam injected into the database or the files. On our old site there were 9,915 such posts.

There are links in the footer nobody added

Hidden links to other sites are usually injected by a modified PHP file. On our site, 2 infected files were doing it.

There’s an admin account I don’t recognise

A rogue account is a backdoor: even after the malware is gone, the attacker can walk straight back in. We review accounts, roles and active sessions, then rotate passwords and keys.

My host suspended the site or my emails land in spam

Hosts switch off sites that send spam or spread malware, and the server’s IP ends up on blocklists. We clean the site and help get the service back.

Causes

The most common causes

01

Outdated plugins and themes

Patchstack found that 91% of new vulnerabilities in 2025 were in plugins. A hole that has had a fix available for weeks, but was never updated, is a typical way in.

02

Nulled plugins and themes

Pirated copies of premium plugins from unofficial sites often come with a backdoor built in. They don’t get security updates either.

03

Weak passwords and no 2FA

One shared “admin” account, passwords reused on other services, no two-factor login. Bots try to log in to every WordPress site they can find.

04

Abandoned plugins

A plugin its author has stopped maintaining won’t get a fix even after a vulnerability is made public. It has to be replaced or removed.

05

Old copies and shared hosting accounts

A forgotten copy of the site in /old or /test, or several sites on one hosting account, so an infection in one spreads to the rest.

06

An infected computer

A trojan on the computer of someone who logs in to the dashboard or over FTP can capture passwords. That’s why we change every login after the clean-up.

How we fix it

Step by step

  1. 01

    Contain and back up

    We copy the files and database exactly as they are, because we’ll need them for analysis. We change hosting, FTP and database passwords, and if the site is redirecting visitors, we take it offline for now.

    first few hours
  2. 02

    Diagnosis

    We compare core and plugins with the originals (wp core verify-checksums, wp plugin verify-checksums), scan with Wordfence and review recently changed files, .htaccess, mu-plugins and server logs.

    4–8 hours
  3. 03

    Clean the files

    Core, plugins and theme are replaced with clean copies from official sources. Infected files go into quarantine rather than the bin, so we can work out what they did.

    1 day
  4. 04

    Clean the database and accounts

    We remove rogue accounts, spam posts, tags and categories, scripts injected into options and widgets, and suspicious cron jobs. We replace the keys in wp-config.php, which logs everyone out.

    1 day
  5. 05

    Clean up Google

    Spam URLs return HTTP 410, the sitemap lists only real pages and we request a review in Search Console. Google usually reviews malware cases within a few days, and spam cases can take up to several weeks.

    1 day + Google’s review
  6. 06

    Harden the site

    We update everything, remove unused plugins and themes, switch on 2FA and a web application firewall, disable file editing from the dashboard and set up off-site backups.

    1 day

Hacked WordPress site: what kind of infection is it?

“Malware on my site” covers several different problems, and each one is hunted down a little differently. These are the five infections we see most often:

  • SEO spam. Thousands of pages with Japanese titles, pharmacy offers or counterfeit goods, created in the database or as files on the server. They’re aimed at Google, not at your customers.
  • Malicious redirects. A script sends some visitors to a casino, a fake prize draw or a bogus browser update, often only those arriving from Google or on a phone.
  • Hidden links. Links to other sites injected into the footer or content, invisible to people and readable by crawlers.
  • Backdoors. PHP files and rogue admin accounts that let attackers return after a clean-up. Leave them in place and the infection comes back within days.
  • Card skimmers in stores. Code that captures what customers type into the WooCommerce checkout form.

We identify the type of infection before removing anything. We check the Security Issues and Pages reports in Search Console, run a site:yourdomain.com search in Google, fetch the site as Googlebot and as an ordinary phone, scan it from outside with Sucuri SiteCheck and VirusTotal, and compare the files on the server with the originals.

What not to do after a hack

  • Don’t restore a month-old backup without knowing how the attackers got in. They’ll come back the same way.
  • Don’t delete whole folders in a panic. You’ll lose the evidence, and often working parts of the site too.
  • Don’t request a review from Google before the site is clean. Google says doing so only prolongs the time your site is flagged as dangerous.

WordPress.org’s guide FAQ My site was hacked covers the first steps for site owners as well.

How we cleaned malware and spam off orbitbuilder.pl

In November 2026 we went through exactly what our clients come to us with. The old orbitbuilder.pl, built on Elementor, had been hacked. We found:

  • 2 files injecting spam links into the site footer,
  • a rogue administrator account none of us had created,
  • 9,915 auto-generated spam posts,
  • 2,238 spam tags and categories in the database.

We worked in the same order we use for clients. First, a full backup of files and database, so nothing was lost and we had material to analyse. Then the infected files went into quarantine and the rogue account was deleted. Next came removing the spam from the database and returning HTTP 410 for the spam URLs. A 410 tells Google the page has been removed permanently, and URLs like that drop out of the index.

Finally, we chose to rebuild the site rather than patch the old install. We wrote a custom theme with no page builder, removed 24 unnecessary plugins (5 remain), and gave both language versions correct hreflang plus 301 redirects from the old URLs. Today every URL in the sitemap passes a crawl check: HTTP 200, a single H1, a canonical URL and valid structured data. Fewer plugins means fewer ways back in.

A hack like this is easy to miss. The homepage usually looks normal, and the scale of the problem only shows in the Pages report in Search Console or when you search site:yourdomain.com in Google. That’s why we check both every month on every site we look after.

If your Google traffic dropped after the hack, cleaning up may not be enough on its own. See what we do when organic traffic drops. You can also check the state of your index yourself with our SEO audit checklist.

After the clean-up: how to avoid a second hack

Removing malware without closing the hole buys you a few quiet days. Patchstack’s data for 2025 shows why. 91% of new vulnerabilities in the WordPress ecosystem were in plugins, 46% of all new vulnerabilities had no developer fix when they were made public, and roughly half of high-impact flaws were exploited within 24 hours. Updating once a quarter isn’t enough.

After every clean-up we leave the site in a state that makes a repeat much harder:

  • core, plugins, theme and PHP all up to date, with abandoned plugins replaced,
  • unused plugins and themes deleted, because a deactivated plugin still sits on the server,
  • two-factor login for every administrator and separate accounts instead of a shared “admin”,
  • file editing disabled in the dashboard (DISALLOW_FILE_EDIT) and correct file permissions,
  • a web application firewall, such as Wordfence or Cloudflare rules,
  • off-site backups with several weeks of history, because infections are often discovered late,
  • file change monitoring and Search Console alerts.

Extra steps for WooCommerce stores

In a store we check more places. We review the checkout page source for foreign scripts, the payment gateway settings and the account number in the bank transfer instructions, accounts with the Shop Manager role, webhooks and REST API keys. Payment gateway and courier API keys are replaced with new ones. If customer data may have leaked, we help establish the scope, because your obligations to customers and the data protection authority depend on it.

The official Hardening WordPress guide has the full list. The simplest option, though, is to hand it to someone who does it every week, which is how our WordPress maintenance works. We apply the same rules to every site we build as part of our website design and development service. If your site is infected right now, get in touch straight away with its URL. We’ll start with diagnosis and securing a backup.

Engagement options

Pick a scope — we’ll tailor the quote

Emergency clean-up

For a site that’s infected right now, when time matters.

  • Backup of files and database before any changes
  • Diagnosis and clean-up of files and database
  • Rogue accounts and backdoors removed
  • The plugin or theme the attackers used updated or replaced
  • New passwords and access keys
Ask for a quote

Clean-up and rebuild

For a site that has been reinfected more than once, or runs on a dated theme with dozens of plugins.

  • Everything in “Clean-up and Google recovery”
  • A new theme with no page builder, as on orbitbuilder.pl
  • Plugins cut down to the bare minimum
  • 301 redirects and 410s without losing rankings
  • Ongoing care with updates and monitoring
Ask for a quote

What you get

Specifically, when we’re done

  • A full backup of files and database taken before the clean-up
  • A report on what we found, where, and the most likely way in
  • Clean WordPress core, plugin and theme files verified against checksums
  • Rogue accounts, spam and injected code removed from the database
  • Spam URLs returning 410 and a review request in Search Console
  • New passwords, new wp-config.php keys and two-factor login
  • A web application firewall, up-to-date software and unused plugins removed
  • Off-site backups and file change monitoring

FAQ

Frequently asked questions

How do I check if my WordPress site has malware?

Start with the Security Issues report in Google Search Console and a site:yourdomain.com search in Google. External scanners such as Sucuri SiteCheck and VirusTotal help, as does a Wordfence scan. An outside scanner can’t see a backdoor hidden on the server, though, so when we suspect an infection we compare every file with the originals.

How much does WordPress malware removal cost?

It depends on the scale: the number of infected files, the amount of spam in the database, how many sites share the hosting account and whether Google has flagged the site. After a quick diagnosis we give you the scope and price before the clean-up starts, so the invoice holds no surprises.

How long does malware removal take?

Diagnosis and clean-up usually take one to three working days. If Google has flagged the site, add its review time: usually a few days for malware, up to several weeks for spam. Spam URLs drop out of the results gradually as Googlebot revisits them.

Can’t I just restore a backup?

Only if the backup is clean and you know how the attackers got in. Infections often sit on a site for weeks before anyone notices, so a month-old backup may already be infected. Even a clean backup, without the hole closed, invites the next break-in by the same route.

How do I get rid of Google’s hacked site warning?

First the whole site has to be cleaned and the cause removed. Then we request a review in the Security Issues report in Search Console, describing what we fixed. The warning is lifted once the review passes. If Google still finds infected URLs, it shows more examples and the site needs another pass.

Why does Google show thousands of spam pages on my site, and how do I remove them?

An attacker’s script creates them, in the database or as files on the server, to rank other people’s offers on your domain. We remove the source and the pages, return HTTP 410 for them and make sure they’re not in the sitemap. For urgent cases we also use the Removals tool in Search Console. On orbitbuilder.pl it came to 9,915 posts plus 2,238 tags and categories.

Shouldn’t my hosting company remove the malware?

Some hosts scan their servers, quarantine suspicious files or suspend the site. But a host won’t close the hole in your plugin, remove spam from your WordPress database or clean up Google. That part falls to the site owner.

Do I have to report the hack to a data protection authority?

If attackers may have reached personal data, such as store customers or form submissions, GDPR requires you to notify your data protection authority within 72 hours of becoming aware of the breach, unless it’s unlikely to put people at risk. That decision rests with the data controller. We help establish from logs and files what the attackers could access.

Free first look

Tell us what’s happening. We’ll tell you what to do about it.

Share your site address and a short description of the problem. We reply within one business day with a first diagnosis and next steps.

What do you need?

Goal, deadline, links to inspiration — the more specifics, the more accurate the quote.

How we can help

Other problems we solve