Introduction
When a critical vulnerability lands in something that runs on every one of your servers (nginx, PHP, OpenSSH, the kernel), patching is only half the job. You also need to know whether anyone got in before you patched. This guide is the process we use to check a Linux server running WordPress for signs of intrusion.
This guide is being written. The full step-by-step process is coming soon. It will cover:
- Preserving evidence before you change anything
- Checking users, SSH keys, sudoers and recent logins
- Looking for unexpected processes, listeners and outbound connections
- Reviewing cron jobs, systemd units and other persistence
- Finding recently changed files and web shells in WordPress sites
- Reading web server, auth and audit logs for the attack window
- Deciding when to clean up and when to rebuild
Updates
- October 31, 2026: Placeholder posted; full guide coming soon.
