Summaries
Short AI and tech summaries with source links, signal scores, and why each update matters for builders, founders, and Malaysian tech workers.
Showing 1-2 of 2 results
| Date | Provider | Score | Summary |
|---|---|---|---|
| 02 Sep 2026, 4:45 AM | The Register | 8.5 | Attacker stole a METR API key, used $600K worth of credits, and no one noticed for weeks
METR disclosed that in March 2026, an attacker found a researcher's publicly accessible EC2 instance running a 'vibe-coded app' with a fail-open auth bug, prompted an agent to reveal its API key, and spent three weeks consuming ~$600K in model credits. The attacker likely discovered the instance by scanning certificate transparency lists for recently-registered sites with LLM/agent-related keywords. METR also disclosed a May 2026 incident involving systematic probing of its public infrastructure. Why: If you are vibe-coding or rapidly prototyping AI agent apps on public cloud instances, attackers are actively scanning certificate transparency logs for sites with LLM/agent keywords to harvest exposed API keys. You need to ensure your auth doesn't fail-open, never let agents handle raw API keys in prompt-accessible contexts, and set hard spending alerts on your model provider accounts — METR's $600K went unnoticed for three weeks. |
| 01 Sep 2026, 5:05 PM | The Hacker News | 8.5 | Attackers Steal METR API Key and Consume AI Credits Worth About $600,000
METR, a non-profit that evaluates frontier AI models for agentic tasks, disclosed two security incidents. In March 2026, attackers found a researcher's personal EC2 instance running a 'vibe-coded' agent orchestration dashboard via certificate transparency logs, exploited a fail-open auth vulnerability that silently disabled Google authentication, then prompted the agent directly to reveal its model provider API key—consuming approximately $600,000 in AI inference credits over three weeks. In May 2026, attackers separately probed METR's public infrastructure but failed to access internal data. Why: If you are vibe-coding or rapidly prototyping agent dashboards with LLM API keys, you need to assume attackers are actively scanning certificate transparency logs for sites with LLM/agent keywords and will prompt your exposed agent to dump its API key. Rotate and restrict API keys, never rely solely on Google auth without a fail-closed fallback, and set spending alerts on any inference account. The $600,000 bill was only absorbed because the provider gave credits for free—you would not be so lucky. |