Discovering that your website may have been compromised can be stressful. Unexpected redirects, unfamiliar administrator accounts, suspicious files, and changes to website content can all indicate a possible security incident.
The priority is to protect your accounts, understand what happened, limit further damage, and restore the website safely.
Signs Your Website May Have Been Compromised
Watch for:
-
Website pages displaying content you did not publish.
-
Unexpected redirects to unfamiliar websites.
-
Administrator accounts you do not recognize.
-
Unknown plugins, themes, scripts, or files.
-
Unexpected changes to website configuration.
-
Browser warnings about suspicious or unsafe content.
-
Unusual password-reset notifications.
-
Customers reporting suspicious messages or activity associated with your website.
One unusual symptom does not automatically prove that your website has been hacked. However, unexpected changes should be investigated promptly.
Step 1: Protect Your Accounts
If you suspect unauthorized access:
-
Use a trusted, updated device to access your accounts.
-
Change the password for affected website administrator accounts.
-
Change related hosting and email passwords if they may also be exposed.
-
Use unique passwords that are not shared across services.
-
Review user accounts and remove access that is no longer authorized.
-
Enable multifactor authentication where the relevant service supports it.
If you cannot safely access your website or hosting account, contact support before making further changes.
Step 2: Preserve Information About the Incident
Before deleting files or making major changes, record what you have observed.
Document:
-
The affected domain and pages.
-
The time you first noticed the problem.
-
Any unusual redirects or browser warnings.
-
Suspicious accounts, files, or software.
-
Recent website changes or installations.
-
Relevant error messages.
Preserving this information can help identify how the incident occurred and which components were affected.
Step 3: Limit Further Exposure
Depending on the nature of the incident, you may need to temporarily restrict access to affected website areas.
Consider:
-
Disabling access to a compromised administrator account.
-
Removing unauthorized users.
-
Temporarily restricting access to an affected application.
-
Warning users if sensitive information may have been exposed.
-
Avoiding administrative activity from a device that may itself be compromised.
Do not delete unfamiliar files indiscriminately. Some files may be legitimate application components, and deleting them could cause additional damage.
If you are unsure how to restrict access safely, ask WebDaddy Pro Support for guidance.
Step 4: Contact WebDaddy Pro Support
If the incident may involve your hosting service, submit a support ticket.
Include:
-
Your domain name.
-
A description of the suspicious activity.
-
When you first noticed it.
-
Any affected pages or services.
-
Relevant error messages.
-
Steps you have already taken.
Do not include account passwords, payment card information, or other sensitive credentials in a support ticket.
Step 5: Investigate the Cause
A website compromise can result from several sources:
-
Vulnerable or outdated website software.
-
Compromised administrator credentials.
-
Unsafe or abandoned plugins and themes.
-
Insecure file permissions.
-
Compromised third-party integrations.
-
Malicious files introduced through an application vulnerability.
Identifying the cause is important. Removing visible suspicious content without addressing the underlying vulnerability may allow the attacker to regain access.
Step 6: Consider Restoring a Clean Backup
If website files or database content have been altered, a known-good backup may help recover the site.
WebDaddy Pro hosting includes continuous data protection and on-demand restores.
Before restoring:
-
Determine which website files or database components are affected.
-
Identify a recovery point from before the suspected compromise, if available.
-
Consider whether the backup may already contain the malicious changes.
-
Address the original vulnerability and compromised credentials.
-
Confirm which data may be replaced during restoration.
A backup should not be restored blindly. If the source of the compromise remains unresolved, the website may become vulnerable again.
For more information, see How to Restore Your Website from a Backup once that article is published.
Step 7: Secure the Website Before Returning to Normal Operation
After the incident has been addressed:
-
Update the website platform and its extensions.
-
Remove unauthorized accounts.
-
Replace compromised passwords.
-
Review administrator privileges.
-
Remove software that is no longer required.
-
Verify important website files and configuration.
-
Check website pages, forms, and database-connected functions.
-
Confirm that HTTPS works correctly.
-
Review email and domain settings for unauthorized changes.
If customers or other users may have been affected, assess what information was exposed and follow any applicable notification and legal requirements.
Step 8: Reduce the Risk of Another Incident
Use ongoing security practices:
-
Keep website software updated.
-
Use unique passwords.
-
Restrict administrative access.
-
Review account permissions periodically.
-
Use secure connections.
-
Maintain recoverable backups.
-
Monitor unexpected changes.
-
Use the security protections included with your hosting service.
Need Help?
If you suspect your website has been compromised, contact WebDaddy Pro Support.
Provide a clear description of the issue and avoid sharing passwords or other confidential credentials in your request.