The Malware Scanner analyses your Joomla file system for known malware patterns and suspicious code. The page is divided into an action bar, an active-configuration summary, scan metrics and a results table.

Three chips beneath the action bar summarise the settings currently in effect (configured under Global Configuration › Malware Scanner):
Click Start in the action bar to begin. The status badge on the left changes to In Progress (blue) while the scan is running. Do not navigate away from this page while a scan is active.
Once the scan finishes the badge returns to Idle and a View Log button appears. Click it to open the full scan log in a modal window; you can also download the log from that modal.
The Configure button (⚙) takes you directly to the Malware Scanner tab in Global Configuration.
The scanner must read every file in your Joomla installation individually. A standard installation contains several thousand files, so a full scan — especially with Timeline: Anytime — can take considerable time and place significant load on the server. Run scans during periods of low activity.
If your PHP memory_limit directive is set to 128 MB or less, a warning badge is displayed before your first scan. Low memory can cause a blank page or make your site temporarily inaccessible. See the Troubleshooting section if this occurs.
After the first scan completes, four summary cards are shown:
| Card | Description |
|---|---|
| Analyzed files | Total number of files inspected in the last scan |
| Suspicious files | Files that matched one or more malware patterns (shown in red when > 0) |
| High alert | Subset of suspicious files rated at the highest alert level (shown in red when > 0) |
| Time taken | Duration of the last completed scan |
Before the first scan, a prompt card is shown instead, inviting you to run your first analysis.
The results table lists every file that matched a malware pattern. Each row contains:
An Alert Level: High file requires manual review regardless of what the online check returns. If you are unsure whether a file is malicious, request a manual analysis.
Online verification requires a free OPSWAT API key (configured under Global Configuration › Malware Scanner). If no key is configured, an alert is shown and the online check buttons are hidden.
When a key is present, two counters are displayed:
Limits reset 24 hours after the first call on a given day. When a limit is reached, the corresponding button is disabled and an alert is shown.
Every time a new scan is launched, all Online Check statuses reset to Not checked, even for files previously submitted to OPSWAT. This reflects the dynamic nature of the service: engine signatures are updated daily, so a file that was reported as clean today may be flagged tomorrow.
Select this filter to view files previously added as exceptions. The Delete file(s) as exception button removes the selected entries, making them eligible to be flagged again in future scans.
This filter requires the Include exceptions in database option to be enabled under Global Configuration › File Manager. If it is disabled, a notice is shown instead of the list.
Select the Quarantined filter to manage files that have been moved to quarantine. Two buttons are available:
Files are flagged as suspicious, not confirmed malicious. False positives do occur. Be certain a file is genuinely harmful before deleting it — removing a legitimate file can break your site.
Three directories (and all files and subdirectories within them) are excluded from scanning by default: /tmp, /logs and /cache.
A collapsible About these results & OPSWAT disclaimer section at the bottom of the page explains the limitations of pattern-based detection, the role of the OPSWAT Metadefender Cloud service, and the recommended course of action when a file is rated as High alert.