WHAT WEBSITE OWNERS SHOULD KNOW
What ordinary website owners can learn from this documented case about automated malware action, independent backups and hosting-provider transparency.
You do not need to write software for this case to matter. If a website depends on PHP applications, plugins, custom scripts, administration tools or other files that overlap with security categories, automated scanner action can affect work that the owner considers legitimate and essential.
Keep an independent copy outside the hosting account
A provider-native backup is useful, but an independent backup under your own control gives you a second source when the hosting platform itself is part of the incident. In the September recurrence, the independent same-day backup corroborated the Hostinger-native pre-event backup byte-for-byte.
Do not assume a legitimate file is automatically exempt from automated action
Hostinger’s final position described the August detection as category and functionality based. That distinction matters because legitimate administrative functionality can overlap with categories used by security products. Owners of business-critical sites should understand what automated cleanup is allowed to do and what recovery options exist.
Preserve the before-and-after boundary as soon as something happens
When a destructive event is discovered, preserve current files, provider backups, independent backups, scanner screens, timestamps and support messages before routine retention or later edits change the record. A clean boundary is often more useful than a long argument about what probably happened.
Ask what is preserved, not only what the interface displays
A dashboard may show an event without preserving every technical field needed later. In this case, Hostinger’s final review said that several requested August fields had not been captured in the preserved event table. If a dispute matters, ask early about retention, quarantine objects, original bytes, logs, rule versions and how long each type of record remains available.
This case does not claim every Hostinger customer will experience the same thing
The warning is narrower and evidence-based: this documented experience shows why owners should not treat important hosted files as automatically immune from destructive automated action. Independent backups and a clear recovery plan are practical safeguards regardless of provider.