Skip to content
Skip to content
Digitalized Planet

My website was hacked: what to do in the first hour

Your site sends visitors to spam or casino pages, shows pages you never wrote, or Google warns "This site may be hacked". Here is what to do first, in order, and how to get back to normal.

USD 750 once, USD 79 a month. No PHP, no plugins, nothing for you to update.

Last updated October 22, 2026

Signs your website is hacked

  • Visitors coming from Google land on spam, casino, pharmacy or adult pages, while the site looks normal when you type its address. Google notes that hacked sites often show something different to visitors from search than to the owner.
  • Google results for your site show pages in another language or about products you never sold, often in Japanese.
  • Google shows "This site may be hacked" under your result, or the browser shows a red warning page.
  • Admin users you did not create, files you did not upload, or a home page you did not change.
  • Your host suspends the site or emails you about malware or spam sent from your account.

The first hour, in order

  1. Do not delete anything yet. Take the site offline or put it in maintenance mode through your host, so visitors stop being sent to harmful pages.
  2. Tell your host at once and ask two things: what they see in the logs, and whether the PHP on the server is patched (after October 2026, against CVE-2026-109618 and CVE-2026-109619).
  3. From a clean computer, change every password: hosting account, control panel, FTP or SFTP, database, every admin user of the site, and the email account they reset to. Turn on two-step sign-in wherever it exists.
  4. Download a copy of the hacked site and its database before anything is cleaned. Whoever repairs it will need it, and so might you.
  5. Find your last backup from before the hack. Check its date: a backup taken after the break-in brings the problem back.

Cleaning it, or starting over

A clean-up means finding every file and database entry the attacker changed. Attackers usually leave a hidden way back in, so a quick clean often ends with the site hacked again a few days later. Restoring a backup from before the hack is faster, but only works if the hole they came through is closed too: an old PHP version, an unpatched plugin or a stolen password.

For a small site that mostly presents a business, rebuilding is often simpler than cleaning: take the words and photos, leave the old files behind, and put the site on something with no PHP or plugins to break into. That is what we do: a website without maintenance.

Getting Google's warning removed

  1. Open Google Search Console for your site (add the site if you have not yet) and read the Security Issues report. Google calls it the source of truth for whether the problem is still there.
  2. Fix every issue it lists, including the sample addresses it shows.
  3. Request a review in that same report and say what you fixed. Google says a review takes from a few days to a few weeks.

Google's own pages: the Security Issues report and what Google counts as hacked content.

Was it the October 2026 PHP flaw?

Maybe, maybe not: most hacks still come through old plugins, themes and stolen passwords. If your server ran an unpatched PHP after 21 October 2026, though, assume that door was open too and have it closed before you put the site back online. What the PHP flaw is.

Done with PHP updates?

We rebuild your site as fast pages with nothing on the server for you to patch, and you still edit it from your phone.

Rebuild my website

Written with AI help; facts from google.com, developers.google.com; checked October 22, 2026.