Skip to content

Malware removal for WordPress in five steps

A hacked site fails before the first delete: no backup, no evidence, no idea which file started the redirect. Here is the order that holds.

BotBlocker dashboard after a malware scan on a WordPress site

What malware removal has to answer

Four questions decide the job: what changed, when, how it got in, and what proves it is gone.

Files

Core, plugins, themes, uploads and custom paths. A PHP file in uploads needs no exploit to run, so it is the first place to read.

The database

Posts, options, users and cron events store content that runs later. A script in an option survives any file cleanup.

Accounts

An admin user created by an attacker, an old FTP account, an application password nobody remembers. Each one restores access after a clean site.

Deleting the plugin comes last

The suspicious plugin is usually the visible part of a longer chain. Deleting it destroys the evidence that explains how the site was entered, and the entry point stays open.

BotBlocker reads what the server stores rather than what a page returns. The scanner looks for eval() chains, base64 obfuscation, injected scripts and webshell markers, and it keeps more than 25 detection patterns for that work. Every finding gets a severity from Critical to Info and a confidence from Review to Confirmed. A Critical finding with Confirmed confidence is a decision; an Info finding with Review confidence is a question for a human.

A remote page check cannot do this. A backdoor does not have to appear in the HTML: it can sit in a PHP file that prints nothing, wake up on a cron event at night, or fire only for visitors arriving from a search engine.

Как читать отчёт до удаления, разобрано на странице про сканирование сайта на вирусы.

Malware removal WordPress scan report with changed plugin files and severity levels

Malware removal WordPress: the order that works

Five steps, in this order.

  1. Back up and move the copy off the host

    An infected copy on the same server is not a backup.

  2. Scan the files and keep the report

    Path, pattern and timestamp are what you compare later.

  3. Scan the database

    A script in an option or a post survives the cleanest file tree.

  4. Compare against known-good copies

    Changed, added and missing files are three different answers.

  5. Rotate every stored password

    Hosting, database and admin users first. Then decide between a clean and a rebuild.

Five steps of WordPress malware cleanup from backup to password rotation

Where the cleanup stops

The scanner reports

Finding a file is evidence. Removing code stays a decision with an owner, and no plugin turns that into one button.

Scans run on a schedule

From once an hour to once every five days, in the background. A visitor request never waits for a scan. The scanner is part of PRO.

Access comes first

The scanner works inside WordPress. A site without admin access needs recovery before any scan can start.

Questions we hear

What site owners ask before the first delete.

Can I remove malware without a developer?
Yes, on a small site with a backup and a report you can read. The step people skip is the file comparison, and that is where a second infection starts.
Is a free scan enough?
A remote check tells you that a page redirects. It cannot tell you which file does it. Local scanning of files and the database is a paid feature here and in most plugins, because it costs server time.
We cleaned the site and the redirect is back. Why?
A payload survived in the database, in a file the cleanup skipped, or in an account that still has the old password. The database scan and the file comparison answer that question.
Does scanning slow the site down?
No. Scans run on a schedule in the background, not on page load.
What does the scanner cost?
It is included in PRO. Prices and what each plan covers are on the pricing page.

Take the backup before the first delete

Install BotBlocker, take a backup and run one scan. Read findings by severity first, then by confidence.

BotBlocker protection across files, database and admin accounts