Detailed Analysis
A user posting to r/Anthropic reported a sudden and unauthorized consumption of 10 million tokens via Opus 4.8 on their API key, resulting in a complete drain of their account credits. The charges appeared in rapid succession — each new API call initiating immediately after the prior one concluded — suggesting an automated or programmatic process was responsible. The user explicitly ruled out the most common explanations: the API key was not leaked, no Opus model had been deliberately invoked in their codebase, and the account in question was not linked to Claude Code, which is a separate tool that can autonomously generate API calls. One detail from an included screenshot showed unusual token usage patterns that the user described as atypical relative to their normal workload.
A potentially significant financial detail emerges alongside the unauthorized usage: the user noted that a recent account top-up had failed to charge their card, as the card had been blocked for internet purchases while still set as the default payment method. This raises the possibility that Anthropic's billing system had an outstanding balance on the account, and that the system may have attempted to resolve or reconcile that discrepancy in an unconventional way. While no official confirmation of this theory exists in the post, the temporal coincidence between the failed payment and the anomalous usage is notable enough that the user specifically flagged it as a possible cause.
The incident highlights a broader vulnerability inherent to prepaid credit-based API systems: when billing irregularities arise — whether due to failed payments, card blocks, or system-level reconciliation processes — the mechanisms by which the platform responds are not always transparent to end users. If Anthropic's infrastructure did attempt to offset an unpaid balance by drawing against existing credits through automated calls, that behavior would represent a serious transparency and consent failure. Conversely, if the API key was compromised through a vector the user was unaware of (such as a dependency, environment variable leak, or a third-party integration), that would point to a security issue outside Anthropic's direct control.
More broadly, the episode reflects growing concerns within developer communities about the financial exposure inherent in large language model API usage. Unlike traditional SaaS billing, token-based consumption can spike catastrophically within minutes, and the asymmetry between how quickly credits can be depleted versus how quickly support can respond creates significant risk for developers. Anthropic, like OpenAI and other major API providers, does offer usage limits and alerts, but these tools are optional and their configuration is left to the user. Incidents like this one reinforce calls for mandatory spending caps, real-time anomaly detection, and automatic account freezing when usage deviates dramatically from established patterns — protections that would reduce the blast radius of both security breaches and billing system errors.
Read original article →