Site Scan for Malware
Scan a page for injected scripts, hidden iframes, base64 payloads, casino spam, mixed content, and unknown script hosts. It is a pattern scan. It is not Google Safe Browsing and it cannot prove a site is clean.
What a page-level infection looks like
Most injected spam is boring. A line of base64 in the footer. An iframe with width and height set to 0. A script tag pointing at a domain nobody recognises. A block of Chinese gambling text hidden behind `display:none`. The page looks fine to a visitor and the spam is only in the HTML or the search results.
The pattern scan looks for those. It also lists every third-party script host, because "which of these did I add?" is the question that finds the problem fastest.
The subdomain that made this tool exist
In August 2024, one of this domain's subdomains was serving Chinese casino spam. The evidence is a local error log from 8 Aug 2024: a file called ak.php in that docroot, throwing a PHP deprecation warning. The Wayback capture three weeks later shows a page titled "PG电子(中国)官方网站" and a link to ky002.cc.
Nobody noticed because nothing linked to the subdomain. It returned 403 at the root and 500 everywhere else for years. That is the actual failure mode: not a dramatic hack, a forgotten folder. The fix is to sweep the account for files you did not put there, then delete or 410 the folder. I wrote the checklist into the deploy notes for this site.
What to do with a finding
- Save the HTML and a screenshot. You will want it for the host and for the report.
- Find the source. Is the script in the theme, a plugin, a widget, a database row, or a server file? Do not just delete it from the rendered page.
- Remove it at the source. Then rescan. If it comes back, the entry point is still open.
- Close the door. Change admin and hosting passwords, check admin users, check cron, check for PHP in uploads, and update everything.
- Check Search Console. Security issues and manual actions live there. A page scan cannot see them.
Questions
Is this a real malware scanner?
It is a pattern scanner. It looks for known injection strings, hidden iframes, obfuscated JavaScript, casino spam keywords, and mixed content in the HTML. It is not Google Safe Browsing, it does not inspect your server files, and it cannot prove a site is clean.
Can it find a backdoor in my hosting account?
No. A backdoor is a file on the server, not a string in the page. Finding it needs file access, a file-integrity check, and a look at the access logs. The pattern scan is the first 30 seconds, not the whole audit.
What was the casino spam on seolivly?
One of this domain's subdomains was serving Chinese casino spam in August 2024. A file called ak.php was planted in that docroot on 8 Aug 2024. The subdomain returned 403 at the root and 500 everywhere else for years, and nothing linked to it, so nobody noticed. That is the exact failure this check is for.
What should I do if it finds something?
Do not panic and do not delete the page. Save a copy, find where the script is inserted (theme, plugin, database, or server file), remove it from the source, then rescan. If the injection comes back, the entry point is still open. Change passwords and check cron and admin users.
Related tools
A page scan is a smoke alarm. The fix is a sweep.
The Fix Sprint starts with access and inventory: unknown PHP in uploads, unknown admin users, cron, old backups in the docroot, and the files nobody remembers. Then the report. $1,500 for one site up to 50 pages.
See the fix service Tell me what you found