SoylentNews is people
SoylentNews
Bleeping Computer reports South Korean Web Hosting Provider Pays $1 Million in Ransomware Demand
Nayana, a web hosting provider based in South Korea, announced it is in the process of paying a three-tier ransom demand of nearly $1 million worth of Bitcoin, following a ransomware infection that encrypted data on customer' servers.
The ransomware infection appears has taken place on June 10, but Nayana admitted to the incident two days later, in a statement[1] on its website.
A Trend Micro analysis of the Nayana systems reveals endemic problems. It is no surprise that the hosting provider fell victim to this infection.
NAYANA's website runs on Linux kernel 2.6.24.2, which was compiled back in 2008. [...] Additionally, NAYANA's website uses Apache version 1.3.36 and PHP version 5.1.4, both of which were released back in 2006. Apache vulnerabilities and PHP exploits are well-known;[...]. The version of Apache NAYANA used is run as a user of nobody(uid=99), which indicates that a local exploit may have also been used in the attack.
The Register reports:
South Korean hosting co. pays $1M ransom to end eight-day outage
More than 150 servers were hit, hosting the sites of more than 3,400 mostly small business customers.
After a lengthy negotiation with the hackers, a demand for Bitcoin worth 5 billion won (nearly $4.4 million) was trimmed to around $1 million (397.6 Bitcoin), and the company paid up. The ransom was demanded in three [installments]; so far, two have been made.
(Score: 2) by shipofgold on Friday June 23 2017, @06:14PM (1 child)
Given the publicity of ShellShock bash vulnerability you would have thought that someone would have though a little about updates....I find it hard to believe that anyone running Linux would not have heard about ShellShock and at least gave an inkling to updating to a newer version of bash.
I wonder how many production systems still have ShellShock active and waiting for fun like this.
However, to paraphrase what parent stated: "if it aint broke don't fix it." Admins probably thought about updating, but given the age of the system feared something would break...updating to fix ShellShock probably meant a full system upgrade to a later release...I know how painful that can be.
In the end it cost somebody $1M which aint nothing.
IMHO, no backups is more unforgivable than no updates. Weekly backups would have given them a route around a $1M payment.
(Score: 0) by Anonymous Coward on Friday June 23 2017, @07:08PM
...and Heartbleed.
N.B. I love how big unpatched vulnerabilities in FOSS OSes are so rare that M$ fanboys make an effort to create cute names and logos for those.
Too bad those folks don't put that effort into Redmond's software and curing its Vulnerability of the Day thing.
...or has it gotten to Vulnerability of the Hour already?
-- OriginalOwner_ [soylentnews.org]