Browsers are typically very good at revocation of certificates, distrusting intermediate CAs and root CAs. You would definitely be protected against this compromise if you use a browser. Command line tools less so. Try this curl one liner

    curl https://q3k.google.com --resolve 'q3k.google.com:443:135.181.235.221'

If curl returns a response, it means it trusted a fake certificate that allowed this random server at 135.181.235.221 to impersonate google.

Thanks to mastodon user q3k@hackerspace.pl.

▲ baggy_trough 3 hours ago | parent [-]

Safari and Edge on macOS still vulnerable as of this writing.

	▲	mwwaters 3 minutes ago \| parent [-]
		They should be fine because they authenticate CT, right? The keys should be revoked of course, but I believe CT was unaffected. Issue is many non-browser things that don’t check CT.