PULSE the living trend engine
🤖 Open Intelligence Dossier available for AI agents & citation View Markdown (.md) →
▲ Peaking Technology

Attackers Hijack .gh, .sl, and .as Registries to Obtain Certificates for Google Domains

Attackers hijack country-code top-level domains to obtain unauthorized HTTPS certificates for Google, prompting direct response actions.

3sources
3articles
1velocity
+420%since first seen
1d agofirst detected

Velocity

How fast coverage is spreading — measured hourly from article rate × source diversity. How this works →

The brief

Recent technology reporting outlines a significant cybersecurity incident involving domain name system operations across multiple country-code top-level domains. The primary consequence of these registry compromises was the generation of unauthorized security certificates affecting major online properties. Media outlets have placed a strong emphasis on the scale of the digital infrastructure breach and the immediate reaction from major technology corporations. Forbes specifically reports that Google took prompt action to block the compromised Chrome security certificates following the domain attacks.

Techzine Global adds further context by explicitly confirming that hackers managed to acquire HTTPS certificates specifically targeting Google. This incident highlights ongoing vulnerabilities within global domain name system registries and the cascading trust issues that arise when country-code top-level domain infrastructure is compromised. Because modern web browsers rely on these certificates to establish secure, encrypted connections and verify website authenticity, unauthorized certificate acquisition represents a severe threat to web traffic integrity and user data security. As the situation continues to develop, ongoing coverage does not yet specify the full identity of the attackers or the complete list of all potentially impacted domains beyond Google.

Observers and stakeholders will be monitoring further technical disclosures from registry operators, security researchers, and browser vendors regarding the permanent revocation status of the affected certificates. Additional updates from the outlets currently tracking the story are expected to clarify whether other major technology entities or global websites experienced similar compromises stemming from the ccTLD hijacks.

Synthesized by PULSE from the headlines below under a strict no-invention contract. ✓ fact-checked: unsupported claims removed (71% supported) Updated 7h ago.

Quick answers

Which registries were hijacked in the attacks?

Coverage states that attackers hijacked the .gh, .sl, and .as registries.

How many unauthorized certificates were obtained?

According to CircleID, the DNS hijacks were linked to 32 unauthorized HTTPS certificates.

How did Google respond to the incident?

Forbes reports that Google acted to block Chrome security certificates following the domain attacks.

Coverage (3)

Topics

Related trends

\n \n \n \n \n \n \n