During resource monitoring on a development server, we noticed an unexpected process running from a site’s files. That raised a broader question: what scans website files for malware? Virus Scanning only inspected mail, which is what it was designed to do, but the name suggested more.
A second, separate feature
We added an on-demand scan of a whole account’s files, using the same engine already used for mail. It follows the pattern of existing long-running actions: a run record, a queued job, and a status page that polls for live progress. Findings appear as a readable list rather than a raw log.
Two issues found while testing
A deprecated option produced a warning on every run, so it was removed. The run log also showed every line twice, because output was appended both by the live-progress callback and again at completion. The final log now comes from the result once.
Verifying
12 new tests, full suite 2691/2691, Pint clean, plus two live scans of real-sized accounts on the development server.
Tested (2691/2691).