How to Check a Joomla Website for Unexpected Modified Files
Unexpected file changes can reveal a failed deployment, accidental edit, outdated customization, or compromise. The key is to compare the live site against trustworthy sources instead of judging a file only by its timestamp or name. Preserve suspicious evidence before replacing anything.
Create a trustworthy baseline
Record the installed Joomla version and the versions of important extensions and templates. Obtain the matching Joomla package from an official Joomla source and trusted copies of third-party packages or source-control history.
An old backup can help, but do not assume it is clean merely because it predates the day you noticed a problem. A compromise or unwanted change may have existed unnoticed for weeks.
Find recently changed files
Use the hosting file manager, SSH, deployment tooling, or a security/file-integrity scanner to list files by modification time. Focus first on changes that do not line up with known Joomla, extension, template, or deployment work.
Timestamps are clues, not proof. Updates, restores, cache generation, uploads, and attackers can all change file times. Preserve the path, timestamp, size, and a copy of anything suspicious before cleanup.
Separate expected writable data from executable code
Changes under cache, logs, media, thumbnails, and temporary directories can be routine. Changes to PHP code, templates, plugins, libraries, and files loaded on every request deserve more scrutiny unless they correspond to a known update.
- Prioritize unexplained PHP or JavaScript changes.
- Look for executable files in media/upload locations.
- Check hidden files and unfamiliar archives.
- Review old/staging site copies that may still be web-accessible.
Compare Joomla core, extensions, and templates separately
- Compare Joomla core paths with the package for the exact installed release.
- Compare third-party components, modules, plugins, libraries, and templates with trusted vendor packages.
- Compare custom code with version control or a known-good deployment artifact.
- Investigate both modified files and unexpected new files.
Do not overwrite a difference until you know whether it is a legitimate customization. If compromise is possible, keep a forensic copy before restoring clean code.
Correlate suspicious changes with logs and accounts
Review web-server access/error logs, Joomla administrator accounts, hosting/SFTP/SSH accounts, and deployment activity around the suspicious timestamps. Requests to an unfamiliar PHP path, unexplained POST traffic, or an unauthorized privileged account strengthens the case that the file change is malicious.
If compromise is credible, stop treating the problem as a single-file cleanup. Restrict the site if necessary, preserve evidence, rotate credentials from a clean device, identify the entry point, and rebuild affected code from trusted sources.
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.