Do not treat a visible symptom as the full incident

A new spam page, redirect or administrator account can be one sign of a wider problem. An attacker may still have access through a hosting account, stolen password, vulnerable plugin, scheduled task or modified file. Removing the visible page alone may not remove that access.

Keep a copy of relevant logs and files before making major changes. If the site handles customer or payment data, involve the hosting provider and the people responsible for privacy and incident decisions. Avoid making claims about data exposure until you have evidence.

Review every path that can change the site

Check WordPress administrators, hosting control panel users, domain accounts, Secure Shell (SSH) keys, file transfer accounts, database users and connected deployment tools. Remove access that is not needed. Reset credentials from a clean device and revoke old sessions or application passwords where available.

Review installed plugins, themes, must-use plugins, uploads and scheduled tasks. Compare core files with trusted release packages. Look for unexpected changes, but do not delete files before you preserve the evidence needed to understand what happened.

Restore from a known clean point

Use a backup from before the suspected compromise only after you have checked its date and contents. Update WordPress, plugins, themes and server software before public access resumes. Rotate secrets that may have been exposed, including database credentials and WordPress security keys.

After recovery, review logs and monitor for the same behaviour. Ask the host how it will protect the account and what evidence it can provide. A scoped WordPress security audit can help identify weaknesses that need repair before the site returns to normal use.