Our hacked WHMCS cleanup service is incident response for a WHMCS install that has been compromised or that you suspect has been. It is for hosting companies, IPTV operators and resellers who need the attacker out, the install trustworthy again and a clear record of what was touched, so they can decide what to tell customers.
Signs your WHMCS may be compromised
- Admin accounts, API credentials or email templates you did not create
- Customers reporting phishing emails or fake invoices that look like yours
- Payments landing in an account you do not own, or gateway settings that changed
- Unknown PHP files in the WHMCS directory, attachments folder or templates
- New hooks or addon modules nobody on your team installed
- Your server provider or a security scanner flagging outbound attacks or malware
Attackers usually get in through an out-of-date WHMCS version, a vulnerable or tampered third-party module, a stolen admin password, or a compromise of the server underneath. 2026 brought several WHMCS security releases on both the 8.13 and 9.x branches, so an install that missed them is a common starting point.
What's included
- Containment: maintenance mode or IP restriction on the admin area, and paused automation where needed
- A copy of files, database and logs taken before cleanup, so evidence is not lost
- File review against a clean copy of your WHMCS version to find modified and added files
- Review of hooks, addons, gateway modules, templates and the attachments and downloads folders
- Database review of admin users, API credentials, payment settings, email templates and recent activity logs
- Removal of backdoors, web shells and injected code
- Rotation of admin passwords, API credentials, gateway keys, registrar keys, server module tokens, SMTP and database passwords
- Update to a patched WHMCS release and removal or replacement of vulnerable modules
- Hardening: admin directory rename, two-factor authentication, file permissions and IP rules
- A written incident report with timeline, likely entry point, affected data and next steps
How it works
- First contact. Tell us it is an active incident so we can triage it first, and we agree the first containment steps on the call.
- Contain. We limit access and stop automated actions that could spread damage, such as outbound email or provisioning.
- Preserve. We copy files, the database and logs before changing anything.
- Investigate. We compare files, read logs and trace the entry point.
- Clean and rotate. We remove malicious code and replace every secret the attacker could have seen.
- Patch and harden. We update WHMCS and modules and close the entry point.
- Restore service. We test orders, payments and provisioning, then bring the site back.
- Report. You get the written report and a list of follow-up actions.
Timeline
We start containment as soon as access is granted. A single WHMCS install is often cleaned and back in service within 1 to 3 business days. Cases where the whole server is compromised take longer, and we may recommend rebuilding the server instead of cleaning it.
Pricing
Cleanup of a single WHMCS install starts at $299. Server-level incidents and larger environments are quoted at a fixed price once the scope is clear. If work has to start before the scope is known, the first hours are billed at our $65 hourly rate until a fixed quote is agreed. Fixed-price work is billed 50% as a deposit and 50% on delivery, and the work includes a 14-day correction window. We accept Stripe (cards, Apple Pay, Google Pay), PayPal and crypto through NOWPayments.
What's not included
- Legal advice or deciding whether you must notify customers or regulators. Under GDPR, notifying the supervisory authority is often required within 72 hours of becoming aware of a breach, so involve your legal adviser early
- Formal forensic reports for court use or card brand investigations
- Cleanup of customer websites hosted on your servers
- Recovery of data that was deleted and has no backup
Related services and modules
After the cleanup, we recommend adding a WHMCS firewall, two-factor authentication and offsite backups so the next incident is smaller. Our security modules add file change detection and exploit blocking. If you think you are under attack right now, contact us and say it is an incident.