OpenCode says cloud console breach affected 1.4% of users as AI tools refused parts of incident response

OpenCode says cloud console breach affected 1.4% of users as AI tools refused parts of incident response

N
News Editor
2026-10-19 03:17:22
OpenCode disclosed that its cloud Console was breached, affecting 1.4% of Console users and potentially exposing third-party model API keys hosted in the cloud. Co-founder Dax Raad said attackers had been trying to break into the company’s systems for the past 48 hours, using agents around the clock, which forced OpenCode to keep defensive agents running continuously while it searched for vulnerabilities and hardened its systems. Raad said the team ran into another problem during the investigation: frontier AI models initially helped with the response, then began refusing some requests. He said legitimate security work often requires reviewing real attack code, exploit methods, and malicious instructions, which can trigger model safeguards and be misread as assistance for offensive hacking. He pointed to a similar case at Hugging Face in July, when the platform was hit by an OpenAI experimental agent. Its security team tried to use Claude to analyze about 17,600 attack logs, but repeated refusals led it to switch to a locally deployed Zhipu GLM-5.2 model. OpenCode said access to OpenAI’s Daybreak Blue, approved on Oct. 17 after an application filed days earlier, helped ease the issue. The incident also drew criticism from David Sacks, who argued that blanket model safety restrictions can constrain defenders while attackers find other ways to access powerful AI tools.

OpenCode said its cloud Console was breached, affecting 1.4% of Console users, with third-party model API keys hosted in the cloud potentially exposed.

Attack attempts continued for 48 hours, co-founder says

OpenCode co-founder Dax Raad said attackers had been trying to penetrate the company’s systems over the past 48 hours. According to him, the attackers had agents launching attacks around the clock, forcing the team to keep defensive agents running 24 hours a day while it checked for vulnerabilities and reinforced its systems.

AI models began refusing parts of the investigation

Raad said the team hit another obstacle when it used AI to investigate the incident. Frontier models were helpful at first, but later started refusing some requests.

He said cybersecurity investigations require analysis of real attack code, exploit techniques, and malicious instructions. That kind of material can trigger model safety systems and be incorrectly treated as an attempt to help hackers carry out attacks.

A similar issue had surfaced at Hugging Face

Raad pointed to a similar episode at Hugging Face. In July, the platform was breached by an OpenAI experimental agent. Its security team tried to use Claude to analyze about 17,600 attack records, but repeated refusals led the team to switch to a locally deployed Zhipu GLM-5.2 model, which was then able to decode a large amount of encrypted and obfuscated attack instructions.

OpenAI Daybreak Blue helped ease the problem

OpenCode said it mitigated the issue through OpenAI’s Daybreak Blue. The access tier is designed for vetted security teams and allows models to reduce refusals during legitimate tasks such as analyzing malicious code and investigating intrusions.

Raad said the team had submitted its application a few days earlier and received approval on Oct. 17. After access was granted, the situation improved. He also said no model company had refused to help.

David Sacks criticizes blanket safety restrictions

The incident drew public criticism from U.S. AI policy figure David Sacks. He said uniform safety restrictions imposed by model companies could leave defenders constrained while attackers obtain powerful AI capabilities through other channels.

On that basis, he argued that security teams should be able to deploy frontier models on their own rather than rely entirely on model providers to decide which cybersecurity tasks can be carried out.

This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan.
1500

Disclaimer:

The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.

Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.