What to Do When a Joomla Website Has Been Compromised
A compromised Joomla site should be treated as an incident, not as a single bad-file cleanup. Contain it, preserve evidence, identify the access path, rotate exposed credentials, rebuild affected code from trusted sources, and verify that persistence is gone before returning the site to service.
Contain the incident before cleanup
If compromise is confirmed or strongly suspected, restrict public access before trying to repair the visible damage. Prefer a hosting-panel, firewall, reverse-proxy, or web-server restriction that runs before Joomla when executable PHP may be hostile. Keep access available only to trusted responders and do not rely solely on Joomla's normal Offline setting for a serious incident.
Preserve evidence and build a timeline
Before deleting files or restoring a backup, preserve relevant access and error logs, hosting logs, a database snapshot, suspicious files, user and privilege information, scheduled jobs, and important timestamps. Store evidence outside the public web root. Record when symptoms began and what legitimate maintenance occurred around that time.
Notify the host and identify the entry point
Tell the hosting provider that the site may be compromised and ask for account, malware, process, authentication, and server logs that are not visible inside Joomla. Determine whether the likely entry point was vulnerable Joomla or extension code, a stolen hosting/SFTP/SSH credential, another site on the account, server software, or an infected administrator workstation.
Rotate credentials from a clean device
After containment, rotate hosting control-panel, SSH/SFTP, database, Joomla privileged-user, deployment, API, SMTP, backup, payment, and other exposed credentials as appropriate. Revoke unknown sessions, tokens, app passwords, and keys. If a secret was stored in an exposed configuration file, treat that secret as compromised.
Rebuild from trusted sources
Replace compromised Joomla core files with clean files from the correct official Joomla package and reinstall extensions/templates from trusted compatible packages. Do not simply overwrite the compromised tree and assume extra malicious files disappear. Preserve verified user content separately and inspect it before returning it to service.
Audit persistence and verify recovery
Review privileged users, extensions, database content, scheduled tasks, writable upload areas, neighboring sites, and server jobs for persistence. Patch supported software and remove abandoned or unnecessary extensions. Scan and test the recovered site in a controlled state, then reopen only after the original access path is closed and monitor logs closely for recurrence.
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.