A malware scan tells you whether the page has patterns that look like an infection. It does not tell you the site is clean, and it cannot replace a server-side audit. The distinction matters, because a clean scan is treated as a certificate when it is only a smoke alarm.
This site has a reason to be careful. One of its subdomains served Chinese casino spam in 2024. A file called ak.php was planted in the docroot on 8 August 2024, the subdomain returned 403 at the root and 500 everywhere else, nothing linked to it, and nobody noticed for years. That is the failure mode: not a dramatic hack, a forgotten folder.
What the scan looks for
The site scan for malware fetches a public page and looks for the patterns that appear in injected content: hidden iframes, base64 payloads in scripts, casino and pharmacy spam text, mixed content, unknown script hosts. It is a pattern scan, not Google Safe Browsing and not a scan of your files.
That means it can catch a hacked page that is serving spam to visitors. It cannot catch a backdoor in a plugin, a database injection, a cron job, or a compromised hosting account. Those live below the page.
What to do with a hit
- Do not panic and do not delete the page. Keep a copy of the output for evidence.
- Check the source. View the HTML of the live page and search for the flagged pattern. If it is not in the source the site sends, it may be injected by JavaScript or by a proxy.
- Check the file timestamps. Recent modifications to theme files, plugin files or
.htaccessare the first place to look. - Search for suspicious files. PHP files in upload folders, files with
eval(,base64_decode(, or$_POSTnear the top are the usual suspects. - Change credentials. Hosting, database, FTP, admin panel. All of them.
- Tell the host. A shared host has tools you do not. Ask them to scan the account and check the access logs.
The forgotten-folder problem
Most infections on small sites are not in the main site. They are in a test folder, an old subdomain, a backup directory, a plugin nobody uses, or a file left behind by a developer. The main site looks fine because the spam is on a URL nobody visits.
Audit your docroot at least once a year. List every folder, every subdomain and every file over a few hundred kilobytes that you cannot identify. Delete what you do not need. A forgotten subdomain is a free home for a spam page, and it inherits your domain's reputation.
Prevention that actually works
- Update the CMS, themes and plugins. The old plugin is the common door.
- Delete plugins and themes you do not use. Inactive code is still code.
- Use strong unique passwords and two-factor authentication on the host and the admin panel.
- Back up off the server, and test a restore once a year.
- Remove old subdomains and test folders. Point them at the main site or remove the DNS record.
None of this is glamorous. It is the same advice as ten years ago because the attack has not changed. The scan is the alarm, the hosting account is the building, and the forgotten folder is the back door.
What the free scan can and cannot do
Use it as a first check, especially if you have just taken over a site, changed hosts, or seen a traffic drop with no obvious cause. If it is clean, that is one item off the list, not a guarantee. If it is not clean, treat the domain as compromised until a human has looked at the files.
The incident checklist
If the scan returns a hit, keep this order. Deleting fast feels decisive and usually destroys the evidence.
- Capture. Save the scan output, the page source and a screenshot with the date.
- Scope. Is the pattern in the HTML the server sends, or only in the rendered browser? That difference tells you whether the injection is in the page, a script or a proxy.
- Files. Look for recently modified theme, plugin and
.htaccessfiles. Search for PHP in upload folders. - Accounts. Change hosting, database, FTP and admin passwords. Enable two-factor if it is available.
- Host. Ask the host to scan the account and check the access logs. They can see things you cannot.
- Clean and verify. Remove the files only after you understand how they got there, then rescan and monitor for a week.
If the site is on a shared plan, a compromise can affect neighbours, and the host is an ally rather than a bystander. Tell them early. The worst outcome is not the spam page. It is a blocked domain that takes weeks to clear because nobody reported the infection when it was small.
After a clean-up, watch the same URLs for two weeks. Reinfection is common and it means the entry point was not found. A second hit on the same page is a signal to hire someone rather than repeat the same deletion.
Pair the scan with the spider crawl to see what a bot gets, and the website auditor to check for injected scripts and unexpected redirects on the page. The tools hub has all the checkers. If a site needs a full clean-up, the service page explains the scope, including the subdomain sweep that found the file on this domain.