Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Security · Guide

How to Tell If Your WordPress Site Has Been Hacked

Short answer

Check Google Search Console for security warnings, look for admin users you did not create, and scan the site for malware. Then compare your WordPress core files with the official checksums. If two or more of these checks point to a hack, treat the site as hacked and start the recovery steps.

Key takeaways

  • WordPress.org lists blacklisting, a disabled site, malware flags and unknown admin users as clear signs of a hack.
  • Google Search Console has a Security issues report that shows hacked pages, malware and deceptive content it found.
  • A remote scan only sees public pages, so it can miss backdoors hidden in server files.
  • The wp core verify-checksums command compares your core files with the md5 checksums WordPress.org publishes.
  • A hack can hide from the site owner and show spam only to visitors from search results or on mobile.

What are the signs your WordPress site has been hacked?

A hacked WordPress site often shows a Google or browser warning, a host suspension, unknown admin users, strange redirects, or spam pages in search results.

WordPress.org calls these signs indicators of compromise.

Its hacked-site FAQ lists 7 of them: the site is blacklisted by Google, Bing or another search engine; the host disabled the site; the site is flagged for distributing malware; and visitors say their antivirus warns them. Read the FAQ on WordPress.org

The other 3 signs are a report that the site is used to attack other sites, things you did not authorise such as new users, and a hack you can see when you open the site.

Sucuri adds 5 more warning signs to watch for: a sudden drop in organic traffic, unexpected redirects or pop-ups, browser and antivirus warnings, unapproved changes to content or admin users, and a notice or suspension from your host. Sucuri lists these signs

One sign alone can have another cause. A traffic drop can follow a Google update, so check it against the steps in the guide on how to check if a WordPress site is penalized. Two or more signs together are far harder to explain away.

SignCheck firstWhat it often means
Browser or search warningSearch Console Security issuesGoogle found malware or hacked content
Redirects to unknown sitesSite on mobile data, logged outInjected redirect code
Spam pages in Google resultsSearch site:yourdomain.comContent injection, often called SEO spam
Unknown admin userUsers screen, Administrator filterAttacker created a backdoor account
Host suspension or abuse noticeAsk your host for the reasonSite used to send spam or attack others

How do you check Google Search Console for a hack?

Open Search Console, go to the Security issues report, and read every issue Google lists for your site.

The Security issues report shows hacked pages Google has found on your site, with steps to fix the problem. Google also sends a notification to the Search Console message panel when it detects malware, so check messages as well as the report. Google explains the report

  1. Open Google Search Console and pick the property for your site.
  2. Go to Security and manual actions, then Security issues.
  3. Read each listed issue and note the sample URLs Google gives.
  4. Check the message panel for malware notices you may have missed.

Also check who owns the property. Google advises you to verify that you own your site in Search Console and that no new, suspicious owners have been added. An attacker with owner access can hide warnings from you. Google covers this in its social engineering guide

A clean Security issues report is good news, but it is not proof the site is clean. Google only lists what it has found so far, and some infections hide from its crawlers.

How do you check what Google shows for your site?

Search Google for site:yourdomain.com and look for pages, titles or words you did not publish.

Google recommends the site: search operator as a regular check. Run it from time to time to see what pages Google has found on your site. If you see unknown pages, or topics you did not write, you may have been hacked. Google gives this advice

Look for pharmacy, gambling or loan words in titles, pages in a language you never used, and dozens of new pages you never created. Attackers inject these pages to use your site's standing in search results, a trick often called SEO spam.

Check the results the way a visitor sees them. Open your site logged out, on your phone over mobile data, and by clicking a result from Google. Hackers often hide their changes from logged-in admins, so the site can look fine to you and dirty to everyone else.

How do you check for unknown admin users?

Go to Users, then All Users, filter by Administrator, and check every account against the people who should have access.

An unknown administrator is one of the clearest signs of a hack. Attackers create an admin account so they can return after a cleanup, even if you change your own password. Note the username, email address and creation date of any account you do not recognise before you change anything.

