Monday morning. You open your site and see Google’s red screen: “This site may harm your device.” Or a redirect to a casino. Or your hosting provider emails you: “Your site is sending spam, account blocked.” If any of that sounds familiar, your site has been hacked. Breathe. In the first 30 minutes we’ll locate the threat; within 24 hours we’ll have it back online. This is solvable—most of the hacked sites I clean come back fully, without data loss. The key is not to create new problems in the first hours of panic.

How to tell your site has really been hacked — 7 signs

Sometimes the symptoms are obvious (a casino redirect), sometimes the site looks fine and the problem only shows up in the logs or search results. I’ve broken down the 7 main indicators I check in the first minutes when a client contacts me.

Browser shows “This site may harm your device”

The loudest symptom. Chrome displays a red screen with a shield; other browsers show a warning banner. It means Google Safe Browsing has already blacklisted your domain—antivirus tools have scanned the pages and found malicious code or infected external scripts. Visitors won’t see the site again until you clean it and request a review.

Site redirects to casino, pharmacy, or adult sites

You load the homepage and get sent to 1xBet, a pharma store, or a casino. Sometimes the redirect only happens on mobile or only from search engines (cloaking—the bot sees a normal site, the visitor gets redirected). This is classic casino-redirect or pharma-injection. It usually works through an injection in .htaccess, a JavaScript snippet in the theme’s header.php, or the wp_options table.

Search results show pages in Japanese or Chinese

You search Google for your brand and see new result cards written in characters next to your real pages. This is Japanese SEO spam (or “Japanese keyword hack”)—attackers have created thousands of spam pages so Google indexes them and boosts their rankings. Their goal is usually to sell counterfeit goods or build link spam; they’re simply using your site as a platform.

Hosting provider emailed “Your site is sending spam”

Your host has noticed suspicious activity from your IP, threatened to suspend the account, or already blocked the site. It means a backdoor is using mail() or direct SMTP connections to send advertising and phishing emails from your domain. The host sees tens of thousands of outgoing messages per hour and hits the emergency button.

Ads you didn’t place appear on your pages

Banners for pharmacies, betting, or casinos show up—ads you never placed. Sometimes they’re just new links in the footer or sidebar; sometimes they’re full-screen modals. Technically this is an injection through wp_options (the siteurl field, widgets, or active plugins), less often a direct edit of the theme’s functions.php.

Admin login rejects the correct password

You go to /wp-admin/ with your usual login and WordPress says “Incorrect password.” You reset via email, but the new password still fails. The attacker has already changed your admin password and possibly the email address in the profile so you can’t recover it. They may also have created a “shadow” admin with a random login like wp_8a7f2.

Sudden spike in server load

Your host complains about CPU or memory limits. The site loads five times slower than usual. Your access.log shows tens of thousands of requests from different IPs in a single minute. Either your site has joined a botnet (sending spam, mining cryptocurrency, or attacking other servers) or it’s being used as a platform to brute-force other sites. Either way, it’s a serious compromise.

i

Tip. If you spot even one of these signs, follow the steps below in order. Don’t try to “fix everything at once”—panic moves usually make things worse.

First 5 Minutes — What NOT to Do

Paradoxically, in the first minutes after discovering a hack, it’s more important to know what not to do. Here are several common mistakes panicked site owners make that can seriously complicate recovery.

Don’t delete the entire site — you’ll lose the evidence

The urge to “wipe everything and start fresh” is understandable but harmful. An infected site contains clues: the location of backdoors, database changes, anomalies in the logs. Without them it’s impossible to understand exactly how the attackers got in, and you risk leaving the same hole open a week later. You need a snapshot of the site “as is” for later analysis.

Don’t change passwords from an infected session

A very common mistake. You see the admin area is accessible, quickly change the password, and feel relieved. In reality, if there’s a backdoor on the server or a JavaScript sniffer in the admin area, the new password goes straight to the attackers. First make sure you’re working from a clean environment — and change passwords in the correct order (more on that below).

Don’t hire “specialists” from $5 gigs

