Help Centre › Plesk Panel › Plesk Website Hacked Malware
This troubleshooting guide walks UK Plesk hosting users through the symptoms, likely causes and fixes for Plesk Website Hacked Malware. Steps apply to any standard Plesk Obsidian installation — including managed hosting from smartxhosting.uk/web-apps where this guide assumes EU data-centre infrastructure, modern Plesk Obsidian (18.x) and a Linux back-end. Each solution is ordered from most-common to more-advanced.
Symptoms of a Compromised Website · Common Causes · Solution 1: Check Imunify360 in Plesk · Solution 2: Change All Passwords Immediately · Solution 3: Restore from a Clean Backup · Solution 4: Update Everything and Remove Unused Software · Solution 5: Scan Again and Verify · Preventing Future Attacks · When to Contact Support · FAQ
Common causes of this issue in a Plesk environment:
- Resource exhaustion — disk, memory or PHP process limits hit. Check in Plesk → Statistics or smartxhosting.uk dashboard.
- Configuration drift — a recent change (PHP version, cron schedule, DNS record) broke previously-working setup.
- Service crash — a backend service (MySQL, Nginx, Apache, Postfix) stopped. Restart from Plesk → Tools & Settings → Services Management.
- Permission issue — file or directory ownership/mode changed; Plesk File Manager shows this.
- Third-party plugin / module — an extension is misbehaving; disable temporarily to isolate.
- Upstream network — DNS propagation, provider routing, or UK ISP issue (check from another network).
Common causes of this issue in a Plesk environment:
- Resource exhaustion — disk, memory or PHP process limits hit. Check in Plesk → Statistics or smartxhosting.uk dashboard.
- Configuration drift — a recent change (PHP version, cron schedule, DNS record) broke previously-working setup.
- Service crash — a backend service (MySQL, Nginx, Apache, Postfix) stopped. Restart from Plesk → Tools & Settings → Services Management.
- Permission issue — file or directory ownership/mode changed; Plesk File Manager shows this.
- Third-party plugin / module — an extension is misbehaving; disable temporarily to isolate.
- Upstream network — DNS propagation, provider routing, or UK ISP issue (check from another network).
Apply this fix:
- Open Plesk and navigate to the relevant section for the failure.
- Apply the specific change indicated in the heading — restart service, correct a setting, or rebuild the affected component.
- Test the issue has been resolved by reproducing the original failure case.
- If resolved, note any preventive steps for the future.
UK note: smartxhosting.uk support can apply this fix on your behalf from the server side if needed — open a ticket from the client area.
Apply this fix:
- Open Plesk and navigate to the relevant section for the failure.
- Apply the specific change indicated in the heading — restart service, correct a setting, or rebuild the affected component.
- Test the issue has been resolved by reproducing the original failure case.
- If resolved, note any preventive steps for the future.
UK note: smartxhosting.uk support can apply this fix on your behalf from the server side if needed — open a ticket from the client area.
Apply this fix:
- Open Plesk and navigate to the relevant section for the failure.
- Apply the specific change indicated in the heading — restart service, correct a setting, or rebuild the affected component.
- Test the issue has been resolved by reproducing the original failure case.
- If resolved, note any preventive steps for the future.
UK note: smartxhosting.uk support can apply this fix on your behalf from the server side if needed — open a ticket from the client area.
¶ Solution 4: Update Everything and Remove Unused Software
Apply this fix:
- Open Plesk and navigate to the relevant section for the failure.
- Apply the specific change indicated in the heading — restart service, correct a setting, or rebuild the affected component.
- Test the issue has been resolved by reproducing the original failure case.
- If resolved, note any preventive steps for the future.
UK note: smartxhosting.uk support can apply this fix on your behalf from the server side if needed — open a ticket from the client area.
¶ Solution 5: Scan Again and Verify
Apply this fix:
- Open Plesk and navigate to the relevant section for the failure.
- Apply the specific change indicated in the heading — restart service, correct a setting, or rebuild the affected component.
- Test the issue has been resolved by reproducing the original failure case.
- If resolved, note any preventive steps for the future.
UK note: smartxhosting.uk support can apply this fix on your behalf from the server side if needed — open a ticket from the client area.
Preventive steps that reduce the chance of this issue recurring:
- Keep Plesk and all installed applications (WordPress, PHP, Node.js) updated.
- Maintain recent backups — daily server-side + weekly off-server ZIP.
- Monitor disk and bandwidth usage monthly.
- Avoid installing untested third-party Plesk extensions on production.
- Document routine changes (DNS edits, PHP version swaps) so you can roll back.
- For UK businesses, ensure Plesk admin credentials are stored in a password manager, not a spreadsheet.
This section covers the practical aspects of plesk website hacked malware in Plesk Obsidian for UK users.
The feature is accessed from the main Plesk panel — typically via a left-sidebar entry or a per-domain settings tab. Behaviour is consistent across Plesk Linux (smartxhosting.uk default) and Plesk Windows with minor path differences.
For managed Plesk hosting with UK support and VAT invoices, see smartxhosting.uk/web-apps. Under UK GDPR, include any personal data processed through this feature in your data-processing inventory.
Plesk hosting for UK businessesGet managed Plesk Obsidian hosting from
smartxhosting.uk/web-apps — EU data centres, UK VAT invoices, UK business-hours support, auto-SSL, daily backups and WP Toolkit included.
Q: How do I know if my issue matches this guide?
A: Compare the symptoms described in the When-This-Occurs section. If they match, apply the solutions in order. If not, check other Plesk troubleshooting articles.
Q: Will applying these fixes affect my live site?
A: Most fixes are non-destructive (restart services, adjust settings). Any risky action (database repair, file restore) is flagged explicitly. Always back up before making changes in production.
Q: Do I need root SSH access?
A: Most fixes work inside the Plesk panel UI. Some advanced steps mention SSH. On managed smartxhosting.uk Plesk hosting, root SSH is not required — panel access covers everything.
Q: Does this apply to Plesk on Windows as well as Linux?
A: Most solutions apply to both. Where behaviour differs (file paths, service names), we note it. smartxhosting.uk runs Plesk on Linux; the guide assumes that default.
Q: What if the fix does not resolve the issue?
A: Move to the next solution. If every solution fails, contact smartxhosting.uk support via the client area with the error message and the solutions you have already tried. UK business-hours response typically within a few hours.
Q: Where do I get more Plesk support?
A: For smartxhosting.uk-hosted Plesk accounts, priority support is available through the client area. Plesk also maintains extensive official documentation that complements this guide.