Wordfence lists the same check among the signs of compromise it published in October 2026, along with unfamiliar PHP files in the uploads folder, unexpected scheduled tasks and unexpected outbound connections from the server. Wordfence lists these signs

Also look for users with odd roles. Check Editors and Shop Managers too, since a lower role can still edit content or inject links. If a user changed their own email address recently, ask the person first, since a changed email can be an attacker locking the real owner out.

How do you scan your site for malware?

Run a free remote scan first, then run a scan from inside WordPress, because the two scans see different things.

A remote scan visits your site the way a visitor or search engine would. Sucuri SiteCheck is a free remote scanner that checks a URL for malware, blocklist warnings, defacements, SEO spam, outdated software and injected code, with no setup. Paste in your address and read the report it returns. Sucuri describes SiteCheck

A remote scanner only sees what is public. Sucuri warns that it can miss backdoors, phishing pages and other threats hidden in server files, which is why a server-side scan matters. A plugin scan runs inside your hosting account and reads the real files and database. Sucuri explains the gap

  1. Run the remote scan and save or screenshot the result.
  2. Install or open a security plugin and run its full scan.
  3. Compare the two reports and note every file or URL either one flags.

Wordfence is one plugin option for the inside scan, and the steps to set it up are covered in the guide on how to set up the Wordfence firewall. A clean result from one scanner does not cancel a warning from the other.

How do you check if WordPress files were changed?

Run wp core verify-checksums from the server, and read the list of files that do not match the official release.

WP-CLI downloads the md5 checksums for your installed version from WordPress.org and compares them with the files on disk. It avoids loading WordPress while it checks, so tampered code does not run during the check. A clean run prints a success message. WP-CLI documents the command

wp core verify-checksums
wp core verify-checksums --include-root
wp plugin verify-checksums --all

The first command checks core files. The second adds the site root folder. The third checks plugins, but only plugins from the WordPress.org directory have published checksums to compare against. WordPress explains plugin checksums

If you cannot use the command line, ask your host to run it. Then check the files attackers change most often by hand: the .htaccess file, index.php, the theme header.php and footer.php, and the theme functions.php file. WordPress.org names these as common targets.

Also look for PHP files where none should exist. No PHP file belongs in wp-content/uploads, so any .php file there deserves a close look.

This is why plugins matter so much: Patchstack counted 11,334 new WordPress vulnerabilities in 2025, and 91 percent of them were in plugins, with only 6 in WordPress core itself. Sucuri cites the Patchstack report

How do you check for hidden redirects and spam pages?

Visit the site as a stranger would, on mobile data and from a search result, and note where each click actually lands.

Some hacks redirect only some visitors. A redirect that fires only on mobile, or only for visitors who arrive from Google, is a common pattern. Your own desktop visit can look normal while those visitors land on a spam shop or a scam page.

Google warns that hackers can turn off their attack when they think the visitor is the site owner. Its advice is to check sample flagged URLs from a computer that is not inside the network serving your site. Google gives this warning

Write down the redirect for each test: the page you opened, the device, whether you were logged in, and the final address. That record shows the pattern and helps your host or a cleanup service find the injected code.

How do you tell a hack from a plugin or hosting problem?

A hack leaves signs a bug does not: unknown users, changed files, a Google warning, or a host abuse notice.

A plugin conflict usually breaks a page the same way for everyone, and it starts right after an update. A hack is often selective, appears without a change you made, and leaves traces in users, files or search results. Use that contrast to sort the two.

  • A white screen after an update points to a plugin or theme problem.
  • Spam pages in Google results point to injected content.
  • A login that stops working for one user points to an account problem.
  • A new admin account nobody created points to a hack.

Check the exact version and install date of any plugin you suspect. In October 2026, some Rank Math SEO PRO 3.0.123 packages downloaded between 15 October 2026 at 20:02 UTC and 16 October 2026 at 07:12 UTC contained malware, and the clean replacement was version 3.0.124.

Wordfence rated the flaw CVSS 9.8, the highest severity band. Wordfence reported the incident

