«Hello, as a result of a scheduled audit on your hosting we detected malicious code and suspended access to the account.» If that email arrived in the morning, your site has been blocked by the hosting provider — and it’s a solvable problem. Not a catastrophe, not “everything is lost,” not “you’ll have to rebuild from scratch.” In most cases the account is unblocked within 24 hours once you show the host that the malware was found, cleaned, and won’t return. This article gives a step-by-step technical guide on what to do in the first hours, how to work with support, and how to bring the site back online without losing data.
What “site blocked by the hosting provider” means and why it happens
When people say “site blocked by the hosting provider,” they usually mean one of three situations. The host has either stopped serving the site (the domain still resolves but returns a “account suspended” placeholder), closed access to the control panel and FTP/SSH, or done both at once. The files themselves remain on the server — they are not deleted. This matters: while the account is “suspended” rather than “closed,” you still have the data and can regain access through negotiation.
Hosts usually block a site for one of these common reasons:
- Malware and viruses. Backdoors in files, JS injects on pages, web shells in
wp-content/uploads/— the most frequent cause. The host either found them with its own scanner (ImunifyAV, AI-Bolit) or received a complaint from Google Safe Browsing. - Spam sent from your domain. A backdoor uses the
mail()function or direct SMTP connections to send tens of thousands of messages per hour. The host sees this in the outgoing-mail logs and blocks the account preemptively. - Abuse report from outside. A complaint about your domain or IP arrived from an external party: phishing, copyright infringement, or a distributed attack. The host must respond within 24 hours.
- Resource limits exceeded. CPU at 100% for several hours straight, MySQL connections hitting the limit — either a botnet on your site, a poorly written plugin, or a real DDoS. Shared hosting blocks the account so other clients aren’t affected.
- Non-payment or expired domain. No virus here, but the symptom is the same: the site is down and the panel is inaccessible. Check your balance first.
Host emails are often worded vaguely — you have to translate from “support-speak” into technical terms. Here are typical phrases and what they actually mean:
| Host’s wording | Real cause | First step |
|---|---|---|
| «Malicious code detected» | Malware in files (backdoor, web shell, JS inject) | Ask for the scanner report with the list of files |
| «Anomalous outgoing-mail activity» | Spam sent via mail() from a backdoor |
Request the maillog for the last 24 hours |
| «CPU/MEM limits exceeded» | Bots on the site, a bad plugin, or DDoS | Request the access.log for the peak-load hour |
| «Third-party complaint received» | Abuse: phishing, malware, DMCA | Request a copy of the complaint (abuse report) |
| «Violation of the terms of service» | Usually the same as above, just without details | Ask them to name the exact clause |
Right after you receive the email, don’t reply with “just delete everything and reinstall” — that’s the worst thing you can do. First you need a calm plan.
First steps: 30 minutes after receiving the email
When your hosting provider blocks the site, everything you do in the first half hour affects how quickly you can recover. The main goal is to document the situation and keep your options open, not to “fix everything right away.” Follow these steps in order.
Save the hosting provider’s email and take a screenshot
Move the email to a separate folder in your inbox and take a screenshot that shows the date, subject line, and headers. If the message includes a scanner report with a list of files, treat it like gold—don’t lose it. That report will tell you exactly where to look for malware and save you hours of manual searching.
Request a backup of the current state—even the infected one
If the backup feature in your hosting control panel still works, download the archive right now, before you make any changes. You need the files and database exactly as they are for two reasons: insurance (so you can roll back if something goes wrong during cleanup) and a sample of the infection for analysis (where the backdoor sits, which files were modified and when, and how the code got in).
Open a support ticket with the right wording
Don’t write “help, everything is broken.” Keep it short and specific: “Hello, I received a notice that my account was blocked for malicious code. Please: 1) give me read-only access to the files and database for investigation; 2) send the scanner report listing the infected files; 3) provide the web-server and mail logs for the last 7 days. I will finish cleanup within 24–48 hours and will not bring the site back online until the host confirms it is clean.”
This wording shows support that you understand the situation and are ready to work constructively, which greatly improves your chances of getting temporary access.
How to get temporary access: working with support
Most hosting providers will cooperate if they see a reasonable client. Each has its own internal process, but the logic is the same: they either open FTP in read-only mode, give you a temporary restricted SSH account, or let you download a full backup so you can work on another server.
What to ask the host
- List of infected files. If the host has already run a scanner, it has a text report with file paths. Ask for this first.
- Read-only access to files and database. So you can examine the code and tables without letting malware run.
- Web-server logs. At least the last 7 days—
access.loganderror.log. These show the URL that was used in the initial compromise. - Mail logs. If the block was for spam,
maillogwill show which PHP script started sending mail. - Backup. The most recent available archive of files and database, ideally from a week before the block (there is a good chance the backdoor was already there, but having a rollback point is still useful).
Support email template
Hello.
I received a notice that account [login/site name] was suspended on [date] because malicious code was found. I’m ready to fix the problem quickly.
Please:
1. Send the antivirus scanner report with the list of infected files.
2. Open FTP/SSH access in read-only mode for diagnosis and cleanup.
3. Provideaccess.loganderror.logfor the last 7 days.
4. Send a link to the most recent available backup.The site will stay offline until cleanup is finished. After I’m done I will contact you for a rescan. Timeframe: 24–48 hours.
Best regards, [name, contact info].
This text usually gets through the first line of support without being escalated to a security specialist, because it is specific and calm. With major hosting providers the response time for a ticket like this is typically 30–90 minutes during business hours.
Diagnosis: what to look for in files and the database
When support opened read-only access, the technical part begins. If you’ve dealt with cleaning up WordPress before, a lot of this will be familiar. I covered all the signs of infection and how to find backdoors in detail in the article “WordPress site hacked: what to do in the first 30 minutes” — here are only the key locations and commands that work in most cases I see.
Where malware usually hides
wp-content/uploads/— the media folder, which should not contain a single.phpfile. If one appears, it is almost certainly a web shell.- Site root —
wp-config.php,index.php,.htaccess. An unusual file size (for example,wp-config.phpat 50 KB instead of 3 KB) or garbage include lines at the top are immediate signs of an injection. wp-content/plugins/— plugin folders you never installed. Especially those with short names likewpcfg,wp-system,seo-tools,fancyboxx.- Theme (
wp-content/themes/.../functions.php) — injections at the beginning or end of the file, obfuscated code,base64_decode. - Database — the
wp_userstable for extra admins,wp_options(fieldssiteurl,home,active_plugins),wp_postsfor injected template posts or hidden publications.
Search commands
Through SSH (if the host opened access) I look for suspicious PHP files in uploads:
find wp-content/uploads -type f -name "*.php"
Any result is a candidate for deletion. Next, search for typical malware patterns in the code:
grep -rn "eval(base64_decode" wp-content/ 2>/dev/null
grep -rn "eval(gzinflate" wp-content/ 2>/dev/null
grep -rn "@assert\|create_function\|preg_replace.*\/e" wp-content/ 2>/dev/null
grep -rn "FilesMan\|WSO 2\|c99shell\|r57shell" wp-content/ 2>/dev/null
Files modified in the last 14 days (often showing “fresh” attacker edits):
find . -type f -name "*.php" -mtime -14 -not -path "./wp-content/cache/*"
In the database I check for extra admins:
SELECT ID, user_login, user_email, user_registered
FROM wp_users
WHERE ID IN (
SELECT user_id FROM wp_usermeta
WHERE meta_key = 'wp_capabilities'
AND meta_value LIKE '%administrator%'
);
If the results contain a user you did not create (especially a recent user_registered with a suspicious email), it is almost certainly a backdoor account.
wp checksum core and wp checksum plugin --all. These commands compare all core and plugin files against the official WordPress repository and show any changes. In my experience, this pair of commands saves a lot of diagnostic time.Treatment: cleanup + reinstalling the WordPress core
Once you know where the malware sits, the main work begins. The order of steps matters: if you change passwords before removing the backdoor, the backdoor will simply capture the new password. If you install a clean WordPress without removing database injections, the infection returns on the first request. Follow this sequence.
- Download a fresh WordPress from the official site — ru.wordpress.org/download. Not from a backup, not from mirrors, only from the original source.
- Delete all core files. Except
wp-content/andwp-config.php, remove everything else in the site root and unpack the clean distribution in its place. - Reinstall all plugins from the official repository. Do not copy
wp-content/plugins/from a backup as a whole — a backdoor may be hiding there. Get the list of active plugins from the database (wp_options, fieldactive_plugins), then download each one fresh from wordpress.org/plugins. - Check the theme. If the theme is custom, run
grepthrough it for malware patterns. If it is a popular theme (Astra, GeneratePress, Avada), reinstall it from the official source. - Remove PHP files from
wp-content/uploads/. Delete every.phpfile in this folder without hesitation. Keep images and documents. - Check
.htaccessfor injections. It should contain only the standard WordPress block. Remove any RewriteRule pointing to unknown domains. - Clean the database of extra admins and injections in
wp_options. Thesiteurlandhomefields must point to your real domain, not a third-party one. - Change all passwords in the correct order: hosting control panel → FTP/SSH → database → WordPress admin. Clear browser cookies between steps.
If the virus was noticed because the site redirects to a casino, a separate article covers all the typical injection locations: “Site redirects to casino or ads — how to find and remove malicious code”. A redirect injection is often the reason the host blocked the site for malware.
Getting Your Site Back Online: What to Write to Your Host
After cleanup, show the host that the work is done and the site is safe. Simply saying “I cleaned it” is not enough. Support expects a structured report that shows you understood what you were doing.
Sample Cleanup Report
Hello.
Cleanup for ticket [number] is complete. Brief report:
What was found:
• N infected files in
wp-content/uploads/(web shells such as FilesMan).
•eval(base64_decode)injection at the start ofwp-config.php.
• Extra adminwp_admin2in the database (created [date]).
• Injection in.htaccessthat redirected to an external domain.What was done:
• Deleted all PHP files from
wp-content/uploads/.
• Reinstalled the WordPress core version X.X from the official package.
• Reinstalled all plugins from the wordpress.org repository.
• Restoredwp-config.phpand.htaccessto their default state.
• Removed the extra admin fromwp_users.
• Changed passwords for the hosting panel, FTP, database, and all WordPress admins.Preventive measures:
• Updated the WordPress core and all plugins to the latest versions.
• Installed Solid Security Pro (or Wordfence) for monitoring.
• Enabled two-factor authentication for all admins.
• Set up automatic backups to third-party storage.Please rescan the site and lift the block if nothing is found. I am ready for any additional checks.
Most hosting providers review a report like this within a few hours to a day. After the rescan and removal of the block, the site returns online.
Prevention: Keeping the Host from Blocking the Site Again
In my experience, many sites that were once blocked by the host for malware get blocked again within a few months. The reason is simple: after cleanup the owner goes back to old habits—skipping updates, using weak passwords, or installing nulled plugins. To avoid future blocks, a basic hygiene routine is needed.
- ✓ Weekly updates. Core, plugins, and themes. Use an autopilot tool (Solid Security can do this) or update manually—just do it regularly. Most compromises happen through outdated plugins.
- ✓ No nulled plugins. “Free Elementor Pro” or similar offers always come with a backdoor. Use only official sources or paid subscriptions.
- ✓ Monthly user audit. Remove any admins you no longer need—former developers, temporary staff, or test accounts.
- ✓ 2FA for every admin. WP 2FA, Solid Security, or Wordfence—any plugin that supports Google Authenticator. A weak password plus 2FA is still safer than a strong password without it.
- ✓ Weekly scanner. Wordfence or Solid Security can scan files on a schedule and send a report. A backdoor will be caught within a week instead of months later when the host blocks the site.
- ✓ Backups to third-party storage with 30-day retention. UpdraftPlus + Amazon S3 or similar third-party storage. If needed, you can roll back 30 days with no data loss.
- ✓ Monitor outgoing email. On a VPS, set a limit for
mail()in the PHP config. On shared hosting, check the “outgoing email” section in the panel once a week—the numbers should stay steady.
When to Call a Specialist
Most cases of a site blocked by the host for malware can be fixed on your own in 1–2 days if you have basic WordPress and SSH knowledge. There are situations, however, where trying to fix it yourself usually makes things worse, and it is better to hand the job over right away.
- Two or more blocks in the past six months. This means a simple cleanup is not enough—there is an ongoing hole you are not closing.
- The backdoor has been present for several months. Older infections hide deep in the database, themes, cron jobs, and file permissions. A surface-level cleanup does not help without a full audit.
- No working backups and the site is commercial. Every day of downtime costs money. Experimenting on your own ends up costing more than hiring a specialist.
- Multiple sites on the account and all are infected. This is cross-site contamination; cleaning one site lets the others reinfect it. The work must be done in sync.
- The host threatens to delete the account. Time is critical—you need to export the data and get the site back online before the backups are removed.
If your hosting provider blocked the site for malware, I will handle the entire process for a flat $249: communication with support, diagnosis, cleanup, report to the host, and return to online status. Most sites are cleaned within 24 hours. 60-day guarantee—if the same infection returns, I clean it again at no charge. Free 10-minute check if you are not sure the site is hacked.
Need it now? Message me on Telegram @demento174—I reply within 2 hours, 24/7.