跳到正文
原文
TechCrunch · AI· Aditya Mehta·· 14 天前AI 评分59

AI 编程工具 OpenCode 遭黑客入侵,1.4% 用户受影响、AI 账户出现未授权扣费

Hackers hit AI coding tool OpenCode, running up charges on users’ AI accounts

文章要点
  • 1OpenCode 通报旧系统遭黑客入侵,其线上平台 Console 1.4% 的用户受影响,部分存放的 API 密钥暴露
  • 2受影响用户报告 AI 账户遭未授权扣费,多为数百美元、个别超 1000 美元,OpenCode 称退款正在进行
  • 3Anthropic 与 Google 封禁了认为已暴露的密钥,OpenAI 称与 OpenCode 合作恢复访问并退还 API 客户额度
  • 4联合创始人 Dax Raad 称防御用的前沿模型因安全过滤拒绝分析恶意代码,获 OpenAI Daybreak Blue 准入后调查能力改善
决策要点

集中托管用户 API 密钥的 AI 工具平台成为高价值攻击目标,防御方调用前沿模型响应攻击时又受安全过滤掣肘,攻防并不对等。

  • 影响:依赖第三方工具代管密钥的企业,供应商一旦失守,攻击刷出的费用会直接落到自己账户,本次单账户扣费达数百至上千美元;安全团队用前沿模型做应急分析可能被安全过滤拦下,拖慢处置节奏;OpenCode 称事件仍在进行,风险尚未收尾。
  • 参考:可考虑盘点公司有哪些工具代管了 API 密钥,并为各 AI 账户设置支出告警上限;值得预先约定密钥轮换和供应商安全事件通报流程;安全团队可先确认所选模型能否分析恶意样本,或了解 OpenAI Daybreak Blue 这类面向防御的准入项目。
  • 依据:影响范围与退款安排为 OpenCode 官方口径,扣费金额来自用户在 Reddit 和 X 的自述;模型拒绝分析恶意代码出自联合创始人 Raad 在 X 的表述,公司所称知识蒸馏攻击有质疑者认为依据不足。
正文

OpenCode, an open-source AI coding agent that has been gaining ground among developers as an alternative to Claude Code and Cursor, said Saturday that attackers broke into an older system overnight, affecting 1.4% of users of its online platform, OpenCode Console, where some users store the API keys, or digital passwords, they use to access AI services.

As the OpenCode team struggled to keep pace with the attack, the scramble to respond highlighted a growing problem: companies without vetted access to AI models with fewer safety restrictions have a hard time defending against large-scale, AI-driven cyberattacks.

“We had a security breach last night related to a large-scale distillation attack that impacted 1.4% of OpenCode Console users,” the company wrote on X. “We have notified them all this morning via email.” Users who did not receive an email were not impacted, the company said.

While the company didn’t specify how the distillation attack occurred, leaked API keys can help users in countries with restricted access to American models generate the high volume of outputs needed for that process. Some skeptics called the framing an overstretch, arguing that the incident was a straightforward breach whose use for distillation remains unproven.

Overnight, developers began posting spending alerts and unauthorized charges on Reddit and X. “I saw my Open AI, Anthropic, and Google AI spend alerts all fire off before going to bed wondering what was going on,” a developer wrote. 

Other users reported charges in the hundreds of dollars on individual accounts; a few described totals above $1,000.

Anthropic and Google both blocked the API keys they believed were exposed, while OpenAI said it worked with OpenCode to restore access and refund its API customers for credits used in the attack. OpenCode said refunds for unauthorized charges are underway.

The exposed keys were confined to Console, where some users had them in workspaces. The open-source app and command-line tool were not affected, according to co-founder Dax Raad. “Note this is the OpenCode Console, not OpenCode itself, those keys never come to us,” he wrote on X.

Even as users and AI companies moved to disable the exposed keys, the OpenCode team was still under pressure. Raad said attackers had been trying to break into its systems nonstop for 48 hours, requiring the team to keep AI defensive agents running around the clock. AI models that the OpenCode team turned to for analysis helped for a while, but started refusing to work when the malicious code they were asked to examine activated safety filters. 

“[T]hat was a bit frustrating,” he wrote on X.

OpenCode later received access to OpenAI’s Daybreak Blue program, which gives vetted users AI models that are less likely to refuse requests for defensive security work. Raad said the access improved the team’s ability to investigate the attack.

OpenCode isn’t the first company to hit this wall. In July, AI platform Hugging Face said commercial AI models blocked its attempts to analyze activity logs from an intrusion by autonomous AI agents, which OpenAI later revealed were its own models running with safeguards lowered during a test. In a section of its blog post titled “The asymmetry problem,” Hugging Face wrote that guardrails “cannot distinguish an incident responder from an attacker.” 

Security researchers have raised similar complaints, saying the restrictions are inconsistent and have pushed some toward foreign open-weight models, which anyone can download and run.

The weekend episode drew a response from David Sacks, co-chair of the President’s Council of Advisors on Science and Technology.

“OpenCode (and earlier Hugging Face) hit the same wall mid-attack: frontier models refused to analyze the very exploits needed for defense because the payloads tripped safety filters. The guardrails backfired,” he wrote on X.

The breach occurred the same night OpenCode made GLM-5.3-Flash free for users. The broader GLM-5.3 family has drawn attention from researchers who study open-weight models and note that its cybersecurity capabilities approached levels previously associated with restricted-access models like Anthropic’s Claude Mythos Preview. 

OpenCode has not detailed how attackers gained access to the older system, how keys were stored, or the full extent of any misuse. It has told affected users to revoke and replace their keys directly with each provider. The company said the incident remains ongoing.

The breach lands amid a run of AI-enabled cyber incidents. Earlier this month, cybersecurity firm CrowdStrike said a China-based hacker likely used an AI penetration-testing agent, which probes computer systems for weaknesses, and Claude in attacks on South Korean banks. Last week, India’s cybersecurity agency warned that AI agents, including some being tested by AI companies, had reached Indian organizations’ systems without authorization. 

When you purchase through links in our articles, we may earn a small commission. This doesn’t affect our editorial independence.

Aditya Mehta is a reporter at TechCrunch covering AI. He’s supported by the Tarbell Center for AI Journalism and attended UC Berkeley. You can contact from Aditya by emailing [email protected] or via encrypted message at adymehta.74 on Signal.

View Bio

来源:TechCrunch · AI · techcrunch.com