How to Find Unexpected Files in a Joomla Installation

Unexpected files in a Joomla installation can be harmless leftovers, files installed by extensions, or evidence of an incomplete deployment or compromise. The goal is not to delete everything that is absent from a stock Joomla package; it is to identify who owns each file and whether it belongs on this specific site.

Build a trustworthy baseline first

Record the exact Joomla version, installed extensions and templates, active hosting tools, and any known custom code. Download the matching Joomla release from the official Joomla source and obtain clean packages for third-party software from their trusted vendors. Keep these reference packages outside the live web root.

A stock Joomla archive is only a baseline for Joomla core. It will not contain your configuration.php, uploaded media, extension files, template customizations, backup archives, host-created files, or other legitimate site-specific content.

Find files that deserve investigation

  1. Compare Joomla core paths with the clean package and note extra, missing, or changed files.
  2. Review recently created or modified PHP, JavaScript, and configuration files.
  3. Look for executable files in normally static locations such as image or upload directories.
  4. Inspect unusually named files, hidden files, duplicate entry points, and scripts placed beside static assets.
  5. Check writable directories, temporary locations, and the account root as well as the public Joomla directory.

Do not treat timestamps alone as proof. Restores, deployments, updates, and malicious activity can all change timestamps.

Trace each file to an owner

For a file under components, modules, plugins, templates, libraries, or extension media, compare the path and contents with the installed vendor package. For media and documents, identify the administrator or workflow that created them. A file is genuinely unexpected when you cannot explain it through Joomla core, a trusted package, site content, hosting, or an intentional customization.

Preserve suspicious files before removal

If compromise is possible, copy suspicious files and relevant logs to a protected location before deleting or replacing anything. Record the full path, size, timestamps, and a cryptographic hash if your incident process supports it. Do not execute unknown PHP through a browser or command line merely to discover what it does.

Also preserve web-server, PHP, authentication, control-panel, and Joomla logs that cover the suspected time window. Cleanup can otherwise destroy clues needed to find the entry point.

Restore files from trusted packages

When a Joomla core file is confirmed to be added or modified unexpectedly, restore core using Joomla's supported update/reinstall process or the exact official package. Restore third-party files from the matching trusted vendor package. Preserve configuration.php, user uploads, and intentional site-specific files rather than blindly replacing the whole document root.

Verify the problem does not return

After cleanup, test the frontend and Administrator, review logs, run Joomla and extension update checks, and repeat the filesystem comparison. If suspicious files reappear, investigate administrator and hosting credentials, vulnerable extensions, scheduled jobs, writable paths, database content, SSH/SFTP accounts, and other sites under the same hosting account. Repeatedly deleting a file without closing its creation path is not a complete recovery.


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.

Open a Support Ticket