Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

I think my website has been hacked

Short answer

If your site shows pages you did not make, redirects visitors or carries a warning in Google or in the browser, treat it as hacked. Change passwords from a clean computer, keep a copy of the site as it is, and do not delete things in a hurry. Cleaning means removing the injected files and closing the hole they came through.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • Google or my browser warns that the site may be hacked or harmful.
  • Search results show strange titles or pages in another language that I never made.
  • Visitors are sent to other websites, or I see pop-ups that were not there.
  • There is an admin user I do not recognise.
  • My host has suspended the site or sent a malware notice.

Why does this happen?

  1. An old plugin, theme or script has a known hole

    Attackers scan the internet for software that has not been updated and use the published weakness. A site nobody has touched for a long time is the easiest target.

  2. A password was weak, reused or leaked

    One stolen or guessed login for the admin panel, the host or the server is enough. A secret committed to a code repository can also leak access.

  3. Google can label a site it suspects of being hacked

    Google's help says it flags sites it suspects of hosting dangerous downloads, using harmful practices or being hacked, and the label can appear in search results, as a browser warning page, or both.

  4. The cleanup only removes the visible part

    Deleting the odd page you see leaves the way back in. Without finding the entry point, the same site is usually hacked again.

What can I do about it today?

  1. Do not panic-deleteDeleting files or the database can destroy evidence and your own content. First make sure a copy exists.
  2. Ask your host to keep a copy of the site as it isA snapshot of the files and database, taken now, helps the investigation. Keep your own earlier clean backup separate.
  3. Change passwords from a clean computerAdmin panel, hosting account, domain account and email. Use a new, long, unique password for each, and switch on a second sign-in step where offered.
  4. Check Google's view of the siteGoogle's help suggests opening the page in Chrome to see whether a warning appears, and looking at the Manual Actions and Security Issues reports in Search Console. If you do not have Search Console, ask me to set it up.
  5. Tell people if customer data may be affectedIf you store customer accounts or orders, you may have to tell customers or an authority, depending on where you operate. That is a question for a lawyer, not for me.
  6. Take the site offline if it harms visitorsGoogle's help says the site may need to be shut down while injected content is removed. A maintenance page costs less than a warning that scares customers.

When should I bring someone in?

  • You see the signs above and nobody on your side can read the site's files and logs.
  • Payments or customer accounts are on the site.
  • It was cleaned once and came back.

How do I handle it?

  1. Preserve, then investigateI take a copy of the files and database as they are and look for changed files, unknown users and odd scheduled tasks, working from the copy where I can.
  2. Remove the injected code and the way inHacked files are replaced from clean sources, unknown users are removed, and the outdated software or weak login that let the attacker in is closed.
  3. Rotate every secretPasswords, keys and tokens that could have been seen are replaced, and old access is removed.
  4. Ask Google to review, once it is cleanGoogle's help says to request a review in the Security Issues report only after the problem is fully fixed, or the flag will last longer. Reviews take as long as Google takes; its page gives a few days for malware and several weeks for spam-hacked sites.
  5. Set up updates and monitoringUpdates and alerts are put in place so the next hole is closed before someone uses it.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Can I just restore yesterday's backup?

Only if you know the backup is older than the break-in, and the hole is closed first. Otherwise the same entry point is open again.

How long until the Google warning disappears?

Google decides. Its help page says malware reviews usually take a few days and reviews of spam-hacked sites can take several weeks, and that warnings are typically removed within a few days after approval.

Do I need a lawyer?

If personal data of customers may have been exposed, speak to a lawyer about your duties to tell them. I handle the technical cleanup, not the legal side.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.