A coding-agent user's AI provider keys were stolen — and the attackers billed them.
AspireAI community · techcrunch.com
A coding-agent user's AI provider keys were stolen — and the attackers billed them.
OpenCode, the open-source tool competing with Claude Code and Cursor, said intruders broke into a legacy Console system overnight Oct 16. About 1.4% of Console users had stored OpenAI, Anthropic or Google keys; some bills ran into hundreds, a couple over $1,000. Anthropic and Google blocked exposed keys; OpenAI and OpenCode are issuing refunds.
Co-founder Dax Raad said attackers hit OpenCode nonstop for 48 hours, so the team ran AI agents around the clock until safety filters refused malicious code. OpenCode later got OpenAI's Daybreak Blue program, vetted models less likely to refuse defensive work, which Raad said moved the response.
Limit: OpenCode has not said how attackers got in, and "distillation attack" framing is unproven. Anyone who stored a key there should revoke it from the provider's own dashboard.
Read the story and explore more from the AspireAI community.
Two critical PHP remote code execution flaws — one found by GPT-5.6 Sol — were patched on October 21, 2026, and OpenAI published a disclosure framework alongside the fix. Fixed versions: PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Both allow unauthenticated remote code execution, and PHP's advisory says risk is highest for mod_php, where a demonstrated exploit triggers before any application code runs. The CVEs are distinct failure modes. CVE-2026-109618 (OOM corruption): out-of-memory handling can interrupt PHP while internal request data is only partially initialized, and request cleanup may then treat the invalid data as valid. CVE-2026-109619 (stale global state): request-owned internal state can survive after its backing memory is freed, and a later request served by the same worker may use that stale state. OpenAI states GPT-5.6 Sol identified the first flaw through its Patch the Planet initiative, and that Wiz independently discovered and reported both vulnerabilities. PHP's maintainers led the fixes and release, with Wiz, Cloudflare and OpenAI contributing research and coordination. Wiz's write-up adds that it used GPT-5.6 Sol and Gemini 4 Argon throughout, with Gemini 4 Argon contributing to finding the vulnerability and validating the patch. OpenAI describes the gap between discovery and public exploitation as a "Defender's Window," proposes a five-stage response framework, and committed $1 billion in subsidised Daybreak model access for organizations with limited security resources. Honest caveats: these are OpenAI's and Wiz's own characterizations, and OpenAI also notes the same capabilities help attackers build offensive tooling faster. PHP 8.1 and older no longer receive updates from the PHP project.