Unverified60% confidenceFactExact time
OpenCode has not yet disclosed how the attackers gained system access, how the keys were stored, or the full scope of the key misuse; the company only said the situation is still active.
2
Sources
60%
Confidence
Short-term (~14 days)
Relevance
10/19/2026
First Seen
Valid until: 11/2/2026
Sources
Related Entities
Related Claims
VerifiedOpenClaw carries security risks: because its built-in tools have extremely high permissions (capable of operating system files, reading browser information, and executing tasks online), any configured API Keys are highly susceptible to leakage if the machine is compromised.73% similarUnverifiedOpenCode disclosed a provider key leak incident on October 17, with about 1.4% of Console users affected, and key rotation has been initiated.72% similarVerifiedOnce an API Key is leaked, an attacker can make unlimited API calls from anywhere in the world as the key holder, and the server cannot distinguish legitimate calls from unauthorized ones.72% similarUnverifiedOpen-source AI coding tool OpenCode disclosed a security incident: a legacy system being decommissioned was accessed without authorization, about 1.4% of OpenCode Console users were affected, and third-party AI service API keys may have leaked.71% similarUnverifiedUnder a secure boot mechanism, even if an attacker modifies the firmware code, as long as the private key is not leaked, the modified firmware cannot pass signature verification.71% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1071628API
curl https://kongchang.com/api/v1/knowledge/claims/1071628MCP
get_claim(id=1071628)