Website migration & hardening: 25+ sites onto a modern platform – and what we found
In October 2026 we migrated 25+ websites from two outdated servers (incl. CentOS 6, PHP 5.3) onto a modern, multi-layer hardened platform. Three of five WordPress sites were compromised – we rebuilt them cleanly instead of copying. The result is safer and up to 4× faster.
Starting point
Two ageing web servers were to be consolidated – one of them running CentOS 6, PHP 5.3 and MySQL 5.1, i.e. software that has received no security updates for years. In total this involved more than 25 websites: WordPress sites, classic PHP applications, static sites, an image gallery and redirects. Target platform: Debian 13, Apache 2.4, PHP 8.4, MariaDB 11.
The key finding
We examined every site before migrating – and three of five WordPress sites were compromised, in part undetected for years. Traces ranged from 2020 into autumn 2026:
- several, partly well-disguised backdoors – including a login bypass that granted admin access without a password, and a planted administrator account;
- file timestamps had been forged so that a search for "recently modified files" would come up empty;
- on the oldest server, additional web shells in long-retired legacy sites and an open upload form from the year 2001 that was still publicly reachable.
Likely entry point: a file-manager plugin with known vulnerabilities, plus outdated plugins and commercial themes without updates.
Our approach: rebuild instead of copy
Moving an infected site one-to-one would take the attacker along. So we rebuilt the affected sites around their existing content: a fresh WordPress core and plugins from official sources (checksum-verified), media without executable files, new passwords and security keys, cleaned-up user accounts. Nothing suspicious was deleted – it was preserved in quarantine and analysed, keeping everything traceable.
The new platform – hardened in layers
- Strict isolation: each site runs under its own system user – a compromised site cannot read or alter the others.
- Daily integrity check: comparison against official checksums and a custom pattern scanner flag changed website files immediately.
- Brute-force protection for logins and scanners, a local firewall, automatic security updates including WordPress core, plugins and themes.
- Admin areas reachable only from the admin network, uploads without script execution, Let's Encrypt certificate and http→https for every site.
Our scanner was sharpened on the real findings: it detects all discovered malicious files and backdoors – with no false positives on the clean live sites.
Faster, too
With a tuned PHP opcache, adjusted process configuration and a switch of the database to InnoDB, the WordPress sites now respond up to 4× faster (time to first byte e.g. from 0.65 s down to 0.15 s).
What website operators should take away
- Old servers are not "stable", they are unprotected – without security updates, gaps stay open.
- "It still works" does not mean "it is clean": backdoors can stay active unnoticed for years.
- Do not copy a compromised site – rebuild it cleanly.
- Disable file editors and risky plugins, and truly remove retired sites.
- Rely on a daily integrity check rather than chance discoveries.
Do you run older websites yourself, or are you unsure whether everything is clean? We audit, migrate and harden your sites – get in touch.