It usually starts with a message you were not expecting. In this case, it was a Tuesday morning email from a customer: the site looked fine, but the buttons led somewhere strange. Then a second email arrived. Then the phone rang. For a small home-services company with six employees and no IT department, that is the moment the panic sets in, and the question on every owner’s mind is the same one thousands of people type into Google every month: my WordPress site got hacked – what do I do now?
This is the story of how that site went from hacked and offline to clean, secure, and back in business in about 48 hours. Not because the situation was easy, but because someone else knew exactly which steps to take first, and in what order. If you are reading this mid-crisis, take a breath. Recovery is almost always possible, and it usually does not take as long as you fear.
The first hours: how the hack was spotted
The warning signs were quiet ones. Pages loaded a few seconds slower than normal. A search result for the company name showed a description that had nothing to do with landscaping. And there was a new user account in the WordPress dashboard that nobody on the team recognized – which is the single most overlooked clue that a site has been compromised.
Within minutes of the report, the site was scanned. The scan found an injected script tucked into a plugin file, along with two modified theme files carrying a redirect to an outside domain. All three are common hallmarks of an automated WordPress attack rather than a targeted one: the site was not chosen, it was found. That distinction matters, because it means the fix is a known process rather than a mystery.
The first hour was not about fixing anything. It was about stopping the bleeding: taking the site offline so it could not spread malware to visitors, rotating every password tied to the site – hosting panel, WordPress admin, FTP, database, email – and telling the client plainly what had happened, what was already done, and when they would hear back next. No jargon, no guessing, just a timeline they could hold onto.
The 48-hour recovery, step by step
Isolate and capture evidence
Before a single file is deleted, the site is isolated and a full snapshot is taken of the hacked state. This snapshot is what lets a cleanup team see exactly what was changed, where the entry point was, and whether any additional backdoors were left behind. Owners often want the site wiped and restored immediately. Speed feels good, but wiping first means you may restore the same hole that let the attacker in.
Clean the infection properly
Cleanup means more than deleting the file that caused the redirect. The team worked through the WordPress core, themes, plugins, uploads, and database, removing malicious scripts, unauthorized admin users, and scheduled tasks planted to re-infect the site later. Core files were replaced with fresh copies from the official WordPress repository rather than patched by hand. Any plugin that had not been updated in over a year was removed outright.
Restore from a clean backup, then verify
The company had daily backups, but the most recent one was already infected. This is why backups alone are not a security plan – they are only useful if you know which copy predates the compromise. The team rolled back to a backup from four days earlier, then re-applied only the legitimate content changes made since. After the restore, the site was scanned again, then again 24 hours later, because a clean scan on day one does not prove a site is clean on day two.
Get back online with eyes on it
The site went live on the second evening, roughly 44 hours after the first email. For the next two weeks, uptime and file integrity were monitored closely, and the client was told to expect exactly that. Being back online is not the same as being out of the woods, and pretending otherwise is how sites get hacked twice.
What changed afterward
The site is now on managed WordPress hosting, which closed most of the gaps that made the attack possible in the first place. Daily backups are kept offsite and rotated, so there is always a known-clean copy. Security scans and malware detection run automatically, software updates are applied on a schedule instead of “when someone remembers”, and uptime and performance are monitored so a slowdown gets noticed before a customer does.
The owner’s role changed too – from site manager to business owner. She no longer opens a dashboard wondering what she is looking at. When something looks off, she sends one message to a US-based team that already knows her site, and the answer comes back the same day.
If your WordPress site is hacked right now
Here is the short version of what to do, in order. Change every password connected to the site. Take the site offline or put up a maintenance page. Do not delete anything until you have a snapshot. Find out which backup is clean. Remove malicious files, unauthorized users, and unknown scheduled tasks. Reinstall core, themes, and plugins from trusted sources. Restore, rescan, and monitor for at least two weeks.
You can do all of that yourself if you have the time and the stomach for it. Most business owners do not – and that is not a failing, it is a scheduling problem. De-hacking recovery, malware removal, and daily protection are exactly what managed WordPress hosting is for. Your site gets watched, backed up, and cleaned up by people who do this every week, and you get to go back to running your business instead of learning what a backdoor shell is at 11 p.m.
The site in this story is live today, ranking again, and taking bookings. Forty-eight hours after the first worried email, it was just a website again – which is the whole point. If you would rather never field that email in the first place, or you are fielding it right now, a US-based team is one message away.
