Back to Feed
Threat IntelligenceOct 7, 2026

Hackers hijack Google domains after breaching ccTLD registries

Hackers compromised ccTLD registries, obtaining unauthorized HTTPS certificates for Google domains.

Attackers compromised third-party operators of ccTLD registries for Ghana, American Samoa, and Sierra Leone, allowing them to modify DNS records and obtain unauthorized HTTPS certificates for Google domains. While Google's systems were not directly breached, the attackers could impersonate legitimate brands and serve malicious content. Google has since blocked the unauthorized certificates in Chrome and is working with affected organizations and CAs.

AI summary of the linked source. Not reviewed by an editor. How this works

Vendor Watch

Run Google?

Get an email when a new story names Google, usually within the hour.

Free. Your list stays private and never appears in a subject line. One click stops it. How Vendor Watch worksPrivacy

The lesson from this incident

Full lesson

Attackers exploited weaknesses in third-party ccTLD registry operators to manipulate DNS records and fraudulently obtain HTTPS certificates for Google-owned domains — a classic supply chain attack where trust in a delegated third party becomes the attack surface. The root cause lies in insufficient security controls at these registries, which act as critical internet infrastructure but may not be held to the same security standards as the organizations whose domains they manage. This matters because even a well-secured organization like Google can have its domains impersonated through no direct fault of its own, undermining the foundational trust model of the web's certificate and DNS ecosystem. The incident highlights that certificate transparency logging and browser-level certificate blocking, while effective reactive measures, are no substitute for proactive security at every link in the DNS chain.

What helps against this

How we list vendors

Entities

Chrome (product)Google (vendor)