Skip to content

Scan website for malware: five steps before you clean

A hacked WordPress site hides evidence in files and in the database. Check both before you delete anything.

BotBlocker reads what the server stores, marks every finding by severity and confidence, and leaves the decision to you.

Scan website for malware with BotBlocker

What a WordPress malware scanner plugin checks

Files, database and a comparison with known-good copies. Detection first, deletion later.

Files

Core, plugins, themes, uploads and custom paths. The scanner looks for eval() chains, base64 obfuscation, injected scripts and webshell markers, with more than 25 patterns.

Database

Posts, options, users and cron events. A script stored in an option survives every file cleanup, which is why the scan reads the database too.

Known-good comparison

Changed, added and missing files are three different answers. The comparison shows what the attacker touched, not only that something is wrong.

Why a free URL scanner cannot see it

A remote scanner fetches a page and reads the HTML. A backdoor does not have to appear there. It can sit in a PHP file that renders nothing, wait for a user agent, or wake up on a cron event at night.

A conditional payload is the usual trick: the page looks clean to you, to Google and to a scanner, and the redirect fires only for visitors from a search engine. Nothing in the response points to the file that produced it, so only a file scan finds it.

Что делать после скана, пошагово описано на странице про удаление вредоносного кода.

Scan WordPress site for malware

How to scan website for malware without losing the evidence

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

    The path, the pattern and the timestamp are what you compare later.

  3. Scan the database

    A script in an option or a post survives every file cleanup.

  4. Compare with known-good copies

    Core, plugins and themes. Changed, added and missing files are three different answers.

  5. Choose between a clean and a rebuild

    A clean is cheap and risky, a rebuild is safe and slow. A shop loses the orders written since the backup, a brochure site loses nothing.

Steps to scan a WordPress site for malware

What the scan does not do

It does not remove code

Detection is evidence, removal is a separate decision with its own risk. A clean report does not prove the site is clean afterwards.

It runs inside WordPress

If you cannot reach the admin area at all, the plugin cannot help until access is restored through recovery links or the host.

Questions we hear

What site owners ask before the first scan.

Is a free scan enough?
A remote check can tell you that a page redirects. It cannot tell you which file does it. The local scanner is part of BotBlocker PRO, because scanning files and the database on a schedule costs server time.
Can I scan a site I cannot log into?
Not with a plugin. The scanner needs WordPress to run. Restore admin access first, then scan, then rotate every password that was stored on the site.
Does scanning slow down the site?
No. Scans run in the background on a schedule, not on page load. A visitor request never waits for a scan.
Does it check uploads and custom folders?
Yes. Uploads are the first place to look, because a file there does not need an exploit to run. Custom paths outside the standard tree are added manually.
We were cleaned last month 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. A file scan alone would not answer that, the database scan and the file comparison do.

Scan first, delete later

Install BotBlocker, open the scanner and run one scan. Read findings by severity first, then by confidence.

WordPress site back online after a malware scan