How to Reset Joomla Administrator Accounts After a Compromise

After a compromise, every Joomla Administrator and Super User account must be re-verified. Block unknown identities, reset trusted accounts, review privilege and authentication factors, and preserve evidence before deleting suspicious records.

Inventory every privileged account

After containing the incident, open Users → Manage and identify all accounts with Administrator or Super User privileges. Compare them with an authoritative list of staff, contractors, integrations, and service accounts. Record username, email, user ID, group memberships, and relevant login information.

Block suspicious accounts while preserving evidence

Block any unauthorized or unverifiable account before deleting it. Preserve the account details and related logs so you can determine when it appeared and what it may have changed. Deletion can remove useful context during an investigation.

Reset passwords for trusted administrators

Set new unique passwords for legitimate privileged users and do not reuse credentials that existed before the incident. Where appropriate, require users to set a new password at their next login. Deliver temporary recovery information through a secure channel.

Recover access carefully if no trusted Super User remains

If all trusted administrators are locked out, use Joomla's documented administrator-recovery procedure or a controlled database recovery method. Do not paste unknown password hashes from random sources. Once access is restored, replace temporary credentials immediately and remove any temporary recovery configuration.

Review groups, sessions, and authentication factors

Verify that each privileged account belongs only to required groups. Revoke active sessions and tokens where supported, then re-establish MFA or WebAuthn for trusted administrators. Re-enroll factors or recovery codes if they could have been exposed.

Confirm account repair is part of full recovery

Resetting administrator accounts does not remove web shells, vulnerable extensions, stolen hosting credentials, malicious database content, or scheduled persistence. Continue the wider incident recovery, rotate infrastructure credentials, rebuild compromised code, and monitor authentication logs after the site returns to service.


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