Security risks and ecosystem shifts in WordPress hosting
Hostinger faces significant security challenges including a 2019 data breach affecting 14 million customers and high phishing scores. WordPress founder Matt Mullenweg also highlights ecosystem conflicts between managed providers like WP Engine and alternative hosting options.
Phishing and Data Vulnerabilities
Hostinger carries a history of security failures that WordPress teams must evaluate when comparing it to Bluehost or SiteGround. In 2015, a security researcher discovered a collection of 13 million leaked plaintext passwords belonging to users of 000Webhost, which is a free web hosting brand powered by Hostinger, after an exploit in an old version of PHP. Netcraft reported in 2015 that Hostinger hosted over 90% of all Steam phishing sites. In 2019, a data breach at Hostinger affected approximately 14 million customers. Criminals also exploited Hostinger’s website preview feature in 2022 to launch phishing campaigns.
These preview URLs remain active for a maximum of 120 hours after account creation, which allows phishing sites to proliferate. In 2023, the Cybercrime Information Center placed Hostinger in the top five phishing hosts based on its Phishing Attack Score. Although the company dropped out of the top 20 by April 2026, the previous ranking indicates a specific vulnerability in how the platform handles site previews. How will Hostinger balance its expansion into AI-driven automation with the security demands of professional WordPress teams?
The Ecosystem Conflict
Matt Mullenweg urges the WordPress community to move away from WP Engine, calling the company a "cancer" to the platform. He argues that WP Engine disables core features like content revisions to save money on database storage, which breaks the core promise of WordPress to manage and protect content. Mullenweg highlights that Automattic contributes 3,900 hours per week to the ecosystem, while WP Engine contributes just 40 hours. He also criticizes the control held by Silver Lake, a private equity firm with $102 billion in assets, over WP Engine. He suggests that hungry hosts like Hostinger and Bluehost Cloud would welcome the business from users seeking data liberation.
Mullenweg notes that WP Engine recommends using a "third-party editing system" if customers need extensive revision management. He argues this practice targets profit margins at the expense of content integrity. He mentions that migrating a site to a different provider takes only one day of work. If you are managing a team, you should weigh the benefits of AI automation against the specific security risks identified in Hostinger’s history. Hostinger describes itself as an agentic platform that handles websites and marketing through AI agents.
| Host Category | Specific Risk | Relevant Fact |
|---|---|---|
| Managed WordPress (GoDaddy) | Exposed SSL and sFTP credentials | 1.2 million accounts compromised in 2025 |
| Managed Provider (WP Engine) | Loss of core WordPress revisions | 40 hours weekly contribution vs 3,900 |
| Agentic Platform (Hostinger) | Phishing via preview URLs | 120-hour active window for preview URLs |
Comparative Exposure
Comparing the risk profile of Hostinger against other major players reveals different types of exposure. GoDaddy recently reported a breach where unauthorized access to its managed WordPress servers exposed data for 1.2 million customers. This breach, discovered on November 17, involved unauthorized access to systems starting around September 6. The exposure affected both active and inactive managed WordPress users. The compromised data included email addresses, customer numbers, sFTP credentials, and WordPress database passwords. In some cases, the compromise of SSL private keys could allow an attacker to impersonate a website or its services.
GoDaddy’s chief information security officer, Demetrius Comes, said the company detected unauthorized access to systems where it hosts and manages WordPress servers. The breach also exposed the original WordPress admin password created during the initial installation. GoDaddy responded by resetting customer passwords and issuing new SSL certificates. Hostinger avoids some of these specific managed WordPress risks by offering direct control through hPanel, but its history with phishing and massive data breaches makes it a risky choice for security-sensitive WordPress teams. Teams should prioritize providers that do not have a history of high phishing scores.