The October 2026 PHP vulnerabilities ("PHP2Shell", CVE-2026-109618 and CVE-2026-109619) were disclosed on 21 October, and exploitation surged within days. If your site runs PHP (WordPress, WooCommerce, Laravel, most shared hosting), patching is step one and it is urgent. But a patch only stops future attacks. If someone got in during the window, your site may already be serving spam links, a webshell, or altered pages to your visitors, quietly.
Your live page diffed against its pre-Black-October archive snapshot, verdict in plain words, no sign-up.
The uncomfortable truth about this week: most tampering is discovered by a customer, a search engine warning, or never. Hawkline watches your public pages around the clock and, when the content changes, tells you what changed, in plain words: "three outbound links to a pharmacy domain appeared on the homepage." If your site changes and it wasn't you, you know in minutes.
5 pages watched free, no card, two minutes to set up. There is a one-tap "My own website" setup on the desk.
Watch my site, free5 watchers free · alerts in plain words · silence on cosmetic churn
Hawkline watches publicly visible content on a schedule. It catches defacement, spam injection and visible unauthorised edits. It does not scan files, read server logs, detect webshells that change nothing visible, or see pages behind logins. Use it as one tripwire among several, alongside patching and your host's malware scanning. Not affiliated with the PHP project.