A plugin from outside WordPress.org or a vendor site is a weaker link. The guide on whether nulled WordPress plugins are safe explains why those copies carry extra risk.

Outdated plugins are a risk too, so the guide on how to find abandoned WordPress plugins shows how to spot the ones nobody maintains.

How do you confirm the hack before you clean it?

You have a confirmed hack when two or more independent checks agree, such as a Google warning plus an unknown admin or a failed checksum.

One warning can be a false alarm, but two checks from different sources rarely are. A scanner flag plus spam in Google results is a confirmation.

A host suspension plus changed core files is a confirmation too. A single odd page with no other sign is a lead, not a verdict.

  1. List every sign you found, with the date and time you saw it.
  2. Note what changed recently, such as a new plugin or a theme edit.
  3. Match each sign to a check in this guide and mark it confirmed or not.
  4. Keep that list safe, since it becomes the base of your incident record.

WordPress.org recommends this note-taking as the first step, before any cleaning. It asks you to record what made you think the site is hacked, when you noticed it and in which time zone, and what changed recently. WordPress.org gives this advice

Keep a copy of the site exactly as it is before you clean or restore anything. A backup taken now preserves the evidence and gives you a way back if a fix goes wrong.

The guide on how to back up WordPress covers the steps. The cleanup itself, the malware removal steps and the first-hour plan are separate topics, and each has its own guide.

What mistakes should you avoid?

The most common mistake is deleting files before you record what you found.

Deleting an infected file destroys the evidence of how the attacker got in, and the same hole can let them back in days later. Record the file name, its location and its date first.

  • Changing only your own password while an unknown admin account stays live.
  • Trusting one clean scan when another check still shows a warning.
  • Checking the site only while logged in as admin, when the hack hides from admins.
  • Ignoring a Google warning because the homepage looks fine to you.
  • Restoring a backup without finding the way in, so the hack returns.
  • Opening flagged pages in your normal browser instead of using the tools in this guide.

Frequently asked questions

Can a WordPress site be hacked with no visible signs?

Yes. Some infections hide from the site owner and show spam only to search engines or to visitors from search results. That is why you should check Search Console, run a scan, and look at the site while logged out on mobile data, instead of trusting how the homepage looks to you.

Does a clean malware scan mean my site is safe?

No. A remote scan only sees public pages and can miss backdoors hidden in server files. A clean result is a good sign, but it does not cancel a Google warning, an unknown admin user, or a failed checksum check. Use at least two different checks before you call the site clean.

How long does it take to check if a WordPress site is hacked?

The basic checks take about 30 to 60 minutes on a small site: Search Console, the site search, the Users screen, and a remote scan. The checksum check and a full plugin scan add more time on a large site, and a host reply can take a day. Write down each result as you go so nothing gets lost.

What should I do if my host suspends my site?

Ask your host for the exact reason and any log entries or flagged files they can share. A suspension often means the site sent spam or attacked other sites. Do not ask for the site to be switched back on until you know what was flagged, since the same abuse can start again at once.

Should I check my site if Google shows no warning?

Yes, if you see other signs such as strange redirects, spam in search results, unknown users, or a sudden traffic drop. Google only lists what it has found so far. The checks in this guide can catch an infection before Google flags it, which gives you a head start on the cleanup.

Do I need to check every plugin on my site?

You do not need to open every plugin file, but you should check the version and last update date of each plugin, and look for any plugin you do not recognise. Plugins carry most new WordPress vulnerabilities, so an outdated or abandoned plugin is one of the first places to look for the way in.

Sources

  1. FAQ My site was hacked WordPress.org
  2. wp core verify-checksums WordPress Developer Resources
  3. How to Prevent Malware Infection Google Search Central
  4. Social Engineering (Phishing and Deceptive Sites) Google Search Central
  5. How to Know if Your Website Is Hacked Sucuri Blog
  6. How to Scan a Website for Vulnerabilities Sucuri Blog
  7. PHP2Shell Update: Still No Confirmed WordPress Compromises Wordfence

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test