Key takeaways

  • Reply to the suspension notice in writing and ask for the flagged files, what access you still have, and what the host needs before reactivating the site.
  • Take a full backup of files, database and logs before you change or delete anything.
  • Don't restore an old backup just to get online; if it was taken after the infection started, the malware comes back with it.
  • The host's list is a starting point. Check uploads, cron jobs, admin users, other sites on the account and the original way in.
  • Only ask for a rescan when you have finished, with a short written summary of what you fixed.

The short answer

If your host has suspended your website for malware, work through it in this order. Reply and ask for the scan report and a way back into the files. Take a full backup before you change anything. Clean more than the files they listed, close the way in, and change every password from a clean device. Then ask for a rescan, with a short written summary of what you fixed. Deleting the flagged files and asking to be switched back on straight away is how accounts end up suspended a second time.

A suspension is frightening because the site has simply gone. No shop, no contact form, no way for customers to reach you. Hosts do it to stop visitors being harmed, and to stop the server sending spam or attacking other sites. You can recover from it, but treat it as an incident rather than a mess to tidy up quickly.

Why hosts suspend a site

Shared and managed hosts run their own malware scanners. They also get abuse reports from other networks, from Google Safe Browsing, and from customers who were redirected or had cards stolen. When a scan or a report looks bad enough, they disable the site, the whole account, or sometimes just the outgoing mail.

The public message is usually short ("This account has been suspended", or a branded unavailable page). The useful detail is nearly always in the ticket or email. Until you have that, you are guessing.

What to do in the first hour

1. Read the notice properly, and reply in writing. Ask for three things: the list of flagged files or URLs; whether you still have control panel, SFTP or SSH access (and if not, a temporary way in); and what they need to see before they will turn the site back on. Keep the conversation in the ticket. Phone calls get lost when the next shift takes over.

2. Check what you can still reach. Plenty of hosts leave the control panel, backups, SFTP or SSH open even when the website itself is off. Some will whitelist your IP if you ask. If you can't get in at all, say so in the ticket. You can't clean what you can't access.

3. Take a full backup before you touch anything. Copy the files and the database, and download whatever logs are still available. A panicked delete can wipe out the evidence of how the attacker got in, and sometimes the only copy of your content too.

4. Don't restore an old backup just to get online. If that backup was taken after the infection started, you'll bring the malware straight back and fail the host's next scan. If you aren't sure when the compromise began, leave restoring for later, as a careful decision rather than a shortcut.

5. Change passwords from a clean device. That means the hosting account, SFTP or SSH, the database, the CMS admin, and any FTP users that are still set up. Use a computer you trust, not one that might be infected itself. Turn on two-factor authentication wherever it's offered, and remove any admin users you don't recognise.

6. Don't email anyone your passwords. If you bring in help, they should arrange access properly, usually with a key you can revoke.

Free malware check

Is your site showing any of this?

Check for blacklisting, redirects, exposed versions and injected scripts in 20 seconds. No login, no install.

Public checks only · no login · no install

Why deleting only the flagged files is not enough

The list in the host's email is where you start. It isn't a full map of the compromise. Scanners tend to catch the obvious spam pages or one infected plugin file, and miss a webshell in uploads, a cron job that puts the malware back, an extra administrator, or another site on the same account that is still infected.

Remove only what they named, go back online, and the infection often returns. Some hosts treat a failed second scan more harshly than the first. A proper clean-up covers files, the database, scheduled tasks and users, and it finds the original way in. That might be an outdated plugin, a leaked password, a nulled theme, or another site on the same server.

If the site takes payments, take the checkout offline until you are confident it is clean. If customer personal data may have been accessed, you may have UK GDPR duties, including considering whether the ICO needs to be told. That is a separate decision; see our guide to website hacks and UK GDPR. This article is not legal advice.

How to ask for the rescan

Only ask for reactivation once you have actually finished. A short ticket does far more than "it's clean now". Include:

  • A summary of what you removed, replaced or hardened, including anything that wasn't on their original list.
  • Confirmation that WordPress (or your CMS), plugins and themes are up to date, and that unused or unlicensed add-ons have been removed, not just deactivated.
  • Confirmation that credentials have been rotated and unknown admins removed.
  • Any clean scan report or log you can attach.

Then wait for their rescan. Timings vary from host to host, and they aren't obliged to unsuspend you on any particular day. If Google or a browser is also showing a warning, that's a separate process, and it may not clear when the site comes back.

When to get help

Hand it to specialists if you can't get access, if malware has come back after an earlier clean-up, if there is more than one site on the account, or if payments or customer data may be involved. Wiping the server in a panic, or paying for the first "we'll get you unsuspended today" upsell without a proper clean-up, usually costs more than doing the job once.

Our hosting and migration help covers exactly this: we deal with the host, clean the account, and help you get a fair rescan. If you need someone now, use emergency help or call 01932 593642. Please don't send passwords through the form or by email. We'll arrange access with you.

Frequently asked questions

Why has my host suspended my website for malware?

Hosts suspend sites when their own scanner, or an abuse report from another network, Google Safe Browsing or a customer, suggests the site is harming visitors or the server is sending spam or attacking other sites. The detail is usually in the ticket or email rather than on the suspended page.

Can I just delete the files the host flagged?

Not on its own. Scanners often catch obvious spam pages or one infected plugin file and miss webshells, cron jobs that reinstall malware, extra administrators or other infected sites on the same account. If you only remove what was named, the infection often returns and the next scan fails.

Should I restore a backup to get the site back online?

Not as a shortcut. If the backup was taken after the infection started, restoring it brings the malware back. Take a fresh full backup first, and treat restoring as a later, careful decision once you know when the compromise began.

How long will the host take to unsuspend my site?

It varies by host, and they are not obliged to reactivate the site on a particular day. Ask for a rescan only when the clean-up is finished, and include a written summary of what you removed, updated and rotated.

PatientZero Incident Response Team · Digital forensics and incident response

Written by the PatientZero incident response team: the engineers who investigate and clean compromised WordPress sites and Linux servers every week.