---
title: "Discussion on \"Web Hosting Ransomware: What Three Host Attacks Teach Site Owners About Backups\" | Hashnode"
description: "Discussion on \"Web Hosting Ransomware: What Three Host Attacks Teach Site Owners About Backups\". Web hosting ransomware used to be a story about one customer's server. In the first half of November 2026 it became a story about the host itself. Three hosting providers, Beget and ESTT in Russia and"
url: "https://hashnode.com/posts/web-hosting-ransomware-what-three-host-attacks-teach-site-owners-about-backups/6af730758d3338c7e67e0552"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Web Hosting Ransomware: What Three Host Attacks Teach Site Owners About Backups](https://hackerme.hashnode.dev/web-hosting-ransomware-what-three-host-attacks-teach-site-owners-about-backups?utm_source=hashnode&utm_medium=feed)

Web hosting ransomware used to be a story about one customer's server. In the first half of November 2026 it became a story about the host itself. Three hosting providers, Beget and ESTT in Russia and

5d ago · 5 min read · hackerme.hashnode.dev  
Read the article

-   [#security](https://hashnode.com/tag/security)
-   [#web-hosting](https://hashnode.com/tag/web-hosting)
-   [#backup](https://hashnode.com/tag/backup)
-   [#ransomware](https://hashnode.com/tag/ransomware)

## Written by

[HackerMe](https://hashnode.com/@hackerme)

@hackerme

  
[View profile](https://hashnode.com/@hackerme)

Autonomous security testing powered by AI agents. Powerful. Accurate. Actionable.

## Responses 2

Markdown supported · ⌘↵ to post

[Ali Asghar Jamil](https://hashnode.com/@alijay)

[1d ago](https://hashnode.com/posts/web-hosting-ransomware-what-three-host-attacks-teach-site-owners-about-backups/6af730758d3338c7e67e0552/comment/6afc5e2f1289dc05daa76b65)

Useful write-up. The point about the management layer being the weak spot is the part most site owners miss.

Full disclosure: I work at Cloudways. Even though we store server backups off-site by default and let users download them, I still recommend keeping an independent copy in an account you control; that is what saves you if the provider itself goes down. As you mentioned, a backup you have never tested is just a guess.

[HackerMe](https://hashnode.com/@hackerme)

[1d ago](https://hashnode.com/posts/web-hosting-ransomware-what-three-host-attacks-teach-site-owners-about-backups/6af730758d3338c7e67e0552/comment/6afc5e2f1289dc05daa76b65#reply-6afc62603c0ad99dcb94dff3)

Thanks Ali, and thanks for the disclosure. Agreed, the independent copy in an account you control is the part people skip until they need it. I'd add one step: restore it to a staging site now and then, not just download it.

Disclosure on my side: I'm with HackerMe (hackerme.ai), a free outside-in website scanner. We often see the opposite backup problem there: a backup.zip or SQL dump left on a public URL, where anyone can download it.
