How to Determine Whether a Joomla Website Has Been Hacked
A redirect, blank page, spam content, new administrator, unfamiliar file, browser warning, or sudden resource spike can indicate a hacked Joomla site, but no single symptom proves compromise. Build a timeline, preserve evidence, and check accounts, files, database content, and logs together before deciding how to recover.
Record the symptoms before changing the site
Write down what happened, the first known time, affected URLs, browser messages, unexpected users, email activity, and recent legitimate maintenance. Capture screenshots and preserve relevant logs where possible.
If the site is actively redirecting visitors, serving malware, exposing data, or being used to attack others, restrict public access promptly. Preserve a copy of the affected files/database before cleanup when it is safe to do so.
Audit Joomla and hosting accounts
- Review Joomla users with Super User or other elevated privileges.
- Look for new accounts, unexpected privilege changes, or altered email addresses.
- Review hosting control-panel, SFTP/FTP, SSH, database, and deployment accounts.
- Check available login/audit history for access that does not match authorized administrators.
An unauthorized privileged account is strong evidence that the investigation must include credentials and hosting access, not only Joomla files.
Compare files with trusted sources
Compare Joomla core with the official package for the installed version and compare extensions/templates with trusted vendor packages or source control. Look for both modified files and unexpected new files, especially executable PHP in writable media/upload locations.
Do not trust a site simply because core files compare cleanly. A compromise can live in an extension, template, custom code, database content, scheduled job, or stolen account.
Review logs and database changes
Examine web-server access/error logs, hosting security logs, authentication records, and Joomla logs around the first known symptom. Look for requests to unfamiliar scripts, unusual POST activity, exploitation attempts, or access to paths that should not be public.
In the database, review suspicious injected links/scripts, module or template settings, privileged users, redirects, scheduled activity, and extension-specific records. Preserve a database copy before deleting evidence.
Check the computers and services that administer Joomla
A clean rebuild can be compromised again if the original entry point was a stolen password or infected administrator computer. Review workstations, saved SFTP/FTP credentials, browser sessions, API tokens, CI/CD secrets, and hosting accounts used to manage the site.
Determine whether the likely entry point was Joomla core, a vulnerable extension, server configuration, another site on the account, or credentials. Recovery is incomplete until that path is closed.
If compromise is credible, recover from trusted sources
- Restrict the affected site and preserve evidence.
- Contact the hosting provider if server or account compromise is possible.
- Rotate passwords, keys, and tokens from a known-clean device.
- Patch Joomla and supported extensions; remove obsolete or unused extensions.
- Replace compromised application code with trusted clean copies or restore from a verified clean backup.
- Remove unauthorized users and malicious database content.
- Retest the site and monitor logs after returning it to service.
Deleting the visible payload alone does not restore trust. A reliable recovery addresses persistence, the original access path, and credentials that may have been exposed.
Need More Help with Joomla?
Still having trouble? Open a support ticket with QuantaCade Support and we'll be happy to help where we can.
Support priority is given to QuantaCade products, services, and customers. However, we're also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.
QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we're able to resolve.