Skip to content

PHP security updates released 21 October 2026. The flaws are now being actively exploited, so check your website's PHP is up to date. Patches are available for older PHP versions too. What it means for your website

Website hacked?

Website hacked? What to check and what to do first

A practical guide for website owners: the signs to look for, what to do in the first hour, how to clean up properly, and when you may need to tell someone.
Published 4 November 2026 · Last updated 4 November 2026 · By Host Dada

Our checker can't tell you whether you've been hacked

It looks at your home page from the outside and doesn't scan for malware. A clean result doesn't mean your site is clean, and a missing security header doesn't mean it's been compromised. Use the checks below instead.

Signs your website may have been hacked

  • Visitors are redirected to another site, sometimes only on mobile or only when arriving from a search engine.
  • Search results for your site show pages you didn't create, or titles and descriptions in another language or selling products you don't sell.
  • Browsers or search engines warn visitors that your site is dangerous.
  • Your host has suspended your site, or told you it's sending spam or using unusual resources.
  • There are administrator accounts you don't recognise, or you've been locked out of your own.
  • New files, plugins or pop-ups have appeared that nobody on your team added.
  • Customers report strange emails, or card payments being misused after using your site.

Slowness or a broken page on its own is much more often an ordinary fault. Equally, a hacked site can look completely normal to you, as some hacks hide from logged-in administrators and from repeat visitors on purpose.

What to do in the first hour

  1. Don't start deleting things. Cleaning up too quickly can destroy the evidence of how they got in, and if you don't close that door, they'll be back.
  2. Make a note of what you've seen, with the time and date, along with screenshots and addresses.
  3. Contact your host. They can see logs you can't, may be able to isolate the site, and can tell you what backups exist. Ask them not to overwrite older backups.
  4. Copy the site as it stands, both files and database, and store it away from the server. Don't confuse this copy with a clean backup.
  5. Change your passwords from a device you trust: hosting control panel, SFTP or FTP, database, website administrators and the email accounts linked to them. Also check your domain registrar and DNS login. Turn on two-factor authentication where it's available.
  6. Consider taking the site offline or showing a maintenance page if it's harming visitors, such as by serving malware or capturing payment details.

What to check

From outside

  • Search your site in Google: enter site:yourdomain.co.uk and look for pages you don't recognise.
  • Google Search Console: look at the Security issues and Manual actions reports, and at whether unfamiliar pages have appeared.
  • Visit as a stranger would: click through from a search result, in a private window, on a phone using mobile data. Some hacks only appear this way.
  • Check your DNS and email records: confirm they still point where they should and that no one has changed them.

Accounts and access

  • Website administrator accounts, including when each was created.
  • Hosting users, SFTP or FTP accounts, SSH keys and database users.
  • Mail forwarding rules on the accounts that manage your website.

Files and database

  • Recently changed files, and PHP files where they don't belong, such as in an uploads folder.
  • Redirect rules in .htaccess or your server configuration, and your main configuration file (wp-config.php on WordPress).
  • Scheduled tasks (cron jobs) you don't recognise, as these are a common way for an attacker to get back in.
  • Site address settings, and script tags hidden in posts, pages or widgets in the database.
  • Server access logs, which can show how and when they got in if they go back far enough.

On WordPress

If you or your host have WP-CLI, these commands compare core and plugin files with the official published copies:

wp core verify-checksums
wp plugin verify-checksums --all
wp user list --role=administrator

These only cover software from the official WordPress.org directory, so premium plugins and your theme need checking another way. Any differences are a lead rather than proof of a hack, and clean results don't clear the site, since malicious code can also sit in uploads or the database.

Cleaning up properly

  1. Choose how to clean. Restoring a backup from before the hack is often the quickest route, but only if you know when it began. Hacks can go unnoticed for a long time, so a recent backup may be infected too. Otherwise, replace core software, plugins and themes with fresh copies, and review what remains by hand.
  2. Find the way in. Common routes include an out-of-date plugin or theme, an unsupported or unpatched version of PHP, stolen or reused passwords, and another infected site on the same hosting account. Clean every site in that account, or the problem can spread back.
  3. Update everything, and delete plugins, themes and old copies of the site that you no longer use. Check your PHP version too. If you run PHP, read our PHP security warning about the fixes released in October 2026.
  4. Change secrets again, after the clean-up. Include all passwords, database credentials, API keys and, on WordPress, the secret keys and salts in wp-config.php, which signs out everyone who's logged in.
  5. Ask search engines to review it. If Google has flagged your site, request a review through Search Console once it's clean.
  6. Keep watching. Check for returning redirects, new administrator accounts and changed files over the following weeks.

If that's more than you want to take on, it's reasonable to hire a professional. Ask your host first, or contact Host Dada to talk through your options.

Who you may need to tell (UK)

If personal data was or may have been exposed, such as customer details or enquiry forms, this may count as a personal data breach. Under UK GDPR, organisations must report a breach to the Information Commissioner's Office within 72 hours of becoming aware of it, unless it's unlikely to put people at risk. If the risk to people is high, they must be told as well. Keep a record of what happened even if you decide not to report it.

If your site takes payments, tell your payment provider. If you've lost money or been defrauded, report it to the police or the UK's national fraud reporting service, and if you have cyber insurance, tell your insurer early, as policies often have notification terms. This page is general information, not legal advice.

Where our checker can help

Once you've cleaned up, the free check is a quick look at what's visible from outside. It shows whether your home page redirects to a different website, whether your certificate and HTTPS are working, what software is being advertised and which security headers are in place. It also shows your PHP version if your server reveals it. None of that replaces the checks above, but it's a useful starting point for tightening things up.

Run the free check

Check your website now. It's free, needs no account and takes a few seconds. You can read exactly how the check works and what it can't see, or find out more about the Security Checker on hostdada.co.uk.

Check your website now

Free, passive and takes a few seconds. No account needed.

Check My Website — Free