Security
How to tell if your WordPress site is hacked
Most hacked WordPress sites look normal to the owner and strange to everyone else. These are the signals that actually mean something — and the order to act in.
WordPress is not uniquely insecure. It is uniquely popular, which makes it a target, and it is unusually extensible, which makes it easy to leave a door open. The result is that thousands of sites are compromised without the owner noticing, because the attacker’s goal is usually not to deface the site — it is to use its reputation quietly.
These are the signs that hold up in practice, roughly ordered by how often they appear.
1. Search results show pages you never published
Search site:yourdomain.com in Google. Look for Japanese text, pharmaceutical names, casino terms, or pages with titles that make no sense. Attackers inject thousands of doorway pages to borrow your domain’s authority. They often hide them from logged-in administrators, so you will not see them while browsing.
2. Visitors are redirected somewhere else
Usually to a fake store, a survey, or a “your device is infected” page. The redirect may only fire for visitors arriving from Google or from a mobile user agent, which is why owners often cannot reproduce it. Ask someone else to check, or test in a private window with a mobile user agent.
3. Google shows “This site may be hacked” or a red warning
That is a serious signal, not a false alarm to dismiss. Check Search Console → Security Issues. Google lists the specific URLs and the category of problem it found. It is the most reliable free diagnostic available.
4. An administrator account you did not create
Go to Users and look at every account, including ones with no posts. Attackers commonly add a user with a plausible name and an email on a free provider. Also check for accounts with the administrator role that you assumed were editors.
5. Your own password stops working
If you are suddenly logged out and cannot log back in, someone changed the password. That is a direct sign of admin-level access, not a glitch. Do not keep retrying — go to the database or your host and reset it from there.
6. New or modified files you cannot explain
The classic locations are wp-content/uploads/ (which should contain media, never PHP), the root directory, and wp-includes/. A file with a random name, a recent modification date, and obfuscated code is not a plugin doing something clever.
Sort files by modification date in your SFTP client. A cluster of files changed at 3 a.m., all at once, is a strong signal.
7. Spam links in your content
Check the footer, widgets, and a few older posts. Injected links are often hidden with CSS (display:none or a tiny font) so they pass link equity without being visible. Search the database for <a href= patterns pointing at domains you do not recognise.
8. Your host suspends the account or emails you
Hosting providers detect outbound spam, phishing pages, and CPU spikes from crypto miners before you notice anything. Take the email seriously: suspension usually means the site has been used as infrastructure, not that the host is being difficult.
9. Traffic drops for no obvious reason
A sudden fall in organic traffic with no Google update to explain it can be a manual action. Check Search Console → Manual Actions. Blacklisted sites lose visibility fast, and the recovery clock starts when you fix it, not when you notice.
10. Odd admin behaviour
New plugins you did not install, settings changed back after you fix them, scheduled tasks you did not create, or a dashboard that feels “off”. Malware often lives in mu-plugins or a fake plugin with a legitimate-looking name.
11. Outbound email complaints
If your domain starts landing in spam folders, or you receive bounce messages for emails you never sent, the server may be relaying spam through a compromised script. Check the mail queue and the sending logs.
12. Reinfection after a cleanup
This is the clearest sign of all. If the site is clean and infected again within days, the entry point was never found. Something is regenerating the payload: a dropper, a cron job, a hidden admin, or a vulnerable extension that is still installed.
The first three things to do
- Take a full snapshot. Files and database, before deleting anything. It is your only evidence of what happened and your only route back if the cleanup goes wrong.
- Change the passwords you can change without breaking the site. Hosting, FTP, database. Do not wipe the WordPress admin users yet — you may lock yourself out and lose the audit trail.
- Do not run a “cleanup” plugin that deletes files automatically. It will remove legitimate files along with malicious ones and will not find the entry point.
Why scanners are not enough
A scanner compares files against known signatures. That finds yesterday’s malware. It does not find a dropper written for your site, an injected row in wp_options, a malicious cron event, or the vulnerable plugin that allowed the upload in the first place. Cleaning the visible payload while leaving the entry point open is the single most common reason a site gets reinfected.
A proper cleanup is an investigation: inventory the files, diff against clean sources, read the access logs, find the original upload, remove the intrusion, rotate credentials, then harden the specific weakness.
If you are in the middle of this now, WordPress malware removal is the process I run, including the part most cleanups skip: identifying how they got in.