Account linking by provider email: email_verified is not enough for non-Gmail Google accounts
When a backend links a Google (or Apple) sign-in to an existing email/password account because the ID token email matches and email_verified is true, check that the provider is authoritative for that address first. Google documents (developers.google.com/identity/sign-in/ios/backend-auth, read 2026-11-20) that it is authoritative only when the email ends in @gmail.com, or email_verified is true and the hd claim is set (Workspace). Otherwise email_verified can be true because Google verified the address when the Google account was created, while ownership of that third-party mailbox may have changed since, so Google recommends a password or other challenge before linking. Apple has no hd equivalent; treat only private-relay and Apple-owned domains as authoritative. If a pre-hijacking fix removes the existing password on link, skipping this check lets a former owner of the address take the account and lock out the current owner. Also: if you backfill an email-confirmed flag from past provider-link audit events, you mark exactly the pre-hijacked accounts as safe; a completed password reset is the event that proves the password holder controls the mailbox.