Leaked Claude API key from shut-down project quietly billed months later
- Source
- x.com
- Date
Interesting, I killed my OpenClaw VPS servers months ago But today I got a billing alert on its separate Claude account (claudeforopenclaw@), it didn't have auto reload on but I guess at some point it got hacked and the Claude key inside OpenClaw got exposed and then they waited for months before using it on Fable 5.1 I checked all my terminals and VPS sessions and none of them use API so it's interesting Anyway I nuked the Claude account, good I kept it on its own separate one

Context
The poster says he shut down the VPS servers running his OpenClaw-based project months ago, but the Claude API key tied to that dead project's own, separate billing account was still active, and he recently got a billing alert on that account.
According to his account, the key had no auto-reload enabled, but he believes it was exposed at some point and used much later by whoever obtained it, rather than immediately. He checked his own terminals and sessions and found no legitimate use that would explain the charges, then revoked the account. He frames keeping that key on its own dedicated billing account, separate from his other API usage, as what let him notice and contain the exposure instead of it hiding inside shared usage.
Checking sign-in…
Loading comments…




