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 articleResearchers 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.
Related
Polyfill supply chain attack hits 100K+ sites
A supply chain attack on Polyfill JS affects 100,000+ websites, including JSTOR and Intuit. Malware redirects mobile users to a betting site. Users advised to switch to trusted alternatives like Fastly and Cloudflare.
5 WordPress Plugins Compromised; Millions of Websites at Risk
Millions of WordPress sites face security risks from hacked plugins allowing unauthorized access. Owners urged to check, deactivate compromised plugins, update regularly, use strong passwords, two-factor authentication, and security plugins.
Over 100K+ Sites Hit by Polyfill.io Supply Chain Attack
A supply chain attack on Polyfill.io affected 100,000+ websites, redirecting mobile users to a betting site. Security measures like link rewriting and integrity checks are advised to mitigate risks in web development.
Blog.ethereum.org Mailing List Incident
A phishing email targeted 35,794 Ethereum blog subscribers, attempting to drain wallets through a malicious link. Security measures were promptly taken, no funds were lost, and further precautions are underway.
- 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.
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.
> “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.
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?
https://securityalliance.notion.site/A-Squarespace-Retrospec...
Any recommendations for a quality domain registrar? Might as well get started with the migration
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.
Damn.
I think I'm going to switch from fintech to cybersecurity.
Schnikey.
Related
Polyfill supply chain attack hits 100K+ sites
A supply chain attack on Polyfill JS affects 100,000+ websites, including JSTOR and Intuit. Malware redirects mobile users to a betting site. Users advised to switch to trusted alternatives like Fastly and Cloudflare.
5 WordPress Plugins Compromised; Millions of Websites at Risk
Millions of WordPress sites face security risks from hacked plugins allowing unauthorized access. Owners urged to check, deactivate compromised plugins, update regularly, use strong passwords, two-factor authentication, and security plugins.
Over 100K+ Sites Hit by Polyfill.io Supply Chain Attack
A supply chain attack on Polyfill.io affected 100,000+ websites, redirecting mobile users to a betting site. Security measures like link rewriting and integrity checks are advised to mitigate risks in web development.
Blog.ethereum.org Mailing List Incident
A phishing email targeted 35,794 Ethereum blog subscribers, attempting to drain wallets through a malicious link. Security measures were promptly taken, no funds were lost, and further precautions are underway.