payless.host
What to Do in the First Hour After Your Site Is Hacked
Updated Nov 22, 2026
1. Take the site offline
If you can still log into your hosting control panel, suspend the site immediately. Most panels have a "disable site" or "maintenance mode" option. This stops visitors reaching infected pages and prevents search engines indexing malicious content.
What can go wrong: you lose the control panel password or the attacker changed it. In that case, contact your host's support desk directly—most providers can disable a site from their end within minutes. Have your account details ready.
How to check it worked: open the site's URL in a private browsing window. You should see either a maintenance page or nothing at all, not the live site.
2. Change every password
Start with your hosting account, then the site's admin panel, then FTP and database credentials. Use a password manager to generate new ones—nothing you have used before, nothing you will remember.
What can go wrong: you change the admin password but forget FTP or database access, leaving the attacker a route back in. Change all of them.
How to check it worked: log out completely, clear your browser cache, then log back in with the new credentials. If you can access everything and the attacker cannot, the credentials are secure.
3. Document what you see before you touch anything
Take screenshots of anything unusual: files you did not upload, users you did not create, database entries that appeared overnight. Note the exact time you discovered the breach and what tipped you off—a defaced homepage, a warning from your browser, an email from your host.
What can go wrong: you start deleting files immediately and lose the evidence needed to trace how the attacker got in. Document first, clean second.
How to check it worked: you have a folder of screenshots and notes timestamped from before you began removing anything.
4. Check for new admin accounts
In WordPress, go to Users. In other platforms, find the equivalent list. Delete any account you did not create. Demote any account that was promoted to admin without your knowledge.
What can go wrong: you delete an account the platform needs to function, or you miss a backdoor account with a plausible-sounding name. If unsure, demote the account rather than delete it.
How to check it worked: the user list contains only accounts you recognise, all with appropriate permission levels.
5. Restore from a clean backup
If you have a backup from before the hack, restore it. Most hosting providers take daily backups—DreamHost, HostGator, and Hostinger all offer restore tools in their control panels. Choose a backup from at least two days before you noticed the breach.
What can go wrong: you restore a backup that already contains the vulnerability the attacker used, and they get back in the same way. If the site is hacked again within hours, go back further.
How to check it worked: the site is online, the content matches what you expect, and no unfamiliar files appear when you check the file manager.
6. Update everything immediately
Update the core platform, every plugin, every theme. Delete anything you are not using. An outdated plugin is the most common entry point.
What can go wrong: an update breaks the site. Test on a staging copy if your host provides one, or accept that a broken site you control is better than a working site an attacker controls.
How to check it worked: the version numbers in your admin panel match the latest releases on the developers' sites.
7. Scan for malware
Use your hosting provider's malware scanner if they supply one, or install a security plugin. Run a full scan and quarantine anything flagged.
What can go wrong: the scanner misses a backdoor file, or flags legitimate files as suspicious. Review each result individually rather than auto-deleting everything.
How to check it worked: the scan completes, reports what it found, and gives you a list of actions it took.
8. Contact your hosting provider
Tell them the site was compromised, what you have done so far, and ask whether server logs show how the attacker got in. Some hosts will investigate; others will not. Either way, they need to know.
What can go wrong: you assume they will fix it for you. Most shared hosting plans expect you to secure your own site files. Managed plans may help further.
How to check it worked: you have a support ticket number and a record of what you reported.
