Recently a security breach occurred in 445 of GoDaddy’s web hosting accounts. While that may not seem like a lot on a percentage basis, that is also high enough to indicate that the hack was some type of systemic problem. This can scare the new user into a lot of frantic questions.
Panicked thought is seldom a clear thought. So even if you were one of the accounts in question, there are things that you’ll want to consider when evaluating this incident.
Innocent until proven guilty
One of the most obvious knee-jerk responses is the one that is most necessary for us to correct immediately: blaming GoDaddy. When something like this happens, until you have very specific, proven reason to believe otherwise, it’s unwise and unfair to blame the host. We’re hesitant to even use this as an article topic for that reason. We only are because this will happen now and then, and it’s good to have the object lesson.
Why did this only happen with GoDaddy though, you might ask? There are many reasons that have nothing to do with them. The most obvious is just efficiency. By focusing their attack on one host with many users, the hacker(s) don’t have to concern themselves with more than one system architecture.
What actually happened?
Let’s summarize the incident. The compromised accounts had their .htaccess file changed. This is a file that handles URL requests on the user account level. It sets rules for how to treat different requests to that user’s web site based on different criteria. In this case, it was set so that any hits to the user’s site that came from a major search engine were redirected to a malicious outside site. This site in turn infected the surfer’s browser, continuing and amplifying the disease.
The accounts have since been re-secured, but this does now require that we ask the pertinent question: how were the accounts infiltrated?
They got the passwords – but how?
What we know is that somehow the bad guys got these user’s passwords. What we don’t know is how. So in lieu of having further information, we must use this opportunity to repeat two of the oldest security cautions:
- Keep your software updated – One site suggested the possibility that the users exploited a hole in a web site created by an outdated version of WordPress of Joomla! You need to decide how much it’s worth it to stay close to the news reel on security updates, but either way don’t ignore them entirely.
- Choose secure passwords! – This is the bane of the security world. Even after decades of warning, users still continue to have “123456” and “password” for passwords. Do you? Change it! This is a major reason why we must give GoDaddy the benefit of the doubt: this alone might have been the cause of the break-in.
In summary, if there’s any one piece of advice we can take from this incident, it’s this: don’t panic. Security for your web site requires clear-thinking at all times.
