Back to today's topics

Verified · Sep 9, 2026

Independently verified

Anthropic warns that infostealers are draining Claude subscribers' tokens — and every receipt is public

3 sources

TechCrunch reported September 8: UK AI consultant Grant De Swardt's Claude Max 20x account — $200 per month — burned tokens while he wasn't working: 'In the clearest controlled interval, it increased from 45% to 55% while I performed no work', he told the outlet. Anthropic suspended the account, invalidated his sessions and server-side Claude Code tokens, and refunded £44.49 for the remaining time; per TechCrunch, its investigation found 'A compromised Claude session key was used to mint unauthorized Claude Code OAuth tokens' — and per De Swardt's account, the evidence was 'consistent either with credentials/session data being taken without my knowledge, or with the account having been connected to an outside service.' Anthropic's warning email to other users, as quoted by TechCrunch: 'We have recently become aware of a bad actor that is using common infostealer malware to steal Claude login sessions from people's computers, then using those login sessions to access Claude accounts and consume their usage.' When Anthropic saw suspicious activity it 'signed the users out, invalidated existing authorizations, issued some refunds, and warned them that they may have malware'; asked how users can identify misuse, 'Anthropic declined to comment.' AITopic independently read GitHub issue anthropics/claude-code #82506 via the API (filed July 30, 2026, closed): 'I haven't used Claude for three days, but my limits keep getting consumed automatically after every reset' — and a Claude Code collaborator replied that the CLI 'doesn't consume plan usage on its own while you aren't using it', pointing to official docs: plan limits are shared 'across every Claude surface on the same account (claude.ai, desktop/mobile apps, Cowork) and across all your devices — not just the machine you run Claude Code on.' TechCrunch adds that account support tracks total usage but not itemized usage.

Why now

The report landed yesterday (September 8), and affected users have already received Anthropic's warning emails — so Claude subscribers in your audience have the felt experience without the explanation. The official docs hand creators a checkable thread (allowances shared across surfaces and devices), and Anthropic's decline to comment on identifying misuse, plus the absence of itemized usage tooling, leaves an information gap creators can fill without inventing anything: walk the audience through the quoted email, the public GitHub issue, and the docs — and stop where the sources stop.

Why it is worth publishing

Every piece of evidence on this card is one click from verifiable: TechCrunch's full text, the GitHub issue's API-readable record with its collaborator reply and timestamps, and Anthropic's own docs page. It is also a working lesson in restraint — 'users report' and 'Anthropic says' stay separate, and the theft explanation and the shared-limits explanation stand side by side — for an audience that runs its business on Claude, it is about their own invoices.

Evidence basis

TechCrunch full read on 2026-09-09 (posted 2:10 PM PDT September 8, 2026, Julie Bort) + GitHub issue #82506 read directly via the GitHub API (filed 2026-07-30T07:55:17Z; collaborator reply by bcherny 2026-08-17) + Anthropic's docs at code.claude.com/docs/en/costs read. The Reddit thread was unreachable to AITopic (connection reset); Reddit-user quotes stay at the TechCrunch relay layer.

Anthropic says a bad actor is stealing Claude login sessions — and silently burning subscribers' usage.

Angle

Tell it by evidence layer: what Anthropic's warning email says (as quoted by TechCrunch), what the company did in the individual case (suspend, invalidate, refund), what the community reports (the GitHub issue text and the collaborator's reply), and how the official docs explain the benign version of 'usage climbed while I wasn't working.' Anthropic's declined-to-comment line is your boundary — don't write the checklist the company wouldn't.

Format

Short talking-head video

Demo idea

Three-step screen recording: open your own usage page and read this week's burn; pull up the official docs passage on allowances shared across claude.ai, desktop/mobile, Cowork, and all devices; open GitHub issue #82506 and read the collaborator's reply — then say plainly: itemized usage doesn't exist, so contact support if your numbers look wrong.

Platform notes

Keep the two-layer verbs apart: 'users report' for the episodes, 'Anthropic says' for the mechanism. The infostealer malware sits on users' computers per the email's own wording — nothing on this card shows an Anthropic-side breach, so never say 'Claude was hacked.' The 45%→55% interval is De Swardt's own measurement; the £44.49 refund and $200 monthly fee come via TechCrunch — keep those layers when quoting. Shared limits are the docs' explanation for one class of unexplained usage and stand next to the stolen-session explanation — don't pick a winner. Never state a count of affected accounts.

