Attackers hijack three ccTLD registries, obtain Google certificates
First coverage.
Attackers compromised the .gh, .sl, and .as registries, altered DNS, and obtained unauthorized HTTPS certificates for Google and other organizations.
Google's Chrome Secure Web and Networking team said on October 6, 2026, that attackers compromised third-party operators of the Ghana (.gh), Sierra Leone (.sl), and American Samoa (.as) registries and changed authoritative DNS records. That control let them pass domain validation and obtain unauthorized HTTPS certificates for Google and YouTube domains and other organizations; Google said its systems were not breached, encryption was not broken, and the issuing certificate authorities did not act improperly. The Hacker News, citing Certificate Transparency logs, reported 12 domain-validated certificates—11 from Let's Encrypt and one from ZeroSSL—logged between September 22 and 27 for names including google.com.gh, google.sl, and google.as. Chrome blocked identified certificates through CRLSets, the CAs revoked them, and Google later blocked additional certificates for other brands, while warning that some domains may have been missed and that Chrome measures do not reliably protect non-Chrome users. Sources disagree on misuse: BleepingComputer said affected domains were pointed at attacker infrastructure, whereas The Hacker News and GBHackers said Google did not confirm the certificates were used to intercept traffic and did not name the attackers. Google urged owners of names under those suffixes to monitor Certificate Transparency logs and publish restrictive CAA records, including ACME account bindings, while reports noted CAA cannot prevent issuance during an active DNS hijack.
- Attackers compromised third-party operators of the .gh (Ghana), .sl (Sierra Leone), and .as (American Samoa) ccTLD registries and changed authoritative DNS records.
- Google's Chrome team disclosed the incident on October 6, 2026; Google said its systems were not breached, encryption was not broken, and the issuing certificate authorities were not at fault.
- The Hacker News, citing Certificate Transparency logs, reported 12 domain-validated certificates—11 from Let's Encrypt and one from ZeroSSL—logged September 22–27 for names including google.com.gh, google.sl, and google.as; the CAs revoked…
- Chrome blocked identified certificates through CRLSets; Google warned the review may have missed domains and that Chrome blocks do not reliably protect non-Chrome users.
- Other unnamed organizations were also targeted, and Google later blocked additional suspicious certificates after CT logs showed more brands.
- The Hacker News and GBHackers said Google did not confirm the certificates were used to intercept traffic and did not name the attackers; BleepingComputer reported affected domains were pointed at attacker infrastructure.
- Google urged owners to monitor Certificate Transparency logs and publish restrictive CAA records, including ACME account bindings; reports said CAA cannot stop issuance during an active DNS hijack.
- Vendors
- GoogleLet's EncryptZeroSSL
- Victims
- Organizations
- GoogleLet's EncryptZeroSSLGoogle Trust Services
- Countries
- GhanaSierra LeoneAmerican Samoa
Coverage
oldest first · one row per article · UTCHackers hijack three country-code domain registries, obtain HTTPS certificates for Google domains
Attackers hijacked Ghana, Sierra Leone, and American Samoa domain registries and obtained HTTPS certificates for Google domains.
Hackers Hijack .gh, .sl and .as Registry to Obtain Unauthorized HTTPS Certificates
Attackers hijacked .gh, .sl, and .as registries to obtain unauthorized TLS certificates for Google and others.
Attackers Hijack .gh, .sl, and .as Registries to Obtain Certificates for Google Domains
Attackers hijacked the .gh, .sl, and .as registries and obtained later-revoked HTTPS certificates for Google and YouTube domains.
Hackers hijack Google domains after breaching ccTLD registries
Attackers breached .gh, .sl, and .as operators, hijacked DNS, and obtained TLS certificates for Google and others.
Attackers Hijack .gh, .sl, and .as Domains to Obtain Unauthorized SSL Certificates
Attackers hijacked .gh, .sl, and .as DNS to obtain unauthorized TLS certificates for Google and other organizations.