Hi Paul,
Thank you for the clarification.
To clarify from our side: the site was indeed breached via the SP Page Builder exploit you referenced, which explains the unauthorized Super User account we found and purged. The hackers then used that access to drop the standalone backdoor into the Helix template subdirectory.
My concern wasn't that Helix had a specific vulnerability, but rather that Joomla confidently reported version 2.2.4 as "Up to Date" when 2.2.6 was available. If the update mechanism had reliably flagged that an override update was pending, our routine audits would have caught the version drift much sooner. Leaving a hardcoded 2018 creation date in a modern package manifest only compounds that confusion during a post-breach audit.
We have now manually forced the update to 2.2.6, fully cleared the environment, and will be deploying our upcoming EasyStore launch on a completely wiped, sterile directory with a fresh database to ensure total compliance.
No further troubleshooting is required on this ticket. I will mark this as resolved.
Regards,
Bruce