On a hacked site in a crisis it’s easy to become a victim a second time. A cheap “specialist” will either remove the visible symptoms while leaving backdoors — so the hack returns in a week — or sell your credentials and client database to competitors. The stakes are too high to trust a stranger with a vague portfolio.

Don’t try to “roll back” before diagnosis

The “restore from last week’s backup” button in the hosting panel looks like a lifesaver. But if the backup already contains a backdoor (which happens often — the infection may have occurred two weeks ago and only shown up yesterday), you’ll roll back to the same compromised state. Diagnosis comes first: determine the date the malicious code appeared. Only then restore from backup.

?

Worried about making it worse? Message me on Telegram @demento174 or WhatsApp +995 555 18 41 06 — I’ll tell you what to do right now for your specific situation, at no charge. Cleanup service — if you decide you need hands-on help.

Actions for the First 30 Minutes — Checklist

Now for the practical steps. These five actions are done in sequence, take about half an hour, and document the situation so you can work calmly afterward.

Step 1 — Block visitors via .htaccess

While the site is infected, every visitor receives malware or a redirect. Google penalizes the site in search results for this, and Google Safe Browsing flags the domain as dangerous. So the first move is to show a maintenance page to everyone except you.

Create a file called maintenance.html in the site root with the text “The site is temporarily down for maintenance, we’ll be back soon.” In .htaccess add:

RewriteEngine On
RewriteCond %{REMOTE_ADDR} !^123\.45\.67\.89$
RewriteCond %{REQUEST_URI} !^/maintenance\.html$
RewriteRule .* /maintenance.html [R=503,L]
ErrorDocument 503 /maintenance.html

Replace 123.45.67.89 with your IP address (find it at whatismyipaddress.com). Now all visitors see the maintenance page while you work on the site freely.

Step 2 — Make a backup in the current infected state

Copy the files and database exactly as they are — this is your evidence of the infection for analysis. Via SSH:

cd ~/public_html
tar -czf ~/site-infected-$(date +%Y%m%d).tar.gz .
mysqldump -u DB_USER -p DB_NAME > ~/db-infected-$(date +%Y%m%d).sql

Save both archives to an external drive. Don’t touch them — they’re evidence and insurance. If anything goes wrong during cleanup, you always have a clean rollback point.

Step 3 — Take screenshots of the symptoms

Open the site in a browser with DevTools open (Network tab). Capture screenshots of:

  • The symptoms themselves (red screen, redirect, Japanese pages in search results)
  • Network requests in DevTools — where the requests go and what the responses are
  • Emails from your hosting provider or Google Search Console (if any)

You’ll need these for a reconsideration request to Google and for communicating with your host.

Step 4 — Notify your hosting provider and ask for 24 hours before blocking

Open a support ticket: “The site has been hacked, I’ve started cleanup, please don’t suspend the account for 24 hours — activity will gradually stop.” Most hosting providers will work with you if they see you’re aware of the problem and actively addressing it.

If your host has already suspended the account and is threatening deletion, ask whether a temporary restoration for cleanup is possible. Sometimes it’s easier to migrate the site to another host temporarily than to wait for unblocking.

Step 5 — Change passwords in the correct order: hosting → FTP → database → WordPress admin

Passwords must be changed in this exact sequence — otherwise an attacker with backdoor access can intercept the new password. Between steps, clear your browser sessions (Ctrl+Shift+Del → cookies for the hosting domain and the site).

  1. Hosting control panel password. Use email or SMS recovery, not the active session
  2. FTP/SSH passwords. In the hosting panel → FTP section → change the password. It’s best to delete existing SSH keys and create new ones
  3. Database password. Create a new MySQL user, update wp-config.php, then delete the old user after a successful test
  4. WordPress admin passwords. Via direct database edit (UPDATE wp_users) or email reset — after cleaning functions.php of any potential interceptors

Where to Look for Viruses in WordPress

Attackers usually hide code in a few typical places. Knowing these locations saves hours during manual cleanup. I’ve broken down the four main areas where you should start digging first.

Folder Candidates: wp-content/uploads, plugins, themes

The most popular spot for backdoors is wp-content/uploads/. By WordPress logic, only media files (images, PDFs, videos) should end up in this folder. Any .php file inside uploads/ is a 100% sign of infection. Attackers like to hide webshells in subfolders such as uploads/2024/03/ under harmless names like thumb.php, cache.php, or logo.php.

