Use Malware Scan to look for the module’s selected suspicious-code patterns in included local files. A match needs review; a scan with no matches is not proof that the installation contains no malicious code.

Run the scan deliberately

1. Confirm PD Guard Pro is active.
2. Open PD Modules → Guard → Malware Scan.
3. Read Not scanned yet, or check the time of the saved result.
4. Choose Scan now when you intend to read the included local files.
5. Wait for completion and check the new scan time, processed count and any Result capped warning.

Opening Malware Scan displays the stored result. It does not start a scan by itself. Scanning is synchronous and can take time on a large installation; avoid submitting repeated scans while the first outcome is uncertain.

Understand the result

The scanner uses signatures and heuristics. No threats found means that the included, readable content did not produce retained matching findings. Exclusions, file size, read failures, file-count limits and finding limits all affect what that means.

The scan does not quarantine, delete, repair or restore files. It does not automatically create a trusted integrity baseline, and this manual action is not a scheduled email-alert test.

Verify a completed attempt

Confirm that the stored scan time changed and read the relevant finding or cap details. A request error after a long scan does not establish which result was saved. Check the existing screen before starting another attempt.

Retain the original time, count and redacted message for an unresolved scan failure. Keep private source code and unredacted server-file listings out of routine diagnostics.

See the PD Guard Blesta guide for related tasks, or explore PD Guard.