WordPress Hacked? What to Do in the First Hour (and What Not To)
If your WordPress website has been hacked, preserve a backup of the current state, avoid making sweeping changes, change credentials only when it is safe to do so, and get the site assessed before cleaning it. A careful response protects evidence, customers and your ability to recover fully.
Stay calm and avoid rushing
A hack feels urgent, and acting fast is sensible, but acting carelessly can destroy evidence, break a working recovery path or spread the problem. The aim of the first hour is to stabilise and understand, not to clean.
A practical first-hour plan
| Step | Action | Why |
|---|---|---|
| 1 | Record what you see with screenshots and notes | Evidence helps find the entry point |
| 2 | Take a backup of the current state | Preserves evidence and a fallback |
| 3 | Tell your host if their systems are affected | They may be able to isolate the problem |
| 4 | Review Users for unknown administrators | Shows whether access was created |
| 5 | Change credentials from a clean device | Cuts off stolen access |
| 6 | Pause advertising to infected pages | Avoids sending customers to danger |
| 7 | Arrange a proper assessment | Cleaning without understanding invites reinfection |
Not sure what is going on with your website?
Tell us what you are seeing and we will outline the next step before any chargeable work.
What not to do
- Do not delete everything and restore an old backup without checking it is clean
- Do not leave the site live to customers if it is actively harmful
- Do not email passwords to anyone
- Do not ignore customer data: you may have obligations if personal information was exposed
- Do not assume one file removed means the problem is gone
Customers and obligations
If the website collects personal information, such as enquiries or orders, a compromise may have privacy implications. Organisations covered by Australian privacy law can have notification duties after certain breaches. Consider seeking advice if customer data may have been exposed.
Recover, verify, strengthen
A professional response preserves evidence, assesses files, users and plugins, removes the malicious code with your authorisation, closes the entry point, rotates credentials and rescans. See our hacked website help or contact urgent support.
Communicating with customers
If the compromise affects visitors or customer data, tell people clearly and calmly what happened, what you are doing and what they should do. Avoid speculation. Honest, prompt communication tends to preserve more trust than silence. If personal information may have been exposed, consider getting advice about any notification duties that may apply under Australian privacy law.
Why you should keep evidence
The state of the site right after a compromise shows how it happened: which files changed, which accounts were added and when. Cleaning immediately can erase those clues and make it harder to close the entry point. A backup of the infected state, kept safely and never restored to the live site, preserves them.
Rebuilding trust and security
- Update everything and remove software you do not need
- Reset all relevant passwords and keys
- Review users, permissions and hosting access
- Add scanning, monitoring and tested offsite backups
- Document what happened and the changes made
The first 24 hours after the first hour
Once the immediate steps are done, use the next day to plan the recovery properly. Decide whether the site should stay offline, gather hosting and domain access securely, identify what clean backups exist, list the people and systems that use the site’s credentials and note which customers or data could be affected. A written plan prevents rushed decisions and gives whoever is doing the recovery clear authority and boundaries.
Questions to ask your recovery provider
- How will you preserve evidence before cleaning?
- How will you decide whether a backup is clean?
- What will you do to close the entry point?
- What will you retest before the site goes back live?
- What ongoing protection do you recommend and why?
Learning from the incident
Once the site is safe, spend time on what the incident teaches. How did the attacker get in: an outdated plugin, a weak password, a compromised account? What detected it and how late? Which backups were useful? What would have shortened the recovery? Write the answers down and change something concrete as a result, such as a monitoring alert, a stricter access policy or an update routine. An incident that leads to better habits is far less costly in the long run. It also gives you something solid to tell customers who ask what you have done to protect them.
Preventing a repeat
Updates, strong unique passwords, fewer plugins, scanning, monitoring and tested offsite backups reduce the chance. A maintenance plan bundles those so they happen every month.
Want this looked after for you?
WP Mate maintenance plans cover managed updates, daily offsite backups, security scanning and 24/7 uptime monitoring.
Think your website is hacked? Get a safe recovery plan.
Services related to this guide
Hacked website help
Assess the damage and plan a safe recovery.Get Security Help →
Urgent WordPress support
Website down or checkout failing? Tell us what happened.Request Urgent Help →
Talk to WP Mate
Not sure which service fits? Ask us and we will point you the right way.Contact us →
Frequently asked questions
Should I take my website offline?
If it is actively harming visitors, temporarily taking it offline or into maintenance mode is reasonable while it is assessed.
Is restoring a backup the fix?
Only if the backup is clean and the way in has been closed. Otherwise the site can be reinfected.
How long does recovery take?
It depends on how far the compromise spread and what clean backups exist.
Ready to get your website sorted?
Based in Warrnambool, Victoria, helping Australian businesses online. Tell us what is happening.
Tell your mate what's going wrong.
Send us a few details and we’ll work out the next step. Please don’t include passwords or payment details.
- Australian support in plain English
- Clear scope and next steps before chargeable work
- Backup and recovery plan before live changes