Find all PHP files in uploads via SSH:

find wp-content/uploads -type f -name "*.php"

If the output is not empty, every file found is suspicious and should be checked. Do the same in wp-content/plugins/ for plugin folders you never installed — especially ones with short names like wpcfg, wp-system, or seo-tools.

Marker Files: Suspicious .php in uploads, extra code in wp-config.php

Core WordPress files — wp-config.php, index.php, .htaccess — should look standard. If the top or bottom of wp-config.php contains suspicious include statements, long base64 strings, or calls to eval(), that’s an injection.

Compare core file sizes against the originals. A clean wp-config-sample.php is about 3 KB. If your wp-config.php suddenly weighs 50 KB, it contains extra code. The same applies to wp-load.php and wp-blog-header.php — they should stay short.

What a webshell, backdoor, c99, r57, FilesMan actually are — in plain terms

Webshell — a PHP file that gives an attacker a web interface to control the server. Through the browser they can upload new files, edit existing ones, run operating-system commands, and read the database. Well-known shells include c99, r57, FilesMan, WSO, and b374k.

Backdoor — a hidden door. Often just a tiny PHP snippet tucked inside a normal plugin or theme that runs arbitrary code when a specific GET parameter is supplied. A backdoor can be as small as 50–100 bytes — nearly impossible to spot by eye in a gigabyte-sized WordPress site. That’s why scanners are used.

Code signs: eval(base64_decode(…)), obfuscated JS

Typical patterns of malicious PHP code that show up during manual searches:

  • eval(base64_decode(…)) — runs arbitrary code packed in base64
  • @assert(…) — executes a PHP expression from an HTTP parameter (assert can take a string and treat it as code)
  • create_function(…) — builds a function from a string; in legacy PHP this is a normal way to compile code dynamically, but in malware it’s a way to run supplied code
  • preg_replace with the /e modifier — an old flag that treated the replacement as PHP code (removed in PHP 7+, but still found in injections on older sites)

All four patterns pull code from $_POST, $_GET, or $_REQUEST and execute it — I’m not listing the exact copy-paste forms on purpose.

None of these constructs should exist in normal WordPress code. Search the files with:

grep -rE "eval\s*\(\s*base64_decode|@assert|create_function|preg_replace.*/e" wp-content/ wp-includes/ *.php

For JavaScript injections, look for long \x... or \u... strings, eval wrapped around obfuscated code, or document.write that loads hidden iframes.

Scanners — how to check your site for malware

Manual search gives you a sense of where to look, but it doesn’t cover everything. Scanners can check thousands of files against known malware signatures in minutes. I usually run several different ones — each has its own strengths.

AI-BOLIT — server scanner

Free command-line scanner from Revisium. It works with signatures and heuristics, catches obfuscated code, shells, and injections. The main advantage is high accuracy on common attack patterns and regular database updates. Run it via SSH:

cd ~/public_html
wget https://revisium.com/kb/aibolit.tar.gz
tar -xzf aibolit.tar.gz
cd ai-bolit
php ai-bolit.php --path=../public_html

The output is an HTML report listing suspicious files grouped by category: critical, needs review, and informational. I go through the list manually and delete the confirmed threats.

ImunifyAV — built into many hosts

Server antivirus from CloudLinux. It’s often included right in the hosting control panel — you can start a scan with one click. It catches shells and SEO spam well. The downside is occasional false positives on legitimate plugins (especially nulled builds).

Wordfence — scanner from the WordPress dashboard

The most popular security plugin for WordPress. Wordfence scans files for changes against the official repository, looks for suspicious code, and checks for updates. The free version is enough for most tasks. Install it, run Wordfence Scan, and review the report.

The downside is that it runs from inside the hacked site, so a clever backdoor can disable it or fake a “clean” result. For reliability, combine it with a server-side scanner.

VirusTotal and Google Safe Browsing — external domain check

External services look at the site the way a browser does. On virustotal.com you enter the URL and the system runs it through 70+ antivirus engines. Google Safe Browsing checks the domain against its database. If the domain is blacklisted, you’ll see it right away. This is useful before starting cleanup to understand the scale of the problem.

