How to tell your website has been compromised, and what to do first
Redirects to other sites, Google warnings, unknown admins or foreign pages in search results. How to spot a compromised site, what to do in the first hours and how we clean one up.
A compromised website rarely looks dramatic. Often a customer notices before the owner does. Here is how to recognise it, what to do right away and what not to do.
How to recognise it
- The site redirects elsewhere. After clicking from Google, a foreign page opens, perhaps about gambling or dubious goods. It often happens only on mobile or only for visitors from search, so opening the site directly shows nothing.
- Google or the browser warns. A warning appears in search results saying the site may be dangerous, or the browser shows a full-page red alert.
- Search results contain pages you never created. Typically hundreds of addresses with text about foreign products or in another language.
- The admin has unknown users. A new administrator nobody created is one of the most reliable signals.
- The site slowed down or went down for no obvious reason. The host may even suspend it because spam is leaving it or foreign scripts are running on it.
- Strange emails appear. Customers get messages you did not send, or you receive bounces for messages you know nothing about.
- Files changed without you changing them. Unknown files on the hosting, or a modified page layout.
One symptom alone does not have to mean a compromise. Several at once are a reason to act.
What to do right away
- Don't panic and don't delete things in bulk. Removing the visible items wipes out the traces that show how the attacker got in. And if a backdoor stays, they will be back in a few days.
- Save the current state. A backup of the site and the database, even a "dirty" one. It serves as evidence and a basis for analysis.
- Change passwords. Site admin, hosting, database, FTP, and the email tied to the accounts. Do it from a computer you know is clean. Turn on two-factor authentication wherever you can.
- Check users and permissions. What you don't recognise, don't delete at once; note it down and show it to an expert.
- Limit the damage. For an e-shop, consider temporarily pausing orders. A pause of a few hours beats stolen payment details.
- Contact your host and someone who knows the field. The host can often tell where access came from. The rest is work for someone who knows what to look for.
What we do
The procedure is similar each time and adapts to the particular site:
- We secure the state and make a copy for analysis.
- We find what changed. Foreign code, new files, a modified database, unwanted users.
- We remove the backdoors. Deleting what is visible is not enough. We look for how the attacker got in and what they left behind.
- We close the original hole. An outdated core or plugin, a weak password, an unprotected form. Otherwise it repeats soon.
- We secure the site again and help with delisting at search engines if they flagged it as dangerous.
- We write a report in plain language on what happened and what we did.
Repairs are billed at 500 CZK per hour, and you get an estimate in advance, before we start anything. We only test and intervene in systems we have the owner's written consent for.
None of this guarantees an attack will not happen again. But the likelihood can be reduced considerably with regular updates, backups that can really be restored, and monitoring. In the article Website security audit we describe how we do such a check in advance. If your site runs on WordPress, also read our comparison of WordPress and a custom site.
Suspect something is going on with your site? See our compromised-site clean-up service or write to us directly.
More articles
How AI is changing website security, and what a small business can do
Attackers use AI to automate scanning and scam texts, and AI chatbots on your site add new risks. What a small company can do and how we approach AI integrations.
Website and e-shop security audit: what we check and what you get
Logins, updates, forms, payments, HTTPS and backups. What a website security audit covers, what the final report looks like and what an audit does not guarantee.