If your website is showing strange code, redirecting visitors somewhere else, displaying a pop-up you didn't add, or you've found admin users you don't recognise, it has probably been hacked. Don't panic. In most cases you can get it back quickly from one of our daily backups, then lock it down so it doesn't happen again.
This guide is written for WordPress, but the same steps work for most other website software.
Common signs your site has been hacked
- The site shows code, spam links or a page you didn't create.
- Visitors are redirected to another website, often only on mobile or only when they arrive from Google.
- A "Verify you are human" or CAPTCHA box appears that asks visitors to press keys or paste something into their computer. This is a well-known malware trick, not a real security check.
- Plugins have been deactivated, or there are admin users you didn't create.
- Google shows a "This site may be hacked" warning, or we've told you about outgoing spam from your account.
Note: an email from WP Toolkit saying "Site vulnerabilities found" doesn't mean you've been hacked. It means something on the site needs updating. See WP Toolkit security alert emails: what do they mean?
Step 1: Work out roughly when it happened
Think about when the site was last working normally. If you're not sure, check when files were last changed in File Manager (sort public_html by "Last Modified"), or look at your website error logs. You'll need a backup from before that date.
Step 2: Restore a clean backup
We back up cPanel hosting accounts every day and keep the last 14 days. You can restore them yourself with JetBackup:
- Go to Services → My Services (https://www.hooplahosting.co.nz/client/clientarea.php?action=services), open your hosting service and click Log in to cPanel.
- Before you restore, download a copy of the hacked site (your
public_htmlfolder and database) in case you need anything from it later. - Open JetBackup and restore both the website files (File Backups) and the database (Database Backups) from the same date, before the hack.
- Check the site in a private browser window. If it still looks hacked, try an older backup.
Full step-by-step instructions are in Restore files, databases or email from a backup (JetBackup).
No clean backup? If the hack happened more than 14 days ago and you don't have your own backup, the site will need to be cleaned by hand. This usually means reinstalling WordPress core files, replacing every plugin and theme with a fresh copy, and checking the database and wp-content/uploads for malicious code. We recommend asking your web developer or a WordPress security service to do this.
On a VPS or reseller account? JetBackup restores depend on your backup storage. If JetBackup shows no backups, open a ticket and we'll check what restore options are available for your server.
Step 3: Close the door the attacker used
Restoring a backup brings back the site, but it also brings back whatever weakness let the attacker in. Do all of these straight away, before the site gets hacked again:
- Update everything. Update WordPress, every plugin and every theme. Outdated plugins are by far the most common way in. You can do this in WordPress under Dashboard → Updates, or in cPanel → WP Toolkit.
- Delete what you don't use. Remove inactive plugins and themes, and old copies of the site (like
/old,/testor/backupfolders). These still get attacked even when they're switched off. - Check your users. In WordPress, go to Users and delete any administrator you don't recognise.
- Change your passwords. Use a new, unique password for:
- every WordPress admin user (see Log in to your WordPress dashboard and reset a forgotten password)
- your cPanel account, using Change Password on your service page
- any FTP accounts
- email accounts on the domain, if they share a password with the website
- Turn on two-factor authentication for WordPress (using a security plugin) and for cPanel. See Turn on two-factor authentication for cPanel.
- Turn on automatic updates in cPanel → WP Toolkit, so security fixes are applied without waiting for you.
Step 4: Scan for anything left behind
Our servers run Imunify360, which scans hosting accounts in the background and automatically cleans or quarantines many known malicious files. That's a good safety net, but it can't catch everything, so we also recommend scanning the site with a WordPress security plugin such as Wordfence. If you find you're having to restore again and again, there's likely a backdoor still on the site, and it's time to get a developer to clean it properly.
Step 5: Tidy up afterwards
- If Google flagged your site, request a review in Google Search Console once it's clean.
- If you use a caching plugin or Cloudflare, purge the cache so visitors stop seeing the hacked version.
- If the site was sending spam, see Outgoing spam detected on my account.
- Keep your own backup too. You can download a full copy of your account at any time. See Download a full backup of your hosting account.
What we can help with
We look after the hosting platform, the server security and the backups. We're happy to restore a backup for you, or help you work out which date to use. Cleaning and repairing website code, plugins and themes is the responsibility of the website owner or their developer.
If you'd like a hand, open a support ticket from Support → Open Ticket and tell us:
- the domain name that's affected
- roughly when it last worked normally
- whether you'd like us to restore a backup (files, database or both) and from which date
Please don't include passwords in the ticket. If we need login details, we'll ask you to send them securely. See How to send sensitive data to our team securely.












