July 15th, 2024

Researchers: Weak Security Defaults Enabled Squarespace Domains Hijacks

Researchers found Squarespace's weak security defaults allowed hackers to hijack domains, targeting cryptocurrency businesses. Migration from Google Domains left accounts vulnerable, leading to phishing attacks. Squarespace improved security measures post-incident.

Read original articleLink Icon
NegligenceFrustrationDisappointment
Researchers: Weak Security Defaults Enabled Squarespace Domains Hijacks

Researchers have discovered that weak security defaults at Squarespace allowed malicious hackers to hijack several domains, particularly targeting cryptocurrency businesses. The issue stemmed from the migration of domain names from Google Domains to Squarespace, where hackers could exploit unregistered accounts by using associated email addresses. This led to domain redirection to phishing sites aimed at stealing cryptocurrency funds. Squarespace's oversight in assuming user behavior during migration left accounts vulnerable, lacking necessary verification steps. The company has since removed the option to create accounts solely with an email address. Security experts recommend steps like enabling multi-factor authentication and auditing user accounts to enhance security. The incident highlights the importance of robust security measures during domain migrations to prevent unauthorized access and potential breaches.

AI: What people are saying
The comments on the article about Squarespace's security issues and the migration from Google Domains highlight several key points:
  • Criticism of Squarespace's security negligence, with some calling for accountability and legal consequences.
  • Concerns about the lack of email verification and its security risks, with suggestions for stricter verification processes.
  • Disappointment with Google's decision to sell Google Domains to Squarespace, leading to security vulnerabilities.
  • Recommendations for alternative domain registrars and dissatisfaction with Squarespace's overall service quality.
  • Calls for a more secure and trustworthy domain registrar, similar to Let's Encrypt for SSL certificates.
Link Icon 15 comments
By @kentonv - 4 months
So many products make email verification optional in order to improve their funnel. But it's a huge security risk, because it leads to bugs like this. Very few engineers and PMs will actually stop to think: "Wait, what if the user's email address isn't verified?"

I kind of wish we could just pass a law that says you have to validate email addresses before attaching them to accounts at all. Because otherwise, competitive pressure will keep pushing people towards not doing it and aiming this gun at their foot in the name of conversions.

In the absence of a law: If your service insists on allowing unverified email addresses, you should store them in a completely different place in your database from verified ones. Maybe even obfuscate them with some encoding. Do whatever you can to make it really hard for anyone to accidentally rely on an unverified address. Ideally make it impossible for anyone except the team in charge of authentication to even see an unverified address.

On another note, holy shit. So many people (myself included) chose Google Domains specifically because they thought it would be secure and trustworthy, because it's Google. Won't make that mistake again.

By @diggan - 4 months
> Taylor Monahan, lead product manager at Metamask, said Squarespace never accounted for the possibility that a threat actor might sign up for an account using an email associated with a recently-migrated domain before the legitimate email holder created the account themselves.

> “Thus nothing actually stops them from trying to login with an email,” Monahan told KrebsOnSecurity. “And since there’s no password on the account, it just shoots them to the ‘create password for your new account’ flow. And since the account is half-initialized on the backend, they now have access to the domain in question.”

This sounds like gross security negligence, and should probably be considered a crime when you're at the size of Squarespace with (assuming) a dedicated security team. Hopefully executives/management can be held responsible for whatever damage was done because of this.

By @meiraleal - 4 months
Wow that's a terrible way Google managed customers security, selling them to an incompetent buyer. So many red flags pushing me to stop using anything Google.
By @nikolay - 4 months
Google sold Google Domains to the worst possible buyer! Right after a bunch of my domains, one by one got transferred to those amateurs, creating a random subdomain for each domain, I started to receive notifications about somebody trying to reset my password!
By @23B1 - 4 months
This move of google domains over to squarespace is the dumbest deal I have ever experienced and it makes me hate both companies even more.
By @wintermutestwin - 4 months
When I evaluated squarespace for a couple nonprofits I work with, they lost out to Wix because squarespace lacked a backup solution. I was stunned by that, but certainly not that such a cluefree team would cut security corners.

How is it possible that this team blew off backup functionality for a product that is targeted at low skill end users? Maybe they ran out of money paying designers for yet another template that utilizes a full screen image on the landing page?

By @IntToDouble - 4 months
By @jddj - 4 months
Ugh.

Any recommendations for a quality domain registrar? Might as well get started with the migration

By @TheNewsIsHere - 4 months
The problem with Squarespace remaining silent with this is that there’s a deafening lack of authoritative information about whether this issue has been patched. The researchers and Krebs are stopping short of making definitive statements because obviously only Squarespace can do that, and they aren’t.

I have emailed some former clients I knew to use Google Domains just as a heads up, with steps from the article.

It would be nice if Squarespace showed a modicum of ownership for their failings here.

By @christophilus - 4 months
Is there a reason that there isn’t a Let’s Encrypt-like disruptor for registrars? It seems like it’s such a cesspool.
By @awinter-py - 4 months
welp that was fast
By @hahahacorn - 4 months
I know we all make mistakes, and that I'm particularly fallible, but...

Damn.

I think I'm going to switch from fintech to cybersecurity.

By @WillPostForFood - 4 months
Clearly Squarespace is the guilty party here, but man, I am still upset Google shut down Domains, and can't help but direct some ire their abandonment of yet another product.
By @dboreham - 4 months
For the impatient, what they did was: put a zillion DNS registration accounts into a limbo state where anyone who knew, or could guess the email address associated with an account, could supply that, and a password of their choice, to gain authentication credentials valid for the account because they stored the supplied password without any verification that it came from the owner of the associated email address.
By @tomrod - 4 months
So glad I migrated everything off of Squarespace. Just an awful experience. Slick website. Slow as mud movement for everything else. AND--the owner can't modify MX records, you have to create and grant admin rights as the owner to an entirely separate account.

Schnikey.