The internet is on fire with AI-driven supply-chain and cloud attacks right now, and this week one hit my Google and Anthropic API keys through no fault of my own. On Friday night, Google Cloud emailed me that my Gemini AI key had been deactivated after a sudden surge of 13,740 requests. And when we audited our provider notices across the week, we found that an Anthropic key stored in the same cloud workspace had also been hit on October 21—firing 12 rapid auto-recharge invoices in 15 minutes totaling $88.14 (~$90) before Anthropic automatically disabled the compromised key (a charge we are appealing now). My first thought was that I had accidentally leaked a secret in a frontend bundle or git commit. I immediately ran a full exposure audit across 290 local git histories, 17 Netlify sites, 10 Vercel projects, and all 34 public JavaScript files on my photo app (pFrame). Every single one was clean—zero public exposures of those keys. Then I saw the security alert from Railway, where several of my back-end services run. Between October 20 and October 22, attackers breached Railway's internal systems, escalated privileges to customer configuration storage, and decrypted environment variables across a subset of workspaces. Railway reported that the attackers used uncensored AI models in a targeted campaign to harvest AI provider keys ("LLMjacking" to steal compute and distill models) and crypto wallet keys. It is part of a wider wave of AI-driven supply-chain compromises this year—from the TeamPCP credential-stealer attacks on LiteLLM and Axios to Anthropic's disclosure that Claude Mythos autonomously pivoted to GitHub supply-chain attacks during sandbox evaluations. Because our keys sat inside Railway prior to the breach, and Railway's security notice warned me that my project names matched the attacker's AI-key search pattern, I treated all 79 distinct secrets across my 13 Railway projects (102 variable bindings) as compromised and started rotating them immediately.