A Wordfence malware scan is not only a search for suspicious code in a small group of WordPress files. Depending on the selected scan type and enabled options, it can examine files, content, database-stored options, configuration exposure, file changes, vulnerabilities and other security indicators. That broader scope matters when you are deciding whether a result requires investigation, repair or escalation.
This guide presents a practical workflow for WordPress website owners, freelancers, agencies and developers. First, understand what the scan can check. Then select a scan type that matches the site’s condition, review the available boundaries and options, inspect each result in context, and preserve a backup before making changes. The aim is not to treat every alert as confirmed malware, but to make decisions based on evidence.
What a Wordfence Scan Actually Checks
Wordfence can inspect WordPress files for malicious code, backdoors, shells, known malicious URLs and known infection patterns. It can also identify changes in eligible core, plugin and theme files by comparing them with repository versions when the relevant comparison is available. These checks make WordPress malware scanning broader than a single malware-signature test.
The result may also relate to content, configuration or the wider hosting environment. Therefore, a finding should be read as an indicator that needs interpretation. The documentation does not establish that every individual alert is definitively malicious without site-specific investigation.
Files, content and configuration checks
Depending on enabled options and license state, a scan can include several areas:
- Files: malicious or suspicious code, backdoors, shells, known infection patterns and malicious URLs.
- Content: posts, pages and comments that contain suspicious content or dangerous URLs.
- Options: database-stored options that may contain suspicious content or URLs.
- Exposure: publicly accessible sensitive configuration, backup or log files where the relevant checks are enabled.
- Other indicators: vulnerability, reputation, server and user-related checks available through the configured scan.
This scope explains why a clean-looking file does not necessarily describe the whole result. It also explains why an unfamiliar alert should not be handled by copying sensitive file contents, credentials, database settings or malicious URLs into a support request or public example.
Choosing Between Standard, Limited, High Sensitivity and Custom Scan
Wordfence documents Standard Scan as the recommended choice for most sites. It is the practical baseline when the website is stable, scans complete normally and there is no specific reason to suspect compromise. High Sensitivity is not automatically a better everyday setting: it takes more time and resources and may produce more false positives.
Limited Scan addresses a different problem. It is intended for hosting environments with highly restricted resources, including situations in which the site is running out of memory or normal scans do not complete. The available information does not establish a universal memory, CPU or duration threshold, so the decision should be based on observed scan and hosting problems rather than an invented number.
A practical scan-type decision
- Start with Standard Scan when the site is stable and there is no credible compromise signal.
- Consider Limited Scan when normal scans fail to complete or create resource problems.
- Consider High Sensitivity when the site is known or strongly suspected to be compromised and deeper inspection is justified.
- Use Custom Scan when the administrator manually changes which checks are included.
High Sensitivity scans images, PDFs and other files as if they were executable. That can reveal findings that a routine configuration does not treat in the same way, but it also increases resource use and the possibility of false positives. A High Sensitivity result therefore requires closer review, not automatic proof that the site is infected.
A Practical Wordfence Scan Configuration Workflow
Begin by matching the selected scan type to two facts: the site’s hosting constraints and the strength of any compromise indicators. Next, review which general, performance and content-related options are enabled. Do not assume that every available check is active in every installation. Interface labels and available options may vary with the installed version, license state, hosting configuration and enabled settings.
Repository comparison is a useful configuration detail for eligible WordPress.org core, plugin and theme files. It can help identify differences from an expected repository version, but it is not an authoritative comparison for every product. Review the scan boundaries before starting, especially if the hosting account contains more than one WordPress installation.
Repository comparisons and scan boundaries
Wordfence can compare eligible WordPress core, plugin and theme files with repository versions. This does not apply to commercial themes or themes outside the official WordPress.org repository. Commercial plugins and other products distributed outside that repository likewise may not have an authoritative clean copy available for this comparison. They can still be scanned for malware, malicious URLs and backdoors, but a repository-difference result should not be expected for every product.
Additional directories also require care. Do not automatically include directories that belong to separate WordPress installations with their own Wordfence scans. After starting the scan, record skipped paths, incomplete stages or troubleshooting conditions. An incomplete scan should not be interpreted as a clean result; it means that the coverage needs further review.
How to Read Wordfence Scan Results
Start with the affected path, result type and available details rather than acting on an alert label alone. A modified-file result is not automatically evidence of malware. Intentional customizations, developer changes, host-created files, plugin-generated files or code changes made by a plugin author without changing the release version can all produce differences.
When Wordfence provides the option, use View File to inspect the relevant source. Use View Differences when a comparison with an expected repository version is available. The purpose is to establish what changed and whether the change has a legitimate explanation before selecting Repair, Delete, Ignore or another result action.
Evidence before action
For each suspicious or modified file, work through a consistent review:
- Identify the file, its location, the result category and the scan option that produced the finding.
- Inspect the file with View File where that is appropriate and safe.
- Use View Differences when Wordfence can compare the file with an expected repository version.
- Check whether the change was intentional or came from the site owner, developer, host, plugin author or theme vendor.
- Document why the chosen action is remediation, an understood exception or an escalation.
Mark as Fixed has a narrower meaning than its label may suggest. It removes the result from the current view, but it does not permanently remediate the underlying issue. The result can reappear in a later scan. It should therefore not replace investigation or a real corrective change.
Handling Suspicious Files Without Breaking the Site
Before repairing or deleting an unfamiliar file, create a backup or preserve a copy of the affected file. This is particularly important when the file belongs to a custom or commercial product, because an automated action may remove legitimate changes or leave the site harder to restore.
Repair is appropriate only after the file and its expected source have been understood. For eligible WordPress.org core, plugin or theme files, Repair can replace the file with an original copy. That may remove legitimate customizations, so a modified-file warning must be investigated first. Repair should not be treated as a safe universal response to every difference.
Repair, delete, ignore or escalate
- Repair: use only when the file is eligible, the original source is appropriate and intentional customization has been considered.
- Delete: use only after confirming that the file is unnecessary or malicious. Do not delete every flagged file automatically.
- Ignore: use when the finding is understood to be a false positive or an intentional change, rather than when the alert is simply unexplained.
- Mark as Fixed: understand this as current-view result management, not permanent remediation.
- Escalate: choose a controlled cleanup and recovery process, hosting support or qualified security assistance when legitimacy or compromise scope cannot be verified safely.
High Sensitivity and additional-directory scans can produce false positives. Unknown files should be investigated in context, and commercial-product differences should be treated neither as automatically malicious nor as automatically trustworthy. When the site may be compromised, scanning alone is not a complete incident-response process.
False Positives, Commercial Products and Follow-Up Scans
Repository comparison has an important boundary: commercial themes, commercial plugins and products distributed outside WordPress.org may not have a repository version against which Wordfence can compare the file. A difference in such a product is therefore not, by itself, confirmation of malware. The same caution applies to intentional customizations and vendor or developer changes.
After a real change, a follow-up scan can help you check whether the finding remains. This is different from merely hiding a result. If the result was only marked as fixed, it may return later because the underlying file or condition was not changed. Record what was investigated, what action was taken and whether the result was intentionally ignored or escalated.
A concise review checklist
- Confirm which scan type and options were used.
- Check whether any stages, paths or directories were incomplete.
- Inspect the finding and compare it with an expected source where available.
- Ask whether the change was intentional or produced by a developer, host, plugin author or theme vendor.
- Preserve a backup or copy before repair or deletion.
- Record whether the result was remediated, intentionally ignored or escalated.
- Run a follow-up scan after an actual corrective change, without treating a hidden result as resolved.
The practical hierarchy is straightforward: Standard Scan is the documented baseline for most sites, Limited Scan addresses incomplete or resource-constrained scans, and High Sensitivity is reserved for credible compromise concerns because it uses more resources and can create more false positives. Review evidence and preserve a backup before repair, deletion or ignoring a result. Treat repository comparisons as limited, especially for commercial products, and remember that Mark as Fixed is not remediation. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.