Hacker News
4 years ago by 1cvmask

No surprise at all that this happened. They had not turned on multi-factor authentication and hackers got in through a static password. Over 80% of data breaches are through static passwords.

From the official GoDaddy statement:

Using a compromised password, an unauthorized third party accessed the provisioning system in our legacy code base for Managed WordPress.

-

This could have been an easily avoidable data breach.

4 years ago by bilekas

But they said :

> We, GoDaddy leadership and employees, take our responsibility to protect our customers’ data very seriously

So that makes it okay right ?

4 years ago by kreeben

No. You should only work with partners who take that responsibility extremely seriously. "Very" is an order of magnitude too low.

4 years ago by cpach

I’m pretty sure 'bilekas was being sarcastic :)

4 years ago by gizdan

Totally makes it okay! I assume that's after the data is stolen and sold.

4 years ago by Zancarius

See, the trick is to sell customer data before the bad guys get it!

4 years ago by mooreds

> Over 80% of data breaches are through static passwords.

Static passwords are bad, for sure. But do you have a source for this?

4 years ago by 1cvmask

See page 5 of the Verizon report and the number is 81%:

https://www.verizon.com/business/resources/reports/2017_dbir...

4 years ago by mooreds

Awesome, thanks for sharing that link from 2017.

For everyone not going to go to the PDF, the text is "81% of hacking-related breaches leveraged either stolen and/or weak passwords."

So I'm not sure that you can say that all data breaches are related to static passwords, but it sure a big number and a problem.

I looked at the 2020 Verizon report, but unfortunately they changed their methodology or reporting so I didn't see a figure for that year for "hacking-related breaches".

4 years ago by alexis2b

Over 80% of statistics posted in comments are made on the spot.

4 years ago by mellavora

no, the correct figure is 78%

4 years ago by theplumber

An even better solution is webAuthn...I don't understand why it's not supported more than "2nd factor" which very often happens to be a phone/sms verification service, easy to steal as well.

4 years ago by paulpauper

A static password is fine if you have a good strength and rate limiting or other ways to prevent brute forcing

4 years ago by vimda

It's really not... Password reuse, other breaches, there's many ways a password can be leaked that isn't bruteforcing. Considering how low the barrier to entry to 2fa is, there really is no excuse these days

4 years ago by 1cvmask

And the classic keyloggers which have been known to be around for over 4 decades ever since the typewriter....

https://en.wikipedia.org/wiki/Keystroke_logging#History

https://en.wikipedia.org/wiki/Keystroke_logging

4 years ago by iamricks

We once had a domain stolen because somebody called GoDaddy and was able to get the 2FA code removed with a phone call and they had some leaked email credentials for the account.

We had to call GoDaddy and cancel the domain transfer, they would give us no information on how it happened.

4 years ago by bhartzer

I can tell you that unfortunately that's not an isolated case. We recover stolen domain names, and it happens quite often (that someone gets into a GoDaddy account and is able to remove 2FA).

4 years ago by cpach

IMO: Friends don’t let friends use GoDaddy.

4 years ago by unstatusthequo

Or Network Solutions… which, dare I say, is even worse.

4 years ago by Turing_Machine

Pretty much all of them are bad/evil in some way, but some are worse than others.

4 years ago by _nickwhite

Us greybeards have been around long enough to experience several of these bad/evil domain registrars. One common path I see has been:

Network Solutions -> GoDaddy -> Namecheap -> Google Domains OR CloudFlare Domains

Seriously, if anyone is still using Netsol or Godaddy, there are much better alternatives, and it's very easy to make the transition- I've helped a good handful of friends.

4 years ago by rvz

   • Up to 1.2 million active and inactive Managed WordPress customers had their email address and customer number exposed. The exposure of email addresses presents risk of phishing attacks.

   • The original WordPress Admin password that was set at the time of provisioning was exposed. If those credentials were still in use, we reset those passwords.

   • For active customers, sFTP and database usernames and passwords were exposed. We reset both passwords.

   • For a subset of active customers, the SSL private key was exposed. We are in the process of issuing and installing new certificates for those customers.

Oh dear. No mention of 2FA mechanisms here. So does that mean GoDaddy's security is not good enough or is in fact very poor?