Sucuri SiteCheck — free quick scan

The service at sitecheck.sucuri.net provides a fast external check for signs of infection. It analyzes the source code, scripts, and blacklist status. It’s free and requires no registration. It’s great for initial diagnosis and for showing a client: “here’s a public scan that shows the issue.”

The scanner found dozens of infected files and you’re not sure which ones to delete?

I clean hacked sites for $249 flat: cleaned within 24 hours, review requests submitted as part of the cleanup, 60-day guarantee. Free 10-minute check.

Order cleanup

Removing the virus — step-by-step plan

Once you know where the infection is sitting, cleaning begins. I break it into six sequential operations — each with a result check. You can’t skip steps: miss one backdoor and the site will be infected again in a week.

Replacing the WordPress core with a clean copy

The most reliable way to clean an infected core is to replace it entirely. Download the latest version of WordPress from wordpress.org, unpack it on your local computer. Delete every folder and file from the server except:

  • wp-content/uploads/ — media files (already checked)
  • wp-content/themes/ — current theme (also under cleaning)
  • wp-content/plugins/ — current plugins (under cleaning)
  • wp-config.php — database credentials config
  • .htaccess — server rules (under cleaning)

Upload the fresh core files in place of the deleted ones. This guarantees removal of any injects in the WordPress core files.

Reinstalling plugins from the official repository

Plugins are the most common source of infection. So I export the list of installed plugins, delete the entire plugins folder, and reinstall each one from the WordPress repository. If a plugin is paid, download the latest version from the developer’s site, not from an old archive.

At this stage it’s a good idea to remove every unused plugin. Every plugin is a potential hole. If you last opened a plugin a year ago, you probably don’t need it anymore — delete it.

Cleaning the theme or switching to a default one

The theme is the second most popular place for backdoors. If you’re using an official theme from the repository, reinstall the latest version. If your theme is custom or paid, download a clean copy from the git repository or from the developer.

If you suspect the theme may have been modified, temporarily switch to the default twentytwentyfour theme until you finish. Restore your own theme after the cleanup.

Checking wp-config.php and .htaccess for injects

Open wp-config.php in an editor and compare it with wp-config-sample.php. It should contain only constant definitions (DB_*, AUTH_KEY, etc.) and standard require statements. Remove any extra include, base64 strings, or calls to create_function or eval.

