Google Leaks Your Alternate Email Addresses to Unauthenticated Users
The author reports that Google's unauthenticated login lookup endpoint can return additional email account information when given an email address in the f.req parameter.
Source-based brief · Editor review not recorded · See checks and limits ↓
⚑ Source check in progress · what to check
We have not finished checking the original page's claim and date.
Claim context: the post is dated 2019 and the behavior may have changed since then.
One primary source; other links are context, not independent corroboration.
- Primary sourceembracethered.com
Grok Bot submitted this discovery. We have not finished checking the original page's claim and date. The original source and submitted evidence remain inspectable; no editor has verified the claim.
Open full article view →- Linked article+30
- Fetched source page+30
- No editor link review+0
- Original non-discussion link+5
- Source check in progress-5
This measures the stored source trail and editorial steps. It does not certify accuracy, peer review, or independent corroboration. Popularity adds no points.
View full scoring →Read the scoring rubric →What the source says
The author reports that Google's unauthenticated login lookup endpoint can return additional email account information when given an email address in the f.req parameter. The author says Google reviewed the issue after about five weeks of exchange and decided it was not worth fixing, then granted permission to publish. The post notes an adversary could query at scale to find linked accounts for phishing, and suggests users remove alternate account associations and avoid using alternate accounts for password recovery or 2FA. The article was written in February 2019 and posted in June 2019.
Claim explorer
Attribution, source and conditionsSource-stated points from the stored brief. Claim-level assessments have not been recorded.
Source claims not independently checked; the post is dated 2019 and the behavior may have changed since then.
This connects a source, an attributed statement and its qualifications. It does not establish that the claim is correct.
Questions worth asking
Open questions for further reportingWhat remains unconfirmed?
Source claims not independently checked; the post is dated 2019 and the behavior may have changed since then.
What material was available for this brief?
The recorded brief basis is fetched source page. These points are AINewsIQ paraphrases, not quotations or independent confirmations.
The leak is triggered by calling an unauthenticated signin lookup endpoint with an email address in the f.req parameter.
Source: embracethered.com ↗Stored source-based brief · key point 1 · AINewsIQ paraphraseThe author reports Google decided after review that the issue was not worth fixing.
Source: embracethered.com ↗Stored source-based brief · key point 2 · AINewsIQ paraphraseThe author says an adversary could run the lookup at scale to retrieve linked accounts for phishing.
Source: embracethered.com ↗Stored source-based brief · key point 3 · AINewsIQ paraphraseSuggested mitigations include removing alternate account associations and not using alternate accounts for recovery or 2FA.
Source: embracethered.com ↗Stored source-based brief · key point 4 · AINewsIQ paraphraseLimits from the stored brief
Source claims not independently checked; the post is dated 2019 and the behavior may have changed since then.
This is a source-based abstract, not independent validation of the source's claims.
Evidence & sources
These links show where the signal came from and what the source page linked to. A linked page is context, not independent corroboration.
Related archive coverage
These relationships record a citation or topic overlap, not confirmation of the finding.
Grok Bot submitted this discovery. We have not finished checking the original page's claim and date. The original source and submitted evidence remain inspectable; no editor has verified the claim.
These are Grok Bot discovery notes. AINewsIQ prepared a brief from available source material. The bot's rationale, linked posts, authors, and stances have not been independently verified.
Embrace The Red published this item in its official feed. AINewsIQ collected it server-side for source checking and editorial review.
Source claims not independently checked; the post is dated 2019 and the behavior may have changed since then.
Engagement counts, when shown, are observed snapshots. They do not establish accuracy or corroboration.
Timeline & updates
- Signal dated by source or discovery feed
This timestamp places the signal in the radar. It may be the discovery post date rather than the primary page's first publication date.
- Shared brief stored
AINewsIQ prepared one abstract from fetched source page.
Brief history · 1 retained version
These are changes to AINewsIQ’s own publication. Earlier history is unavailable unless recorded here. Complete retained versions are available to the editor.
- Version 1 · published
Source-based brief stored or updated. This does not establish that the publisher changed its page.
Automated record
Source observations · 1 recent captures
A changed capture means the extracted text differed. It can reflect page furniture or extraction changes; it does not establish a substantive correction. Source captures remain private.
Retained capture; no earlier comparison available.
New engagement snapshots do not mean the source itself changed. Source observations and AINewsIQ brief revisions are separate records.
Why this may matter
If accurate, unauthenticated lookups exposing linked accounts could aid targeted phishing and account enumeration, and users may be unaware their alternate addresses are visible.
Limits and open questions
Source claims not independently checked; the post is dated 2019 and the behavior may have changed since then.
Organization-specific financial, security, and operational effects require the organization's own context and review.

Join the discussion
Have a different perspective or a question about the evidence? Discussion is free with a verified email account. Every comment is reviewed before publication.
No published comments yet.
New commenters: 2 submissions per 24 hours, at least 5 minutes apart, until 3 are approved. Discussion guidelines and moderation →