How to Recover a Hacked WordPress Site Without a Developer on Call
You open your site on a Tuesday morning and something is off. A page redirects somewhere strange, a client emails to say your homepage looks wrong, or a warning lands in your inbox from Google. Nobody on your team writes code, and there is no developer to call. Take a breath: you can recover a hacked WordPress site yourself, and you can do it in a calm, ordered way. What follows is the same sequence our team walks site owners through, step by step.
The first signs your WordPress site has been compromised
Hacks are rarely loud. Most show up as small wrongness you notice before you understand it. Watch for these:
- Your site redirects visitors to an unfamiliar domain, or only redirects on mobile
- New admin users you did not create, or an admin account you cannot delete
- Strange posts, pages, comments or footer links appearing out of nowhere
- Search results showing spam titles or unrelated products for your domain
- A sudden traffic drop, or a warning in Google Search Console about malware or phishing
- Files with odd names in your hosting file manager, or a spike in outgoing email you did not send
- Hosting or security emails about brute-force logins, phishing, or an infected file
None of these prove a hack on their own. But two or more together almost always do, and it is safer to investigate than to wait.
What to avoid in the first hour
The instinct to fix things fast is what causes the most damage. In the first hour, avoid these five moves:
Do not delete the site or reinstall WordPress over it. You will destroy the evidence needed to find the entry point, and the same hole will still be wide open when you rebuild.
Do not log in from a shared or unfamiliar computer. If your machine is infected, you will hand the attacker your new credentials the moment you change them.
Do not keep changing passwords over and over without first removing the backdoor. The attacker usually still has a way in, and every reset is wasted.
Do not post about it on social media yet. You will attract scanners and opportunists before you have closed the door.
Do not ignore it and hope it clears up. Most WordPress compromises spread quietly – to other sites on the account, to your visitors, and to your search rankings.
Step 1: Isolate the site while you work
Put the site into maintenance mode, or temporarily password-protect it with your host’s tools. This keeps visitors away from malicious code and stops any further automated damage from spreading to customers. If your host has a staging or snapshot feature, take a snapshot right now, before you touch anything, so you have a rollback point.
Step 2: Change access from the outside in
Start with the accounts that lead to everything else: your hosting control panel, your domain registrar, and the email address tied to them. Change those passwords first, then WordPress admin logins. Turn on two-factor authentication wherever it is offered. Then remove any admin user you do not recognize, and reset the passwords of every remaining admin, editor and author.
Also reset your database password and your WordPress security keys (salt keys), because a stolen key set lets an attacker back in even with a new password. That sounds technical, but it is a single paste-and-save, and a good managed host will do it for you on request.
Step 3: Find what was changed
Compare your files against a clean copy of WordPress. Most hosts and security plugins will list files that changed recently, files with suspicious names, and any code that was not there at install. Look closely at the theme’s functions file, custom plugin folders, upload directories, and any file containing obfuscated or encoded code. Write down what you find – it tells you how they got in, which matters for the next step.
Also check for scheduled tasks (cron jobs) and unfamiliar database users. Attackers leave these behind precisely because owners forget to look.
Step 4: Clean or restore from a backup
You have two valid routes, and the right one depends on how much has changed:
Restore from a clean backup if you have one taken before the compromise, and the site has not changed much since. This is the fastest, safest path – but verify the backup predates the hack, then update everything and change all passwords immediately after restoring, or the old hole simply gets reused.
Clean the files manually if your newest backup is already infected or too old to be useful. Remove the malicious code, replace core files, theme and plugins with fresh copies from the official repositories, and reinstall anything you cannot verify. If the database contains injected content, remove it – but take an export first.
If you are cleaning manually, remember that a half-cleaned site is still hacked. Attackers commonly plant more than one backdoor, so assume at least two and keep looking until a full scan comes back clean.
Step 5: Verify and get back online
Before you take the site public again, run a full malware scan and confirm the results are clean. Then check the site the way a stranger would: homepage, a few inner pages, login, contact form, and checkout if you sell anything. Log out and try logging back in with the new credentials. Take the site out of maintenance mode, and request a review in Google Search Console if you were flagged – that clears the warning for visitors.
Step 6: Stop it from happening again
Recovery is only half the job. The other half is making sure you never repeat this week:
- Keep WordPress core, themes and plugins updated, and delete anything you are not actively using
- Enforce strong passwords and two-factor login for every admin account
- Run daily malware scans and act on alerts the same day
- Keep automated, off-site backups you have actually tested restoring from
- Limit login attempts and remove the default admin username
- Watch file changes, because new files in unexpected places are the earliest warning you get
Doing all of this manually is a part-time job, which is exactly why most site owners hand it to someone else. With managed WordPress hosting from wpFlys, updates, security scans, uptime monitoring and daily backups run in the background without you thinking about them, and if a site is ever compromised, our US-based team handles the de-hacking recovery – then walks you through what happened in plain English.
You do not have to do this alone
Recovering a hacked WordPress site is a sequence, not a scramble. Isolate the site, secure your access, find the entry point, restore or clean, verify, and then close the hole for good. Work through those steps in order and you will very likely get your site back within a day. And if you would rather have someone beside you while you do it, our team is one ticket away – no developer required, no jargon, just your site back online.
If you would rather never handle this again, take a look at how wpFlys keeps WordPress sites fast, secure and backed up, with real people on support when it matters.
