Book a call
Max Tymoshyn, founder of Norml Studio
Max TymoshynFounder, Norml Studio

Recovery and hardening for a hacked WordPress site

A hacked WordPress site often shows only part of the problem: spam pages in search results, redirects to other sites, an admin account you do not recognize, or a warning from Google or your host. Deleting what is visible does not stop the attack while the code that created it is still on the server. We find what the attacker changed and how they got in, close that path, put clean copies back and check the site again before the work is signed off.

A few clients we’ve worked with

99Legal / Kremenchuker Law GroupAstraZenecaCoxitDiet vs DiseaseFlorida seal — Regional Counsel projectMetroplex HomebuyersNasdaq Private MarketOffice of Criminal Conflict and Civil Regional Counsel, Second Region of Florida — Ita M. NeymotinPolaclubThe Farm Soho

What we do

Norml investigates and cleans up hacked WordPress sites, then hardens them. The work covers what the attack touched, how it got in, clean restoration and repeat checks, ending with a report that puts the remaining risks in order. A site that someone else already cleaned can get the review and report on their own.

What a hack recovery covers

The stages run in a fixed order: evidence is saved before anything is deleted, and files are removed only after access is reset and the way in is closed. Every finding and change goes into an incident log.

Solution
Websites
Platforms
WordPress
  • The compromise confirmed and its reach mappedFirst we confirm it is an attack and not a broken plugin, for example by comparing what visitors and search engines are served. Then we check every site, staging copy and subdomain in the hosting account, because code placed through one site can sit in the others.
    01
  • Evidence saved before anything is removedSuspicious files are copied to an archive where they cannot run, and each one goes on a file list with its location and status. Later scans are compared with that list, so a removed file that reappears shows up.
    02
  • Files, database and server settings inspectedWe look for what keeps the attack running: changed core files, code injected into the theme, unknown plugins and admin users, scheduled tasks, server settings that run code on every request, and database entries that load scripts or spam links.
    03
  • The way in traced and closedAccess logs, file dates and plugin versions point to how the attacker got in, such as a vulnerable plugin or a stolen password. That plugin is updated or removed, the passwords for WordPress, the database and the hosting account are changed, and every signed-in session is ended.
    04
  • Clean copies restoredWordPress core, plugins and themes are reinstalled from their official sources, or from your repository for custom code, wherever a clean copy exists, rather than patched by hand. If a backup or an older staging copy exists, we compare it with the live database first, so posts, orders and settings added since then are not overwritten.
    05
  • Spam pages and search resultsIf the attack added spam pages, we list their addresses from Search Console and crawl data. Once the site is clean, addresses matching the spam pattern return 410 Gone, after a check that the rule cannot catch real pages. If Search Console reports a security issue or a manual action, a review request goes in after the cleanup is verified.
    06
  • Repeat checks before sign-offWe scan the account again right after the cleanup and once more after an interval in which the site has had real visits, and check core and plugin files against their official checksums where these are published. A file that returns means something was missed, and the investigation reopens.
    07
  • Hardening and a report in order of riskHardening comes next, each change chosen for the site and tested before release: updates, unused plugins removed, admin users and roles reviewed, two-factor sign-in for administrators, file editing switched off in the WordPress admin and PHP execution blocked in the uploads folder where the server allows it. The report covers what was found, the entry point, what was removed and restored, and the risks that remain, in order of priority and in plain language.
    08
Josiah BallCo-Founder & CEO, HOMEEC

“Norml Studio's professionalism and responsiveness were impressive.”

Clutch review
Lucas SeyhunCEO, The Farm Soho

“They were proactive in suggesting improvements we hadn't considered.”

Clutch review
Gaius CooperDirector, Streamline Pump Solutions

“They delivered what they said they would, on time.”

Clutch review
Emma EstefaClient Success Manager, Metroplex Homebuyers

“They focused on how to make our daily operations easier, not just on building features for the sake of it.”

Clutch review
Bret MillerManager, Door Knock Pro

“They understood that the app needed to be practical for someone sitting in a car, not just look good on a desktop.”

Clutch review
Saima AhmedFounder, GoPetZen

“Their level of dedication to the success of the project and GoPetZen's business as a whole is unique.”

Clutch review