Usable claims

  • Anthropic has warned some Claude users that their tokens were being stolen. TechCrunch quotes the company's email: 'We have recently become aware of a bad actor that is using common infostealer malware to steal Claude login sessions from people's computers, then using those login sessions to access Claude accounts and consume their usage.' Per TechCrunch, when Anthropic saw suspicious activity 'it signed the users out, invalidated existing authorizations, issued some refunds, and warned them that they may have malware', and the company said 'the malware didn't come from using Claude itself.' Asked how users can identify misuse, 'Anthropic declined to comment.'
  • TechCrunch profiles Grant De Swardt, an independent AI consultant in East Sussex, U.K., whose Claude Max 20x account — a $200-per-month subscription — burned tokens while he was not working: 'In the clearest controlled interval, it increased from 45% to 55% while I performed no work', he told TechCrunch (adding that scheduled Cowork tasks were paused or completed and cloud execution disabled at the time). Anthropic agreed something was off, suspended the account, invalidated his sessions and server-side Claude Code tokens, and issued a partial refund of £44.49 for the remaining time. Per TechCrunch, Anthropic's investigation found the culprit: 'A compromised Claude session key was used to mint unauthorized Claude Code OAuth tokens.' Per De Swardt's account, the company said the evidence was 'consistent either with credentials/session data being taken without my knowledge, or with the account having been connected to an outside service.' His account was reinstated after about two weeks; he cancelled the subscription afterward. TechCrunch reports account support tracks total usage but not itemized usage, so theft 'could have gone on for months undetected.'
  • Other users have reported similar episodes. Per TechCrunch: one Reddit user claimed their usage 'shot from 0% to 100% automatically without me even touching it'; another 'saw usage go from 0 to 49% in 12 minutes' after only a couple of prompts and a web search; and a third account 'burned through its max tokens every day for three days' without use — that user filed GitHub issue anthropics/claude-code #82506, which AITopic read via the GitHub API: 'I haven't used Claude for three days, but my limits keep getting consumed automatically after every reset' (filed July 30, 2026; closed; 31 comments). A Claude Code collaborator replied on the issue that the CLI 'doesn't consume plan usage on its own while you aren't using it', pointing to Anthropic's docs: 'Plan limits are shared across every Claude surface on the same account (claude.ai, desktop/mobile apps, Cowork) and across all your devices — not just the machine you run Claude Code on.'
  • Anthropic's own documentation explains one reason usage can climb without visible local activity: a session or weekly limit is 'a seat-based usage window on a subscription plan, shared across all models', and on Teams and Enterprise plans each member's allowance 'resets on a rolling five-hour window and a weekly window' and 'is shared with Claude chat and Cowork.' The docs page — code.claude.com/docs/en/costs, linked from the collaborator's reply on issue #82506 — was read by AITopic this run. It is developer-facing and does not document itemized usage or any tool for attributing usage to a specific surface.

Evidence pipeline

Breakdown

Users' Claude tokens were consumed while they weren't working; Anthropic's warning email locates the mechanism in infostealer malware on users' computers (as quoted by TechCrunch), and the company's handling in one documented case was suspend, invalidate, refund. This breakdown lays the evidence out by layer: the warning email (which exists here only as TechCrunch's quote), GitHub issue #82506's API-readable record and the collaborator's reply (the CLI doesn't consume on its own; allowances are shared across surfaces), and the official docs' shared-allowance passage — plus the gap Anthropic's declined-to-comment leaves: nobody can hand you a 'was I hit' checklist, and itemized usage appears in no source on this card.

Risks

  • Keep the two-layer verbs: 'users report' for the episodes, 'Anthropic says' for the mechanism — and never total the victims.
  • Stick to sourced actions: check your usage, contact support the way affected users did, and read Anthropic's docs on shared plan limits — present infostealer hygiene as general security hygiene, not as an Anthropic-endorsed checklist.
  • Present both explanations with their holders (TechCrunch reports Anthropic's finding; De Swardt relays the two possible explanations; the docs and the collaborator's reply carry the shared-allowance reading), and note the CLI cannot see account-side usage.

Demo ideas

  • Two-explanations card: left, TechCrunch's report of Anthropic's finding (a compromised session key minting unauthorized OAuth tokens); right, the official docs' shared-allowance passage plus De Swardt's relayed alternative (the account connected to an outside service) — with neither column marked as the answer
  • Evidence walk carousel: the warning email quote (labeled 'as quoted by TechCrunch') → the GitHub issue text and collaborator reply (labeled 'readable via API') → the official docs' shared-limits passage (labeled 'official docs') — one clickable source per slide