AINewsIQ by Triuna Labs
Menu
SOURCE-LINKED SIGNAL / ARTICLE / SECURITY

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.

READ THE ORIGINAL SOURCEOpen original sourceembracethered.com UTC

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.

Recorded links

One primary source; other links are context, not independent corroboration.

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 →
How this score was derived
  • 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 conditions

Source-stated points from the stored brief. Claim-level assessments have not been recorded.

The leak is triggered by calling an unauthenticated signin lookup endpoint with an email address in the f.req…
Source assertionNot independently checked
Primary sourceembracethered.comInspect source ↗
Attributed toClaimant not recorded per pointSource assertion
Conditions / limitsClaim-specific conditions not recorded. Read the source and limits below.

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 reporting
What 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.

Limits 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.

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.

Checking sign-in…

New commenters: 2 submissions per 24 hours, at least 5 minutes apart, until 3 are approved. Discussion guidelines and moderation →