What we need to start

  • Access for each person on our teamInvitations to the WordPress admin and the hosting account, with file and database access or SSH where your host offers it, issued to each of us by name. We do not need shared passwords, and the ones in use are changed during the cleanup.
    01
  • What you have noticed so farWhen the problem started and what it looked like, such as spam pages, redirects, unknown users, messages from your host or warnings from Google, with screenshots if you have them.
    02
  • Every backup and staging copyAll backups, database exports and staging copies, with their dates. Older copies help date the attack and can hold content that was lost or changed.
    03
  • Search Console accessIf spam pages appeared in search results, access to Search Console for the domain and any crawl or backlink reports that list them.
    04
  • Other sites on the same hostingA list of every site on the hosting account and who looks after each one, since the check covers the whole account.
    05
  • Notes from earlier workThe theme and custom plugin code or its repository, licenses for paid plugins, notes from earlier developers and, if the site was cleaned before, that cleanup's report and any fixes still open.
    06
  • One person who approvesA named person who approves a maintenance page if one is needed, the password changes and the release of the cleaned site.
    07

How a hack recovery runs

  1. [Contain]

    If the attack is still active, a maintenance page can keep visitors away from injected code while we work. It goes up only with your approval.

    Step 01
  2. [Investigate]

    We save the evidence, map what the attack touched and find how it got in. Nothing is deleted at this stage.

    Step 02
  3. [Lock out and close the way in]

    Access is reset and the entry point is closed before any file is removed.

    Step 03
  4. [Clean and restore]

    Malicious files are removed across the account and clean copies of core, plugins and themes go back in. Content is restored from the backup or staging copy you approve, after it has been compared with the live site.

    Step 04
  5. [Verify]

    Repeat scans and file checks show whether anything came back. Spam addresses are retired, and any review request is filed once the site is clean.

    Step 05
  6. [Harden and hand over]

    Hardening changes are tested and released, and you receive the report. Our access is removed unless ongoing monitoring is agreed.

    Step 06

The people who do this work.

Meet the whole team

No account layer between you and them. These are the Norml specialists this work runs through.

Max Tymoshyn, founder of Norml Studio

Let's chat

“I've spent 10 years working across development and marketing. I started as a developer, but design, SEO and advertising were already part of the job. That taught me to treat a website as one system: the business, the content, the design and the code have to work together. At Norml, I lead the architecture behind our work and stay involved wherever strategy, design, development and search meet.”

Max TymoshynFounder & Architect

From the Norml blog.

Questions about recovering a hacked WordPress site

Can you promise the site will not be hacked again?
No, and nobody can promise that for a website. What you get is a record: the way in we found and closed, the files removed and restored, the repeat scans and the hardening applied. Ongoing monitoring helps catch a new problem early.
What if you cannot find how the attacker got in?
The report says so, lists the causes we checked and ruled out, and names the risk that remains. In that case every plugin and theme is reinstalled from a clean copy and every password is changed, whether or not it looked affected.
Will the site go offline during the cleanup?
Only if the attack is still active and you approve a maintenance page. Otherwise the site stays online while we investigate, and restored content is tested on a copy before it replaces the live version.
Our site was already cleaned up. Can you check it?
Yes. The review runs the same checks: files compared with official copies, admin users and access, scheduled tasks, server settings and the database. If the earlier cleanup left a list of fixes, we check each one and list any that are still open in the report. If something is still there, its cleanup is agreed as the next step.
Can you get the spam pages out of Google?
We make the spam addresses return 410 Gone and request their removal in Search Console. Google decides how fast they leave its results, so we cannot give a date for it.
Should we just restore an older backup?
Not on its own. A backup made after the attack began may contain the same code, and one made before it still has the weakness that let the attacker in. We use backups as a source of clean content, restored onto clean files once the entry point is closed.
Does this cover compliance for health or other regulated data?
No. Our work stays on the website itself: the WordPress install, plugins, hosting account and admin access, alongside your compliance specialist. Compliance risk assessments, office email and file accounts, staff training on phishing and phone scams, and devices and networks are outside it. We do not certify compliance or give legal advice.
What happens after the cleanup?
You can take the report and look after the site yourselves, or keep us on a monthly plan: updates tested before release, backups with regular restore tests, security and uptime monitoring, and a plain-English monthly report.
Do you install a security plugin?
Where it suits the site and the host, yes, during hardening. A security plugin or firewall adds protection, but it cannot be relied on to remove code that is already on the server, so it comes after the cleanup.
Who does the work?
Developers from Norml's own team, who also write the report. You talk directly with the people doing the cleanup.
What falls outside this work?
A redesign, a move to another host and SEO work beyond the spam cleanup are scoped separately. Hosting fees and paid plugin licenses are not included.

See how we work on live websites

Each case study covers the starting point, the work we did and what changed afterwards.

See all case studies