Can you also rescue badly outdated versions (e.g. TYPO3 8.7 or 9.5)?
Absolutely. We also secure and clean up “end-of-life” systems, while at the same time drawing up a plan for a secure upgrade to the current LTS version.
Is my provider responsible for the hack?
A blanket statement would not be serious. Hosting providers secure the infrastructure at system level. Experience shows, however, that the vulnerability often arises within the application, for example through outdated TYPO3 versions, unpatched extensions or compromised credentials. We check both.
How long does the clean-up take?
A thorough manual analysis and clean-up usually takes 1 to 3 working days, depending on the complexity and depth of the infiltration. We often initiate the first emergency measures within a few hours.
How could my TYPO3 instance be hacked despite its high security standard?
Security stands or falls with maintenance. Often it's unpatched gaps in third-party extensions (e.g. outdated powermail or news versions), an outdated PHP environment, weak backend passwords or an unprotected Install Tool.
My host has blocked the site. Can you still help?
Yes, that's our everyday business. We communicate directly with your provider (e.g. Mittwald, Hetzner, Telekom) or pull a copy onto our isolated analysis environment and remove the malicious code there.
Isn't it enough to simply restore an old backup?
A backup restores the state before the outage, but doesn't close the gap. Without a root cause analysis and security patches, your system will be infected again within hours or days.
What is the difference between your manual clean-up and automatic scanners?
Scanners often only find known signatures. Professional hackers leave backdoors as inconspicuous lines of code in LocalConfiguration.php or in extension classes. We check by hand at file and database level.
Do I have to report the hack to the data protection authority?
If personal data could have been leaked, for example from contact forms, a frontend user area or shop orders, the GDPR requires a report within 72 hours. We support you with the technical documentation.
How do we prevent my TYPO3 system from being attacked again?
After the clean-up, we harden the system: update to the current LTS version, protection of the typo3/ directory, 2FA for editors and regular monitoring of the Composer dependencies.
Which TYPO3 extensions are often the entry point?
Mostly extensions that are no longer maintained or were written for old TYPO3 versions. Custom developments without a security review are also a common way in.
How does ELTS help me after a hack?
With Extended Long Term Support, older TYPO3 versions continue to receive security updates. This can make sense if an immediate upgrade is not possible. We advise you on which path suits your system.
Do you work together with our internal IT or agency?
Gladly. For corporate and public authority sites, we closely coordinate analysis, clean-up and documentation with your IT, your data protection officer or the agency looking after the site.
What do you check during a TYPO3 clean-up besides the code?
Backend users and permissions, the Install Tool, scheduler tasks, configuration files, the database and the server environment. Attackers like to hide outside the obvious directories.
Do we get a report for compliance or insurance?
Yes. You receive documentation with the time, the route of entry, the affected areas and the measures taken, which you can use for internal audits or a cyber insurance claim.
Can TYPO3 be brought to a current LTS version after the clean-up?
Yes, and that is usually the best protection. We check extensions and templates for compatibility and carry out the upgrade in a planned way, without your site being offline for long.