No different to Epik's security breach I guess, but not the worst security breach I've seen in a long time when compared with Twitch [0].

[0] https://news.ycombinator.com/item?id=28771465

4 years ago by rockbruno

GoDaddy has the weirdest tech stack/tech support combination I have ever seen. I once had an issue where I was unable to update my credit card information, so I contacted their support. Their support process is basically having you give them full access to your account and then having the support person navigate your account like a regular user to see what problem you're facing. So, because I had a problem with the payment flow, she literally asked for my credit card information so she could see which error I was seeing. I was cool headed enough to explain why that was a ridiculous request but hanged up after that. No wonder they got hacked.

4 years ago by croutonwagon

Godaddy has some bad practices.

They used to randomly call us, and then ask US to verify our accounts, passcodes in order for them to tell us a domain was close to expiration.

Not an email. An unsolicited phone call where I have to validate my information.

I told them that was phishing 101 tactic and a bad practice to train users on. And if a call is standard, a user may reasonably assume an email may be too.

Ultimately they just removed my from their call list.

It was one of the most asinine things I’ve seen. It reminds me I need to move my companies domains to hover.

4 years ago by elliekelly

I’m almost afraid to ask but... how long ago did this happen?

4 years ago by rockbruno

About 3 years ago I'd say

4 years ago by dang

There's a summary here, which seems to be reporting on the OP: https://www.wordfence.com/blog/2021/11/godaddy-breach-plaint....

(Via https://news.ycombinator.com/item?id=29311286, but no comments there)

4 years ago by legrande

From my experience with GoDaddy, the amount of dark patterns using the service was astonishing. It made me move to better hosting providers. They always try to up-sell you stuff, and tack on all these additional features that you have to opt out of when buying something. You have to be real careful on there in-case you buy something you didn't want. Also their UI is really messy and things are buried in multiple deep links and menus. One out of five, do not recommend. It's no wonder they suffered a breach.

4 years ago by Dave_TRS

The dark patterns are so ridiculous I almost get a little enjoyment out of it like playing a game. When you sign up for a domain name it's a mini mission to get past the 5 separate screens of upselling and clicking the small Skip link and not the big green Continue button. If you're not paying close attention you get to your cart and there's extra crap in there, and you have to restart the level.

4 years ago by unclebucknasty

After using them for simple domain name registration, I can't imagine using them for something more complex, like hosting.

The UI is so bad that just figuring out how the contact info they collect in multiple places is used is near-impossible.

4 years ago by marcc

Why are we reading this on the SEC site and not the GoDaddy site? I did a quick search and can't find a disclosure on their site. If it's there, it's not easy to find.

Security incidents are going to happen. This particular incident looks to be avoidable (static passwords!). What we should judge the company on is their response and transparency. GoDaddy disclosed, but a new customer on the site wouldn't find this. They also used phrases like "affects our Legacy WordPress Platform" probably to attempt to shift a little blame from the current team or minimize the fall out.

When you have a security incident, be transparent, own it, and deal with it. We can tell when you are trying to sweep it under the rug and hide, and that's bad. This is an opportunity for an org to show that they put customers first and shine.

4 years ago by elliekelly

Management doesn’t put customers first. They put themselves (management) first closely followed by investors. The SEC recently indicated they’d be focusing enforcement on cybersecurity incident disclosures. Particularly on timely disclosures (not waiting 6 months from discovery to disclosure, for example).

That might be the only reason we’re even reading about this at all.

4 years ago by skeeter2020

>> Why are we reading this on the SEC site and not the GoDaddy site?

This is typically by design and public relations 101. If you don't link "bad" content to your domain it's easier to make it disappear in the future. It's why a company purchases "our-data-breach.net" to handle a public incident instead of just a sub domain or deeply linked page. No long-lived anti-SEO

4 years ago by neom

The URL contains "gddyblogpostnov222021" - and at the bottom the FLS mentioned blog post, so I guess the SEC didn't adhere to their press embargo on the blog post? ;)

4 years ago by blablabla123

That's at least the 2nd funny thing happening with GoDaddy. I stopped using them years ago.

Daily Digest

Get a daily email with the the top stories from Hacker News. No spam, unsubscribe at any time.