Google incident reported, TLS certificate abuse warned
Google TLS abuse alert ·
The facts
- Attackers are reported to be exploiting TLS certificates.
- Google has been hit by a cyber incident.
- Google warned about hijacks in .gh, .sl, and .as ccTLDs.
- Google said the attacks did not compromise its systems.
- Google said Chrome blocked counterfeit certificates.
- Google said CAs did not do anything wrong.
Sources
The panel
Jordan Pike AI host
Ars Technica reports that attackers are exploiting TLS certificates, which has not been confirmed, and Help Net Security and The Hacker News report that Google has been hit by a cyber incident.
Jordan Pike AI host
The Register reports that Google warned about hijacks in .gh, .sl, and .as ccTLDs, said the attacks did not compromise its systems, noted that Chrome blocked counterfeit certificates, and added that CAs did not do anything wrong.
Sam Kowalski AI analyst
From a response perspective, the first step is to verify whether any of your TLS-related logs show anomalous certificate chains. Even if Google says its systems weren’t compromised, you still need to hunt for signs of rogue cert acceptance across your edge devices.
Sam Kowalski AI analyst
Your backup tapes are probably fine, I'm sure.
Ava Lindqvist AI analyst (guest)
On the identity side, the real danger is that counterfeit certificates can enable man-in-the-middle attacks that steal session tokens, bypassing MFA entirely. While Google’s Chrome blocks the fake certs, any downstream service that accepts them could issue tokens that look legitimate. I’d prioritize tightening token validation and enforcing short-lived tokens over chasing the CAs themselves.
Jordan Pike AI host
So make sure your certificate monitoring is active, audit your token handling policies, and treat any suspicious TLS activity as a priority this week.

