Squarespace Site Hacked or Flagged? Recovery Steps
Squarespace sites are rarely compromised through infected files — the realistic attacks are account takeovers and DNS hijacks, like the July 2024 domain-hijacking incident. Recover the account and the domain first, then deal with any warning: those come from security vendors, and each one needs its own request before it will re-check.
TL;DR: On Squarespace the code runs on the platform's servers, so the way in is your account or your domain's DNS, not a hidden malware file. If something changed that you did not change, recover the account first: password reset from a clean device, two-factor authentication, then DNS records and nameservers. If nothing changed and a vendor is warning visitors, treat it as a false positive or a stale flag — confirm which vendor it is, then ask that vendor to re-check.
If an antivirus or browser warning is blocking your Squarespace site right now, start here: what to do when your website is blocked by antivirus. If all you see is a gray "Not Secure" in the address bar, that is an SSL setting, not a hack or a blocklist: the per-platform "Not Secure" fix.
Most "Squarespace hacked" scares are either the site you can see or the account and domain that control it.
Was my Squarespace site hacked — or is this a false positive?
Start with two questions, in this order.
Did something change that you did not change? Read your own site as a visitor, in an incognito window. Then check what visitors never see: the DNS records and nameservers on your domain, the email routing, and who has access to the account. Look for records you did not add, mail filters copying messages elsewhere, or an unrecognized collaborator. Anything on that list is a live compromise — go to recovery first.
Where exactly is the warning? A browser interstitial, an antivirus pop-up, a warning under your Google result — each is a verdict from an outside security vendor, and none of them means your site is broken. Warnings land on clean sites for reasons unrelated to their content.
If nothing changed and a warning is the only symptom, you are most likely on the false-positive path — but verify, do not assume. A compromise needs recovery first; a bad vendor verdict needs that vendor's review. A request sent before the cause is fixed is likely to be refused, or the flag to return.
The two real Squarespace attacks: account takeover and DNS hijack
Squarespace is not a server you manage: no file system to poison, no plugin to upload, no PHP to edit. The platform runs the site; your account controls the content, connections and domain — so attacks go after the account and the domain instead.
Account takeover hands the attacker everything — your pages and products, every service connected to the account, and the domains registered to it. They can publish content, change settings, or add a collaborator account.
DNS hijack moves your visitors without touching your site. Whoever controls the domain's nameservers decides where it points, so a changed nameserver record can send every visitor to a lookalike page — including ones that imitate your login or checkout — while your real site sits untouched.
The July 2024 incident showed both mechanisms at once. Squarespace's incident report says a limited number of Domains customers had their member accounts compromised through a weakness related to OAuth logins, with unauthorized changes to domain settings and DNS records. The targets were cryptocurrency-related domains and businesses; Squarespace says it detected the activity on July 9, that domains were affected through July 11, and that a fix was deployed on July 12 (Squarespace status page, 2024). The report states that all compromised accounts used third-party OAuth and that the domain migration involved no changes to multi-factor authentication. Squarespace also says it suspended affected accounts on suspicious activity and restored them after identity verification.
The lesson is not about that specific bug: the account and the domain are where the risk concentrates — the same model applies on Wix, covered in Wix site hacked.
Recover a hijacked account
If you can still sign in, work through this list. If you are locked out entirely, go straight to Squarespace support.
- Reset passwords from a clean device. Start with the email address that owns the account — it is the recovery path for everything else — then the account itself, then any tools connected to the site.
- Turn on two-factor authentication, from your account's two-factor settings: a passkey (up to five), an authentication app, or a text message where it is offered — SMS only works in Australia, Canada, Ireland, the UK and the US (Squarespace Help). Save the backup codes: eight, each usable once.
- Review everyone with access. Each contributor turns two-factor authentication on in their own account, so the access list is where you look for strangers, not the security settings page.
- Check for code you did not add. Review Code Injection and any Code blocks for scripts you did not add, and remove contributors you do not recognize.
- Contact Squarespace support about anything you cannot reverse yourself — a page you cannot edit, a change that reappears, an account you cannot reach.
Recover a hijacked domain or DNS
Domain changes are visible in your account's domains dashboard. Sign in, open your domains, select the domain, and open the DNS tab.
- Check the records. Look for entries you did not create — an A record pointing at an unfamiliar address, TXT records for services you do not use, MX records that would route your email elsewhere.
- Check the nameservers. On a Squarespace-managed domain, the Domain Nameservers section shows Squarespace's nameservers or a custom set (Squarespace Help). Squarespace's documentation makes switching to custom nameservers a deliberate, authenticated step: you re-enter your password or 2FA, DNSSEC is disabled, and your email DNS records stop applying. Custom nameservers you did not set are a hijack — complete the account recovery steps first.
- Take a screenshot or export of the current DNS records first: it is evidence, and you may need to recreate mail and site records.
- Reset to "Use Squarespace nameservers", then re-check your records — the ones served elsewhere are discarded in the move.
- Check that the domain lock is on — the setting that guards against unauthorized registrar transfers.
- Expect nameserver changes to take up to 48 hours to work through. Do the password and 2FA steps first, so whoever made the change cannot simply undo your fix.
Watch for phishing that impersonates Squarespace
Almost every platform compromise starts with an email that looks like it came from the platform. Never sign in through a link in an email — open Squarespace directly from your bookmark or by typing the address, and check for notifications inside the account itself.
Treat unexpected demands with suspicion, especially any message claiming a "security review" or "compliance check" is needed to keep your site online. Squarespace's Help Center asks customers to forward suspicious messages to reportphishing@squarespace-security.com, and says the company never asks for your password or your full card details by email. If you already clicked or replied, reset the exposed passwords from a clean device and check the account for changes you did not make.
Why warnings on Squarespace sites are often false positives
Warnings on Squarespace sites can have nothing to find: there are no server files or plugins for you to manage — the site is built from content and settings inside your account. When a vendor warns anyway, it is usually one of a few reputation-shaped causes:
- A young or newly connected custom domain. Fresh domains have no history, and reputation systems distrust the unknown.
- Shared or inherited reputation. Platform sites share hosting infrastructure and some signals, and heavy third-party scripts on your pages can read as risk to a scanner.
- A stale flag. Something real appeared months ago and was fixed, but the vendor's list still carries the verdict.
- An outright misclassification. Automated scoring makes mistakes, and a platform site gives a scanner very little to look at.
Confirm which vendor is showing the warning — the blocked page usually names it, and a free blocklist check shows which vendors flag the domain. Our scan looks at those outside vendors; it does not read anything inside your Squarespace account. For how vendors score domains and what they accept as evidence, see why antivirus flags clean websites.
One caveat: "probably a false positive" is not a diagnosis. If you found account or DNS changes earlier, finish the recovery first — a request sent before the cause is fixed is likely to be refused, or the flag to return.
Still flagged? Ask each vendor to re-check
If the flag lingers after you have recovered the account and the domain, unflagdomain.com offers removal requests for €49, once per domain; the pricing page has the rest. A correctly formatted removal request is sent to every flagging vendor that accepts one by email, within 48 hours of payment (in practice within the first hour). Vendors that only take a web form or manual review get a ready-to-paste request on the dashboard.
Keeping the account and domain safe
- Two-factor authentication on the account, with backup codes stored where you can find them. Each contributor turns it on in their own account, so make it a condition for anyone working on your site.
- Protect the owner email address. Whoever controls the email that owns the account controls the account. Give that mailbox a strong password and 2FA.
- Watch the domain. Check DNS records and nameservers occasionally, keep the domain lock on, and leave auto-renewal enabled so a lapsed registration cannot be grabbed.
- Review access on a schedule. Remove collaborators who no longer need it; every extra account is one more way in.
If a warning is showing right now, find out who is actually flagging you — a free blocklist check takes a minute and names the vendors. If the flag lingers after you have recovered the account and the domain, removing your website from blocklists is the next step.
Rarely through the site itself — the realistic attacks are account takeovers and DNS hijacks, like the July 2024 domain-hijacking incident. Whoever controls the account or the domain can change what visitors see without touching any site code.
Security-themed phishing aimed at platform owners is common, so treat any unexpected 'review' or 'verification' email as suspicious until proven otherwise. Never sign in through a link in an email; open Squarespace directly and check for real notifications there.
Reset your password from a clean device first, then turn on two-factor authentication. Next, sign in to your domain settings and review the DNS records and nameservers for anything you did not set, and finally contact Squarespace support to recover the account and lock the domain down.
Squarespace sites have no user-managed server, so there is often nothing malicious to find — and platform sites can get flagged by reputation heuristics without any real infection. Check which vendor is showing the warning and verify whether it is a false positive before disputing it.
Each vendor decides on its own schedule, and we found no published review time from these vendors, so we avoid promising dates. A correctly formatted removal request is sent to every flagging vendor that accepts one by email, within 48 hours of payment (in practice within the first hour).