In the root .htaccess there should be only the standard WordPress rules (# BEGIN WordPress / # END WordPress). Remove any extra RewriteRule, especially redirects to third-party domains or conditions based on User-Agent (used for cloaking).

Scanning the database: wp_options, wp_users, wp_posts for spam

Viruses hide not only in files. Check the database as well:

-- Suspicious option values (should be normal URLs and settings)
SELECT option_name, option_value FROM wp_options
WHERE option_value LIKE '%base64%' OR option_value LIKE '%eval%' OR option_value LIKE '%<script%';

-- Hidden admins
SELECT u.ID, u.user_login, u.user_email, u.user_registered
FROM wp_users u
JOIN wp_usermeta m ON m.user_id = u.ID
WHERE m.meta_key = 'wp_capabilities' AND m.meta_value LIKE '%administrator%';

-- Spam in posts
SELECT ID, post_title FROM wp_posts
WHERE post_content LIKE '%<iframe%' OR post_content LIKE '%base64%';

Review every suspicious result manually. Delete hidden admins with unfamiliar logins.

Removing admins you didn’t create

In Users → All Users sort by registration date. Delete any administrator you don’t remember creating. When deleting, choose “Attribute all content to another user,” otherwise the user’s posts will be deleted along with the account.

Also reset all Application Passwords (if any were used) and check the list of active sessions — the attacker may have left a long-lived session.

Restoring from backup — when it’s the right move

Rolling back to a backup is tempting, but it doesn’t always work. How to set up backups in advance so you have something to restore from is covered in the article website backup. Below are three typical situations and what to do in each.

When a backup will help and when it’s already infected

A backup “saves” the site only if it was made before the infection occurred. The problem is that infection often happens 1–2 weeks before visible symptoms: the attacker plants a backdoor, waits, then activates it. During those two weeks all your automatic backups will have copied the infected version.

So check backups older than a month. An archive from 2–3 months ago is almost certainly clean, but you’ll lose recent content. Solution: restore the clean backup to a separate copy, run it through a scanner, and if it’s clean, migrate the current content (posts, orders, settings) on top of it.

How to check a backup for cleanliness

Never restore a backup directly to the live site. Unpack it locally or in a test environment and run AI-BOLIT and Wordfence on the files. Compare wp_options, wp_users, and root files against known-good versions. Only after confirming the backup is clean should you upload it to the live server.

What to do if you have no backup at all

It happens more often than you’d like. If there are no backups, clean what you have: targeted file and database cleaning, replacing the core and plugins with fresh copies, restoring .htaccess and wp-config from clean originals. In most cases I’ve handled, this works — data is preserved and nothing is lost.

If content is partially lost (for example, a backdoor overwrote posts), you can partially recover it via Wayback Machine (web.archive.org) — it keeps page snapshots for years. Pull the missing content one piece at a time. It takes time, but it works.

Removing Google warnings

If your site is already on the Safe Browsing blacklist, simply cleaning it isn’t enough. You need to notify the search engines that the infection has been removed and request a review. Without this, the red banner saying “This site may harm your computer” can stay for several more weeks.

Requesting a review in Google Search Console

Go to search.google.com/search-console, select your site, and find the Security and Manual Actions → Security issues section. If there’s a mark about the infection, there will be a “Request review” button. Click it, describe in free form what was found and how it was cleaned, and submit the request.

In the description, be specific: which files were infected, which scanners you used, what you did to prevent repeats (WAF, 2FA, updates). The more detailed, the faster the bot will decide.

How long it takes

When I clean a site, review requests are submitted as part of the cleanup; Google usually reviews within a few days. If the warning is still there after a week, submit again: the review may have found leftover traces (one missed backdoor) and could not confirm the cleanup.

What to do if your hosting provider has already blocked the site

Hosting providers most often block for spam sent from your IP. Open a ticket: “site cleaned, attaching scanner report, please unblock.” Most providers unblock within an hour after you confirm the cleanup. If your host won’t respond or takes too long, migrate the site to another host temporarily or permanently.

How you were hacked — common attack vectors

Once you understand exactly how they got in, you can close that specific hole. Otherwise they’ll return the same way in a week. I broke down the five most common WordPress compromise vectors.

Vulnerable plugin — how to find the CVE

The most common scenario. You have plugin version 2.3 with a known SQL injection or RCE (CVE-2024-XXXXX). The developer released 2.4 with the fix, but you never updated. The attacker uses Shodan or Wappalyzer to find vulnerable sites and exploits them.

To find which plugin was used: check file modification dates on the server (find . -mtime -30 -type f — files changed in the last month). Check wpvulndb.com or wordfence.com/threat-intel/ against the versions of your installed plugins to see which ones have open CVEs.

Brute force on wp-login.php and xmlrpc.php

If your admin password is weak (Admin123, qwerty, spouse’s name), an attacker can guess it through brute force. Attacks target /wp-login.php (standard login form) and /xmlrpc.php (XML-RPC API, which most sites don’t need but is enabled by default).

Log signs: thousands of POST /wp-login.php or POST /xmlrpc.php requests from different IPs. Protection: disable xmlrpc.php completely (via plugin or nginx rule), protect wp-login with 2FA and login attempt limits.

Nulled themes and plugins with built-in backdoors

Downloaded a paid plugin “for free” from a torrent or warez site? There’s a good chance it contains a built-in backdoor: nulled plugins are one of the most common entry points I find in hacked sites. The attacker maintains a list of sites using that nulled plugin and can activate it at any time. Sometimes these backdoors in nulled builds stay undetected for years.

The only solution: remove all nulled plugins and themes and replace them with licensed or free alternatives. Saving the cost of a license isn’t worth the risk of losing the entire site.

Weak FTP/SSH passwords

If your FTP password is something like 123qweASD, that’s not a password — it’s an invitation. FTP brute-force attacks run 24/7 from tens of thousands of bots. The same applies to old SSH passwords.

Protection: use passwords at least 16 characters long, generated by a manager (Bitwarden, 1Password, KeePass). For SSH, switch to keys and disable password authentication. For FTP, switch to SFTP and disable plain FTP.

Outdated WordPress or PHP

WordPress 5.x on a server running PHP 7.0 is a cocktail of vulnerabilities. Both the core and the language receive regular security fixes that only apply when you update. An old version means dozens of publicly known attack methods.

Regularly update the core, plugins, themes, and PHP. WP 6.x on PHP 8.2+ is the current secure standard.

Protecting WordPress After Cleanup — 8 Steps

After cleaning the site, you need to close every entry point the attackers used. Without these steps, a cleaned site often gets hacked again within a few months. I apply at least 8 layers of protection.

Wordfence or Solid Security (formerly iThemes Security)

The basic security plugin for WordPress. It includes an application-level firewall (blocks known attack patterns), a file-change scanner, login attempt limits, and monitoring for suspicious activity. In most cases the free version is enough.

I prefer Wordfence for technical admins because it has more fine-grained settings. Solid Security is simpler for business owners and has a clearer interface.

Two-Factor Authentication (2FA)

The most effective protection against admin-account compromise. Even if the password is stolen, attackers cannot log in without the second factor (a TOTP code from Google Authenticator or Authy). Enable it with plugins such as WP 2FA, Two-Factor (from the WordPress core team), or Wordfence Login Security.

Turn on 2FA for every role that can publish content (editor, author, administrator). Leave subscriber accounts alone — they pose no risk.

Hide or Move wp-login.php

The standard URLs /wp-login.php and /wp-admin/ are the first places an attacker tries. Moving them to a non-standard URL (for example /secret-login/) with the WPS Hide Login plugin stops most automated attacks. It is not a complete solution, but it reduces log noise by an order of magnitude.

Disable xmlrpc.php

The XML-RPC API is needed only for integrations with old WordPress clients (mobile apps, Jetpack). Most sites do not need it, yet it is enabled by default. Disable it in .htaccess:

<Files xmlrpc.php>
    Order Allow,Deny
    Deny from all
</Files>

Or with an add_filter in the theme’s functions.php file. After disabling it, thousands of brute-force attempts disappear from the logs.

WAF — Cloudflare / Sucuri / ModSecurity

A Web Application Firewall sits in front of the site and filters traffic before it reaches WordPress. Cloudflare offers a basic WAF for free, Sucuri provides a paid plan with more rules, and ModSecurity runs on the server (available from most reputable hosts). It blocks SQL injection, XSS, and RCE using OWASP rules.

File Permissions: 644 for Files, 755 for Folders

If your files are set to 777, any user on the server can write to them. This is a common mistake after sloppy FTP uploads. Restore the standard permissions:

find . -type d -exec chmod 755 {} \;
find . -type f -exec chmod 644 {} \;
chmod 600 wp-config.php

The config file that holds passwords should be 600 (readable only by the owner). This stops attacks that rely on writable files.

fail2ban Against Brute Force

On a VPS, install fail2ban with a rule for wp-login: after 5 failed attempts in one minute, ban the IP for an hour. Brute-force attacks become useless. On shared hosting the same protection is provided by plugins such as Limit Login Attempts Reloaded or the built-in Wordfence feature.

Automatic Backups to Separate Storage

Backups must not live on the same server as the site. If the server is compromised, the backups are too. Use cloud storage: AWS S3, Google Drive, Dropbox. The plugins UpdraftPlus and Solid Security can send backups to these services.

After the security setup the site may run slower because caches were cleared — speed optimization will restore performance.

Site cleaned — what next?

Without ongoing maintenance, a cleaned site can get hacked again within a few months. I offer monthly care plans starting at $99/month that include automatic backups, updates, security monitoring, and fast response to incidents.

Get monthly care

When You Should Call a Specialist

Not every hack can be fixed on your own. Here are situations where it is better to contact a professional right away — trying to handle them yourself usually makes things worse.

The WordPress core, wp-config, or .htaccess is infected

When malware is injected into system files, simply reinstalling WordPress is not enough. You need to understand what each line of malicious code does, which files it touches, and whether cron jobs were added. Without experience it is easy to miss a hidden backdoor.

Multiple sites on the same hosting account are all infected

Cross-site contamination happens when an attacker uses one hole to infect every site in the account. Cleaning sites one by one does not work — after you clean one, the others re-infect it. You need to clean all sites at the same time and isolate the accounts on the server.

Symptoms return within a day after cleanup

If the infection comes back after your cleanup, a backdoor you missed is still active. This is the hardest case: something is still alive and re-activates the malware. Without thorough diagnostics (log analysis, file-change monitoring, cron-job search) you will not solve it.

The site is commercial and every hour of downtime costs money

An online store during peak season or a subscription service cannot afford three days of experiments. Time is critical: 4–8 hours of professional cleanup is cheaper than three days of trial-and-error and lost revenue.

How much does WordPress cleanup cost and how long does it take

Market prices vary widely, and a cheap quote often means a surface cleanup that leaves backdoors behind. Here is how I price and schedule the work.

Price: $249 flat

A full cleanup is $249 flat, no hidden charges: diagnostics, removing the malicious code from files and the database, closing the hole it came through, and review requests to Google and your host.

Very large sites (10k+ files, multisite, several sites on one account) can take more work — I’ll tell you up front if it’s more, before you pay.

No markup for urgency or off-hours work: an infection in the middle of a sale costs the same, and I reply within 2 hours, 24/7.

Timeframe: cleaned within 24 hours

If someone promises to “fix it in an hour,” it is either a superficial cleanup that leaves backdoors or simply not true. Real cleanup starts with diagnostics and continues with careful cleaning and checks — it can’t be squeezed into an hour. Your site is cleaned within 24 hours.

Guarantee: 60 days of free re-cleanup

If the same infection returns within 60 days after cleanup, I clean it again at no charge. Any competent specialist should give you a guarantee like this; without one, it is better not to hire them.

Complete WordPress virus cleanup
  • $249 flat fee for full cleanup, no hidden charges
  • Cleaned within 24 hours
  • 60-day guarantee — if the same infection returns, I clean it again for free
  • Free 10-minute check if you are not sure the site is hacked

Order cleanup

Or message me on Telegram @demento174 or WhatsApp +995 555 18 41 06 — I reply within 2 hours, 24/7.

Conclusion and frequently asked questions

A WordPress hack is not a catastrophe but a solvable technical problem. The main thing is not to panic in the first hours, not to make sudden moves from an infected session, and to follow the checklist step by step. Most sites are fully restored without data loss or SEO damage.

How long does it take to clean a hacked WordPress site?

Diagnostics take 2–4 hours, and the site is cleaned within 24 hours. Do not believe promises to “fix it in an hour” — that is either a superficial cleanup that leaves backdoors or simply not true.

Can the site be cleaned without losing data?

In most cases I’ve handled, yes. Cleanup is not “delete and reinstall” but targeted removal of malicious code. Content, products, orders, users, and settings are preserved. Occasionally the most recent posts are lost if a backdoor touched wp_posts, but even then they can usually be recovered via Wayback Machine.

What if there is no backup?

We work with what exists: scanners (AI-BOLIT, ImunifyAV) locate infected files, we remove them manually, and we reinstall the WordPress core and plugins from official sources. If content is partially lost, it can often be recovered via web.archive.org. After cleanup, set up automatic backups to cloud storage.

How do I get Google to remove the “This site may harm your computer” warning?

After cleaning the site, submit a review request through Google Search Console in the Security & Manual Actions section using the “Request a review” button. Google rechecks the pages and removes the label. Google usually reviews within a few days. When I clean a site, review requests are submitted as part of the cleanup. If the warning stays longer, traces remain and further cleanup is needed.

Can WordPress be protected from hacks 100%?

No one can give a 100% guarantee. But you can cut the risk sharply: regular updates, 2FA for admins, a WAF (Wordfence or Cloudflare), disabling xmlrpc.php, strong passwords, and automatic cloud backups. Most hacks happen because of outdated plugins and weak passwords — these issues can be fixed in one day with proper configuration.