Featured videos

An explainer that follows one example small business WordPress site through the life cycle of an infection: how attackers get in, how they hide, why the hack comes back after a quick cleanup, and what a real cleanup takes. Read the related page.

Eight emSign intermediate signing keys were trivially small, one reportedly the number 4, so Chrome, Firefox, Apple and Microsoft blocked them and Chrome drops the emSign root on Oct 27. Updated browsers are protected, but tools with their own trust lists, like Python pip and certifi, Node.js, Go and Docker images, need updates too. Read the related page.

When a serious bug lands, your servers wait on your vendor's fix. How to choose a server platform with patching in mind, and what to check before you launch. Read the related page.

The upstream PHP fix for CVE-2026-109618 and CVE-2026-109619 is out, but distro and vendor packages can lag behind. How to harden, test backups, and plan your patch window while you wait. Read the related page.

A short explainer on the October 2026 PHP emergency security updates: who is affected, why server updates and monitoring matter, and what to do this week. Read the related page.

The first-hour moves after a suspected WordPress hack: confirm symptoms, preserve evidence, and back up before you change anything. Read the related page.

A walkthrough of the owner triage checklist: confirm symptoms, contain without wiping, back up off-server, tighten passwords, and know what not to do on day one. Read the related page.

What Google's hacked-site warnings usually mean, what not to do, and how to get ready for cleanup and a later review request. Read the related page.

Scanners are useful, but they are not the same as incident response with a written report and hardening. This explainer covers the difference. Read the related page.

Once the malware is gone, lock the doors: passwords, least privilege, file-editor lock, login protection, updates, and tested backups. Read the related page.