GitHub issue #82074 in anthropics/claude-code, opened 2026-07-28 by uningeniero, records a report that the official Claude for Chrome extension can remain authenticated after Log out of all devices while its OAuth grant is not shown in the Claude Code token list or the normal active-session inventory, that a separate user independently reproduced the sequence in which the web session, Claude Code, and Windows and Android apps were logged out while Claude for Chrome remained authenticated and usable, and that Anthropic confirmed through HackerOne that Claude for Chrome uses a separate OAuth authorization and that the revocation gap was already known internally before this report. The report itself states the evidence does not yet prove a stolen token caused the unauthorized usage in the authors account, and attribution remains a hypothesis. The issue was closed 2026-09-07 by github-actions[bot] for inactivity, not as a fix; no fix confirmation appears in the thread.
Verbatim Excerpts from Cited Records
“This issue is an important correction and extension of my original report. The evidence does **not yet prove that a stolen Claude Code token caused the unauthorized usage**. A stronger credential hypothesis has now emerged: the official **Claude for Chrome** extension can remain authenticated after **Log out of all devices**, while its OAuth grant is not shown in the Claude Code token list or the normal active-session inventory.”
·
anthropics/claude-code (issue 82074 opening body, What is Wrong section, Summary subsection)
·
2026-07-28T19:02:16Z
·GitHub Issue ↗
“This creates a containment gap: a user can change passwords, globally log out, revoke every visible Claude Code authorization, remove connectors and delete visible sessions, yet an extension OAuth grant may remain valid and invisible.”
·
anthropics/claude-code (issue 82074 opening body, What is Wrong section, Summary subsection)
·
2026-07-28T19:02:16Z
·GitHub Issue ↗
“1. The Claude web session was logged out. 2. Claude Code required authentication again. 3. Windows and Android Claude apps were logged out. 4. **Claude for Chrome remained authenticated and usable.**”
·
anthropics/claude-code (issue 82074 opening body, Independently reproduced behavior section)
·
2026-07-28T19:02:16Z
·GitHub Issue ↗
“Anthropic has now confirmed through HackerOne that Claude for Chrome uses a separate OAuth authorization and that the gap in revocation and account session-control coverage for this authorization was already known internally before this report.”
·
anthropics/claude-code (issue 82074 opening body, Vendor confirmation section)
·
2026-07-28T19:02:16Z
·GitHub Issue ↗
Counter-record: Issue closed 2026-09-07 by github-actions[bot] for inactivity; it was not closed as fixed and no fix confirmation appears in the surveyed thread. lankhaar (2026-07-29) corroborated with a similar experience and akshayramdass (2026-08-03 to 2026-08-04) reported a related phantom-usage incident while stressing attribution requires the Anthropic request ledger, while hakonhagland (2026-08-05) narrowed the report by showing CLI setup-token revocation does work on the CLI surface. The author edited the opening body on 2026-07-30 to frame the extension as the likely cause and submitted the extension-specific evidence privately via HackerOne report 3899016; the opening body states the HackerOne report was closed as a duplicate of an internal issue. API returned 16 comments; all 16 were read. The claim documents only the original report, not a verified current state.
Falsification probe: If issue 82074 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author posts a retraction of the report, this claim drops to Withdrawn.
Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by
scripts/verify_claim_verbatim.py.