Web Hosting Companies Go Bankrupt After Hackers Compromised Them Entirely

The backend of a software consists of several layers. For example, the first layer is meant for guests. Going deeper, there is one dedicated to customers, which have more access. Under that, there is a layer for moderators, which have even more access, and so forth. The deeper the layer, the larger the power and the more the access. And here, a web hosting company called 'No Support Linux Hosting' is shutting down its business because hackers appear to have "compromised" the company's entire operations, including its website, its customer database, and even its admin section. That according to a message posted on the homepage of its official website [archived]. Without explaining the details, the attack appears to have been destructive. "We can no longer operate the No Support Linux Hosting business," the company acknowledged. "All customers should immediately download backups of their websites and databases through cPanel," NSLH said, urging clients to do so before servers go down for good. Following the hack, TorrentFreak, a blog dedicated to digital rights and piracy news, reported that two UK-based web hosting companies that provide IPTV services to pirate streaming websites have also suffered similar hacks. 'SapphireSecure.net' and 'KS-Hosting.com' were both showing a similar message on their front page. In the message, the hacker of the two companies shared the personal details of the person behind the two sites and threatened the two companies to share their customer databases with police and copyright protection agencies unless a ransom of 2 Bitcoins (about $92,000) is paid. The difference between No Support Linux Hosting hack and the SapphireSecure.net and KS-Hosting.com hack is that, the hacker gave the latter two the option to shut down for good as a way to avoid having their data shared with authorities or paying the ransom. Because the three web hosting companies were hacked in proximity and with overlapping details, it is suggested that the culprit could be the same threat actor.