Outcome is the same. Allowing a breach to be politicized so you can blame the company instead of the illegal act by the hackers is silly. Blaming the victim is ridiculous. Security is security and Epik got a lot of flack for their practices but I barely see anyone saying that Godaddy is responsible for this. Hackers target EVERYONE. If you have a weakness in your security they will find it. It shouldn't matter who the target is and practically doesn't matter what motivated the hackers either. Whether it's for money, politics, or the lulz. You get breached, you do your best, you move on. The Epik thread is like 100 pages. Godaddy hasn't even gotten a 2nd page thread. Just unreal.There is still more information to become available. However, there are some key differences here between the breach of Epik and the breach of GoDaddy. Like response time, scope of the breach, fall-out, motivation and goals of the hacker(s), etc. I had a serious breach about 10 years ago, and the hacker(s) placed malicious code on the server to send out spam and collect email addresses. The hackers wanted to keep the hack incognito as this would allow them to exploit the server for as long as possible. This seems to be the case here. It is to GoDaddy's credit that they identified it so soon (it occurred on Nov 17) and responded fairly quickly.
Exactly. Is Godaddy doomed? Everyone who uses them (who is that btw?) gonna move their domains and hosting now? Is it going to be some political smearing of the CEO?Just waiting for a similar explosion of rage from the same people who were furiously bashing Epik for exactly the same thing about a month ago.
There is still more information to become available. However, there are some key differences here between the breach of Epik and the breach of GoDaddy. Like response time, scope of the breach, fall-out, motivation and goals of the hacker(s), etc. I had a serious breach about 10 years ago, and the hacker(s) placed malicious code on the server to send out spam and collect email addresses. The hackers wanted to keep the hack incognito as this would allow them to exploit the server for as long as possible. This seems to be the case here. It is to GoDaddy's credit that they identified it so soon (it occurred on Nov 17) and responded fairly quickly.
Tagging @Paul Nicks here as well. He knows what GoDaddy is advising, and where to find more guidance for affected customers.Any ideas what we should do? Should we change passwords?