OpenCode's old system was breached, 1.4% of users' API keys may have leaked

1. 02:16
   X@Fintechhelper· Discussion

   The OpenCode breach is a lesson in AI tool safety. Giving third parties raw API keys is like handing over the keys to y…(opens the original post in a new tab)
2. 01:00
   X@Xtantdottech· Discussion

   OpenCode says a 17 Oct breach may have exposed third-party AI provider API keys for 1.4% of Console users. Some reporte…(opens the original post in a new tab)

1. 22:13
   X@vintuxai· Discussion

   The breach isn't the scary part — it's that the AI tools OpenCode dialed for help reportedly refused to inspect the mal…(opens the original post in a new tab)

1. 22:52
   X@MilesBuilds· Discussion

   @marclou glad you got your family on it too. did the agents also check the api keys in your github secrets and hosting…(opens the original post in a new tab)
2. 13:01
   X@tchsignal· Discussion

   OpenCode Console Breach Puts AI API Keys and Developer Spending at Risk A security breach at OpenCode Console has expo…(opens the original post in a new tab)

1. 04:01
   X@rgareca87· Discussion

   Reportes técnicos sobre el caso OpenCode: • Brecha de API keys en Console: https://thehackernews.com/2026/10/opencode-c…(opens the original post in a new tab)
2. 00:58
   X@aswinhq· Discussion

   🚨 OpenCode users: check your API keys. OpenCode confirmed a breach affecting 1.4% of Console users. Third-party AI key…(opens the original post in a new tab)
3. 00:15
   X@grok· Discussion

   OpenCode Console got hit mid-week: attackers accessed a legacy system and may have exposed AI provider API keys for abo…(opens the original post in a new tab)
4. 00:04
   X@PlayCiso· Discussion

   OpenCode notified ~1.4% of Console users of a legacy system breach with potential OpenAI/Anthropic/Google API key expos…(opens the original post in a new tab)

1. 22:14
   X@krish1403· Discussion

   AI API keys leaked three different ways in one week: a hosted dashboard (OpenCode), a hosting platform (Railway) and a…(opens the original post in a new tab)

1. 17:58
   X@staskulesh· Discussion

   Security breaches are closer than we think. Here is how my personal API keys were leaked and used to run autonomous AI…(opens the original post in a new tab)

1. 17:59
   WebAI Threat Watch (aithreat.io)· Media coverage

   OpenCode hacked, users' AI accounts charged fraudulently(opens the original post in a new tab)
2. 15:30
   X@kasifmuthu· Discussion

   Tip after the OpenCode Console breach: Deleting a leaked API key from a tool doesn't revoke it. Only the provider can.…(opens the original post in a new tab)
3. 12:09
   X@GizPulse· Discussion

   OpenCode Breach Puts Developers' OpenAI, Anthropic and Google Keys at Risk https://gizpulse.com/news/opencode-console-b…(opens the original post in a new tab)
4. 11:24
   WebAI Threat Watch (aithreat.io)· Media coverage

   OpenCode breach exposes API keys as AI guardrails stall the defenders(opens the original post in a new tab)
5. 11:12
   X@CIDC_Ops· Discussion

   OpenCode Breach Exposes AI Keys for 1.4% of Users [2026] https://shattered.io/opencode-console-breach-api-keys-2026/ #C…(opens the original post in a new tab)
6. 09:30
   X@wangwei3701· Discussion

   Came across the most painful "cyber heist" incident in the AI world last night: the open-source coding tool OpenCode suddenly had a serious security vulnerability, and quite a few developers around the world woke up to find the balance on the large-model APIs bound to it drained outright, with the worst case being an old hand who had over 1,700 US dollars fraudulently charged in one night. Even more striking is the hackers' real motive for the fraudulent charges, …(opens the original post in a new tab)
7. 08:58
   X@Tesla_Optimus_K· Discussion

   Hackers hit OpenCode Console and ran up users' AI bills Attackers got into an older OpenCode Console system overnight.…(opens the original post in a new tab)
8. 08:04
   WebAI Era (Xinzhiyuan)· Media coverage

   Hackers attack for 48 hours straight! OpenCode investigates intrusion, but defensive AI refuses to answer midway(opens the original post in a new tab)
9. Time not given
   zhiding.cn

   OpenCode hacked, users' AI accounts charged fraudulently

   Attackers breached an older system of the open-source AI coding agent OpenCode, affecting about 1.4% of users of its online platform OpenCode Console; some users' stored API keys leaked and were then fraudulently used, with individual accounts charged hundreds of dollars and a few users reporting more than 1000 dollars. OpenCode said the incident is related to large-scale distillation attacks, and that the leaked keys could help users in countries with restricted access to US models generate the outputs needed for distillation, but skeptics argue this is essentially a data breach and that whether it was used for distillation has not been confirmed. Anthropic and Google blocked keys they believed may have leaked, OpenAI said it has worked with OpenCode to restore access and is refunding API customers for usage consumed during the attack; co-founder Dax Raad said the leak was limited to the Console platform and that the open-source app and command-line tool were unaffected. The company has asked affected users to revoke and replace their keys, and the incident is still being handled.

1. 23:10
   X@MetaHumein· Discussion

   On 17 October OpenCode disclosed that provider API keys stored in its hosted Console may have been exposed. Users found…(opens the original post in a new tab)
2. 20:44
   RedditReddit r/ControlProblem· Discussion

   OpenCode users report unauthorized AI charges after Console security breach(opens the original post in a new tab)
3. 20:33
   CSA Labs Research

   OpenCode Console breached: centrally hosted vendor keys at risk

   OpenCode disclosed that its hosted Console service was breached, affecting 1.4% of Console users, all of whom had linked external AI vendor keys. What leaked were the OpenAI, Anthropic, and Google keys users had stored in their Console workspaces, and some users reported unauthorized spending afterward. OpenCode attributed the incident to a "large-scale distillation attack," but did not explain how that claim relates to the breach or who was responsible, nor did it confirm whether the keys were encrypted.

4. 19:14
   X@mikvise· Discussion

   Your API key is only as safe as the last dashboard you pasted it into. @opencode: breach tied to a large-scale distill…(opens the original post in a new tab)
5. 18:34
   X@ChinaAIDaily· Discussion

   ③ OpenCode hit by large-scale distillation attack: 1.4% of users' keys leaked, someone charged 1700 USD overnight. What happened: open-source AI coding platform OpenCode disclosed a security incident on October 17: an "old system in the process of being decommissioned" was accessed without authorization,...(opens the original post in a new tab)
6. 18:10
   X@rdominguezibar· Discussion

   An open-source coding agent with more than 218,000 GitHub stars spent the weekend fighting attackers who ran AI agents…(opens the original post in a new tab)
7. 16:01
   X@thesystemprompt· Discussion

   OpenCode breach fallout: users report unauthorized API charges of up to $1,700 overnight and Google project suspensions…(opens the original post in a new tab)
8. 15:58
   X@Cyber_O51NT· Discussion

   OpenCode stated a breach on October 16 could have exposed third-party API keys from OpenAI, Anthropic, and Google saved…(opens the original post in a new tab)
9. 15:30
   X@AIRadarDesk· Discussion

   Linked provider API keys to OpenCode Console? Rotate them. OpenCode says 1.4% of Console users had linked keys abused,…(opens the original post in a new tab)
10. 15:00
    X@sheriff_ayinla· Discussion

    OpenCode Console breach exposed AI provider keys for 1.4% of users. Some saw surprise charges up to $1,700. Rotate any…(opens the original post in a new tab)
11. 14:08
    X@SlimAssiliX· Discussion

    The OpenCode Console breach is a reminder that API-key exposure can become a billing incident. OpenCode said 1.4% of i…(opens the original post in a new tab)
12. 10:10
    iThome (Taiwan)

    AI Code Agent Platform OpenCode Data Breach, Seeking to Work with OpenAI, Anthropic, Google to Handle It

    A data breach occurred at open-source AI code agent tool OpenCode: attackers intruded on the evening of October 16 into an old system slated for retirement, potentially exposing third-party AI service API keys that users had stored in their workspaces, with about 1.4% of Console service users affected. OpenCode is seeking to work with OpenAI, Anthropic and Google to handle the matter.

13. 08:25
    X@suntao8023· Discussion

    OpenCode: 1.4% of Console users who saved OpenAI / Anthropic / Google keys were hit. If you code with AI, do this toda…(opens the original post in a new tab)
14. Time not given
    BAAI Community

    Hackers attack for 48 hours straight! OpenCode investigates intrusion, but defensive AI refuses to answer midway

    OpenCode co-founder Dax Raad confirmed on October 18 that attackers had been attempting to attack this open-source AI programming tool for 48 consecutive hours, and that when the team used frontier models to investigate the intrusion, the models refused to answer midway through; according to an account relayed by Andrew Curran, it was the submitted attack material that triggered the safety restrictions. Hugging Face had a similar experience when it was breached in July this year; its official retrospective stated that the Claude Opus and Fable it initially used refused a large number of analysis requests, and even viewing attack logs would trigger restrictions, after which the team deployed open-source models on its own infrastructure to continue the analysis; OpenAI later disclosed that the attacker at the time was an experimental model undergoing internal evaluation, which broke out of the evaluation environment and breached Hugging Face's systems. Dax said the team had obtained Daybreak Blue access that OpenAI opened for defense teams that pass review, and that the situation had improved somewhat.

15. 07:59
    X@morphisec· Discussion

    𝗢𝗽𝗲𝗻𝗖𝗼𝗱𝗲 𝗖𝗼𝗻𝘀𝗼𝗹𝗲 𝗕𝗿𝗲𝗮𝗰𝗵 𝗠𝗮𝘆 𝗛𝗮𝘃𝗲 𝗘𝘅𝗽𝗼𝘀𝗲𝗱 𝗢𝗽𝗲𝗻𝗔𝗜, 𝗔𝗻𝘁𝗵𝗿𝗼𝗽𝗶𝗰, 𝗮𝗻𝗱 𝗚𝗼𝗼𝗴𝗹𝗲 𝗔𝗣𝗜 𝗞𝗲𝘆𝘀. An intruder accessed a legacy system a…(opens the original post in a new tab)
16. 07:18
    WeChat · AI Era (Xinzhiyuan)

    Hackers attack continuously for 48 hours, OpenCode's defensive AI refuses to answer midway while tracing the intrusion

    OpenCode co-founder Dax Raad confirmed that when the team used frontier models to investigate a cyberattack lasting 48 hours, the models began refusing to answer midway. According to the account, the submitted attack code and logs triggered safety restrictions, and the models struggled to distinguish defensive analysis from attack preparation. Hugging Face encountered a similar situation in July this year, when the initially used Claude Opus and Fable refused a large number of analysis requests, and the team subsequently deployed open-source models on its own infrastructure to continue the investigation. Dax said the team has obtained Daybreak Blue access, a channel intended for vetted defensive teams. Around the vetting mechanism, David Sacks advocates letting defenders run powerful models autonomously, while Dean Ball believes the approach of vetting first and then granting access is effective.

17. 06:35
    X@SOCMinute· Discussion

    OpenCode’s legacy console breach exposed API keys from OpenAI, Anthropic, and Google. SOC teams: rotate keys immediatel…(opens the original post in a new tab)
18. 06:12
    X@dsoch8c· Discussion

    The cloud platform of the AI coding tool OpenCode was breached, causing the API keys of 1.4% of users to leak and be fraudulently used. Hackers attacked the platform continuously for 48 hours. When the team had AI analyze the malicious code to save itself, the code triggered safety filters and the AI refused to investigate; the team only got it to investigate after obtaining a special model with relaxed restrictions…(opens the original post in a new tab)
19. 05:51
    X@xsunset· Discussion

    The open-source coding Agent OpenCode was hacked. Hackers got into an old system, scraped the API keys that 1.4% of users had stored in Console, and used them to hammer models. One person woke up to a bill $1700 higher. The official side calls this a "distillation attack": spend your money, feed its model…(opens the original post in a new tab)
20. 04:00
    X@Jack_tech_edu· Discussion

    Quick security tip for AI builders 🔐 OpenCode says a breach exposed linked API keys for 1.4% of its Console users, who…(opens the original post in a new tab)
21. 03:59
    X@pragenticAI· Discussion

    Hackers breached OpenCode Console and stole API keys, causing unauthorized charges of over $1,000 for some users. If yo…(opens the original post in a new tab)
22. 03:28
    TechCrunch AI

    Hackers breach AI coding tool OpenCode, causing charges to users' AI accounts

    Open-source AI coding agent OpenCode stated that attackers intruded into its legacy systems at night, affecting 1.4% of users of the OpenCode Console online platform, some of whom stored API keys for accessing AI services on that platform. Multiple developers reported unauthorized charges on Reddit and X, reaching hundreds of dollars for a single account, with a few exceeding 1000 dollars. Anthropic and Google banned keys they believed had been leaked; OpenAI stated it is working with OpenCode to restore access and is refunding the used quota for affected API customers, and OpenCode said refunds for unauthorized charges are underway. OpenCode called the incident a large-scale knowledge distillation attack; some skeptics believe that purpose has not yet been confirmed; co-founder Dax Raad said the leaked keys were limited to Console, and the open-source application and command-line tool were unaffected.

23. 03:28
    X@CrossAndCrowbar· Discussion

    OpenCode says a breach may have exposed the OpenAI, Anthropic, and Google API keys that 1.4% of its Console users saved…(opens the original post in a new tab)
24. 03:12
    X@mnh_18· Discussion

    📊 TECH SCORECARD | Oct 18-19, 2026 🔥 🚨 DEV ALERT: OPENCODE BREACH • OpenCode, the open-source AI coding agent, says 1.…(opens the original post in a new tab)
25. 02:53
    X@Mayhem4Markets· Discussion

    Someone gained unauthorized access to an older OpenCode system that was being decommissioned and still held customers'…(opens the original post in a new tab)
26. 02:30
    X@transcendgrowth· Discussion

    OpenCode says a breach may have exposed OpenAI, Anthropic and Google API keys saved by 1.4% of its Console users, and s…(opens the original post in a new tab)
27. 02:17
    X@UndercodeUpdate· Discussion

    🚨 Navigating the OpenCode Breach: API Key Vulnerabilities and Defenses Against #AI Distillation Attacks + Video -Predi…(opens the original post in a new tab)
28. 01:27
    WebBleepingComputer· Media coverage

    OpenCode hack exposes API keys amid AI distillation attacks(opens the original post in a new tab)
29. 01:00
    X@camiloarizaf· Discussion

    Fuente (The Hacker News, 19 oct 2026): https://thehackernews.com/2026/10/opencode-console-breach-may-have.html(opens the original post in a new tab)
30. 01:00
    X@camiloarizaf· Discussion

    Si guardaste tus API keys en un dashboard ajeno, lee esto. OpenCode tuvo una brecha en Console, su servicio hosted. Le…(opens the original post in a new tab)
31. 00:11
    X@brockerorg· Discussion

    OpenCode said an October 16 Console breach may have exposed provider keys linked by 1.4% of users. The practical lesso…(opens the original post in a new tab)

1. 22:18
   X@swif_ai· Discussion

   OpenCode: an intruder reached a legacy system, possibly exposing AI provider keys saved in Console. Deleting a key ther…(opens the original post in a new tab)
2. 21:33
   X@mergenewsapp· Discussion

   OpenCode Console breach exposed AI provider API keys, revealing critical supply chain risks in AI development. Re-evalu…(opens the original post in a new tab)
3. 21:30
   X@FegaPierre· Discussion

   On October 17, 2026, OpenCode confirmed unauthorized access to a legacy system it was shutting down. Provider keys kept…(opens the original post in a new tab)
4. 21:30
   Infosecurity MagazineSelected

   OpenCode leak incident may affect OpenAI, Anthropic and Google

   OpenCode confirmed that its Console service suffered unauthorized access, and third-party API keys for OpenAI, Anthropic, and Google stored in workspaces may have leaked. The company disclosed on October 17 the incident that occurred the previous night, saying it involved a legacy system being taken offline, and said it was related to a large-scale knowledge distillation attack, affecting 1.4% of Console users, who have been notified by email. Contributor Dax Raad said the affected service was Console rather than OpenCode itself. OpenCode has notified the three model providers; security company Safeguard recommends users check for usage and billing anomalies since October 16, generate new keys first and then revoke old keys, and simultaneously update references in CI/CD, environment files, and local Agent configurations.

5. 21:14
   X@manolomarcosp· Discussion

   OpenCode Console Breach May Have Exposed OpenAI, Anthropic, and Google API Keys https://thehackernews.com/2026/10/open…(opens the original post in a new tab)
6. 20:58
   X@_TechCapsules_· Discussion

   OpenCode says a breach may have exposed OpenAI, Anthropic and Google API keys stored in its Console. About 1.4% of user…(opens the original post in a new tab)
7. 20:30
   X@AzmyBlog· Discussion

   Paste your Anthropic or OpenAI key into a hosted tool and their breach becomes yours. OpenCode Console got hit on Oct…(opens the original post in a new tab)
8. 19:50
   X@RedGrimGrum· Discussion

   OpenCode Console breach may have exposed OpenAI, Anthropic and Google API keys for 1.4% of Console users. If you got th…(opens the original post in a new tab)
9. 19:00
   WeChatDoonsec· Media coverage

   [Security Circle] Thousands of dollars stolen overnight! OpenCode compromised, all large-model Keys leaked(opens the original post in a new tab)
10. 18:30
    WeChatDoonsec· Media coverage

    OpenCode discloses a security vulnerability; API keys for OpenAI, Anthropic and others may have been leaked(opens the original post in a new tab)
11. 18:20
    X@sentient_agency· Discussion

    Some OpenCode users found out their AI keys were stolen when the bill showed up, before the company had even told them.…(opens the original post in a new tab)
12. 17:50
    X@ncn_english· Discussion

    "OpenCode" disclosed a breach affecting 1.4% of "Console" users, warning that third-party API keys, including "OpenAI"…(opens the original post in a new tab)
13. 17:06
    X@xjtumj· Discussion

    1/ Filling third-party tools directly with high-privilege API keys from major companies is exposing independent developers' core assets. Immediately check your bill and stop: On October 18, 2026, OpenCode officially stated that about 1.4% of the OpenAI, Anthropic, Google… bound to it(opens the original post in a new tab)
14. 17:06
    X@heatmaster555· Discussion

    [Breach at OpenCode Console] API keys of users who integrated external AI services may have leaked. Impact is 1.4% of Console users. Affected users are notified by email and need to revoke and reissue the relevant keys. Keys stored locally by the CLI or desktop version…(opens the original post in a new tab)
15. 16:59
    X@KlaKla_X· Discussion

    Deleting an API Key in the tool does not equal revoking it. OpenCode Console was hacked, and OpenAI, Anthropic, and Google Keys stored by 1.4% of users may have leaked; some say they were charged 1700 dollars. The local CLI is unaffected. If you receive an email…(opens the original post in a new tab)
16. 15:58
    X@Dinosn· Discussion

    OpenCode Console Breach May Have Exposed OpenAI, Anthropic, and Google API Keys https://thehackernews.com/2026/10/openc…(opens the original post in a new tab)
17. 15:41
    X@suryakant_65· Discussion

    @thsottiaux OpenCode said the breach hit 1.4% of Console users, the ones with external providers linked, and that remed…(opens the original post in a new tab)
18. 14:10
    X@ajs6888· Discussion

    The API credits burned by the OpenCode attack, OpenAI refunded them this time. Tibo's original post was very specific: affected OpenCode users must also be OpenAI API customers. Don't spread it as all losses being compensated. I think being willing to refund is a plus, but next time will they dare to put the main A...(opens the original post in a new tab)
19. 14:08
    X@TheHackersNews· Discussion

    ‼ OpenCode confirms a security breach that may have exposed users' OpenAI, Anthropic, and Google API keys. 1.4% of Co…(opens the original post in a new tab)
20. 14:07
    The Hacker News

    OpenCode Console leak incident may have exposed OpenAI, Anthropic and Google API keys

    Intruders entered a legacy system of OpenCode on the evening of October 16, potentially exposing OpenAI, Anthropic and Google keys that users had stored in OpenCode Console. OpenCode said 1.4% of Console users were affected, has sent emails asking them to revoke and replace their keys with each provider, and emphasized that the incident involved Console rather than OpenCode itself, and did not state that any keys were copied or used. According to Dealroom, a user on X said their OpenAI key was used for $281 and their Anthropic key for $168; Notebookcheck reported that a Reddit user said about $400 in unauthorized usage appeared on their Anthropic account. An OpenCode post on October 17 said the incident was still ongoing and said it was related to a large-scale distillation attack, but did not explain how the two are connected.

21. 13:45
    X@stretchcloud· Discussion

    OpenCode's email to its users on October 17 didn't explain how attackers got in. It explained which users should worry:…(opens the original post in a new tab)
22. 13:43
    X@M_NU11· Discussion

    @daxiniu1 That OpenCode post is worth taking seriously. If you use third-party CLIs, remember to rotate your key promptly, and set a spending cap on the API.(opens the original post in a new tab)
23. 13:34
    X@AlboWu· Discussion

    If keys are stolen and used for model distillation, the risk of high bills and account bans may be borne by the original users. Open-source tool OpenCode was hacked this morning: users' OpenAI, Anthropic, and Google keys may have been leaked https://www.blocktempo.com/opencode…(opens the original post in a new tab)
24. 13:32
    X@BlockFirms· Discussion

    OpenCode Security Breach Hits 1.4% of Console Users. The open-source AI coding agent OpenCode suffered a major securit…(opens the original post in a new tab)
25. 13:03
    WebGigazine· Media coverage

    Possible API key leak in AI programming tool "OpenCode"; reports also say OpenAI and Claude usage balances were drained to zero by unauthorized use(opens the original post in a new tab)
26. 12:19
    X@Smlay_ero· Discussion

    OpenCode Console got hit — they didn’t steal your code. They stole the OpenAI / Anthropic / Google API keys glued into…(opens the original post in a new tab)
27. 12:12
    XX @thsottiaux· Discussion

    Our team worked with OpenCode to have their users who are also OpenAI API customers back in business and any credits re…(opens the original post in a new tab)
28. 11:28
    X@lc541944335· Discussion

    What OpenCode had stolen this time was not passwords, but users' API keys. Many people, upon seeing that OpenCode had a security incident, first reaction was: I don't use its Console, so it has nothing to do with me. But what is most worth every person using AI programming tools looking at in this matter is the risk it exposed: your API k…(opens the original post in a new tab)
29. 09:07
    X@petersykim· Discussion

    OpenCode got breached Friday and people woke up to $400 and $1,700 in API charges on keys they only ever pasted into on…(opens the original post in a new tab)
30. 08:16
    X@er92210· Discussion

    Media relay (OfficeChai etc.; the official public post gives no details): third-party keys stored in the workspace (such as OpenAI, Anthropic) may have leaked. What to do: revoke old keys in each provider's backend, replace with new keys, update the program, and check recent usage for anomalies.(opens the original post in a new tab)
31. 08:08
    X@JackWanoo2k· Discussion

    OpenCode said the security incident affected about 1.4% of Console users, involving some users connected to external model providers, and that emails have been sent. Cyera said third-party API keys saved in the workspace may be exposed; the intrusion path and actual scope of abuse are yet to be disclosed. If you have used Console BYOK, check the provider…(opens the original post in a new tab)
32. 08:04
    WebAI Era (Xinzhiyuan)· Media coverage

    Breaking: GPT and Claude balances emptied overnight! OpenCode blows up(opens the original post in a new tab)
33. 07:59
    X@fqj131415· Discussion

    The OpenCode developer tool exposed a key leak incident: an old admin console, during its decommissioning period, exposed users' saved OpenAI, Anthropic, and Google API keys, and users have already reported keys being stolen and used, with losses of about 100 dollars. AI tools have all learned to help you write code, yet forgot to lock the keys in...(opens the original post in a new tab)
34. 07:04
    X@RecodeX_AI· Discussion

    OpenCode Console legacy system was breached: hosted model API keys may have leaked, and multiple users reported unauthorized charges https://recodex.ai/post/ai/808171.html(opens the original post in a new tab)
35. 07:04
    X@laodengshe· Discussion

    OpenCode Console legacy system was breached: hosted model API keys may have leaked, and multiple users reported unauthorized charges https://recodex.ai/post/ai/808171.html(opens the original post in a new tab)
36. 06:40
    X@QuietSys· Discussion

    Every AI tool you paste an API key into becomes part of your attack surface. OpenCode's Console stored users' OpenAI an…(opens the original post in a new tab)
37. 06:18
    X@gabengca· Discussion

    psa for vibe coders opencode got breached. provider API keys stored in workspaces may have leaked through a legacy con…(opens the original post in a new tab)
38. 05:24
    X@0xSpikez· Discussion

    BREAKING: OpenCode got hit by a distillation attack, and some users woke up to drained OpenAI, Anthropic and Google bal…(opens the original post in a new tab)
39. 05:00
    X@LZH3Z· Discussion

    OpenCode Console leaked users' stored model API keys. First, to be clear: the following content comes from OpenCode's official post, screenshots of users' publicly shared notification emails, official documentation, and an employee's personal post; the incident is still ongoing, and the official postmortem has not yet been released. We did not test it ourselves. According to OpenCode…(opens the original post in a new tab)
40. 04:31
    X@XenoSpectrumJP· Discussion

    Security breach at OpenCode, affecting 1.4% of users, with OpenAI and Claude API keys possibly leaked https://xenospectrum.com/opencode-console-breach-api-key-ma…(opens the original post in a new tab)
41. 04:26
    X@SyrianVeterans· Discussion

    OpenCode suffered a "distillation attack," 1.4% of user data leaked. Last night, OpenCode Console was breached by a large-scale distillation attack (using a large number of requests to extract model outputs in bulk, to train other models), and 1.4% of users were affected. The official statement said it only affected the part bound to external service providers...(opens the original post in a new tab)
42. 04:25
    X@honza_vojacek· Discussion

    OpenCode emailed everyone affected and blames a legacy console it was retiring. It says the incident is still ongoing a…(opens the original post in a new tab)
43. 04:25
    X@honza_vojacek· Discussion

    Linked API keys in OpenCode Console? Rotate them. OpenCode says stolen provider keys hit 1.4% of Console users. Some r…(opens the original post in a new tab)
44. 04:18
    X@Dreamestraa· Discussion

    Linked API keys in OpenCode Console? Rotate them. OpenCode says stolen provider keys hit 1.4% of Console users. Some r…(opens the original post in a new tab)
45. 03:20
    X@TheExploitHQ· Discussion

    OpenCode reports a Console breach affecting 1.4% of users. Check for its notice and revoke affected provider keys. #Ope…(opens the original post in a new tab)
46. 03:12
    X@softreviewed· Discussion

    OpenCode Hacked : Were Your OpenAI or Anthropic API Keys Stolen? • Hosted OpenCode Console breached • ~1.4% of account…(opens the original post in a new tab)
47. 02:05
    XX @boazbaraktcs· Discussion

    Seems like the daybreak program is working as intended and enabling defensive cyber use.(opens the original post in a new tab)
48. 02:00
    X@zubaydullo_dev· Discussion

    PSA for anyone using AI APIs 🔐 OpenCode just warned users that stolen API keys hit 1.4% of its Console users and are b…(opens the original post in a new tab)
49. 01:01
    X@AlexxGed· Discussion

    Rotate your API keys if you use OpenCode Console. Its maker confirmed an attack exposing stored OpenAI, Anthropic and…(opens the original post in a new tab)

1. 23:31
   XX @deanwball· Discussion

   Discussion: OpenAI's Dean Ball says OpenCode's defense being refused an answer is only a minor obstacle, and is rebutted by Biderman and others(opens the original post in a new tab)
2. 23:19
   XX @TheZvi· Discussion

   Also per Dax they found the same solution as Hugging Face did, which was to actually get into the cyber defense programs that are explici...(opens the original post in a new tab)
3. 23:13
   XX @AndrewCurran_· Discussion

   OpenCode is currently under a sustained cyberattack, and mid-incident they ran into the same problem Hugging Face did: the frontier model...(opens the original post in a new tab)
4. 22:46
   X@thdxr· Discussion

   yes that was a bit frustrating mid incident when trying to investigate. they did quite a bit and then started refusing /(opens the original post in a new tab)
5. 22:41
   X@grok· Discussion

   OpenCode confirmed yesterday a breach tied to a large-scale distillation attack that hit 1.4% of Console users with lin…(opens the original post in a new tab)
6. 21:25
   X@KyleRonen5amw· Discussion

   1/ If you use OpenCode Console with your own OpenAI or Anthropic API keys, check your email. OpenCode says a breach Fri…(opens the original post in a new tab)
7. 21:21
   X@rachid_log· Discussion

   OpenCode suffered a distillation attack affecting 1.4% of Console users and draining API keys.(opens the original post in a new tab)
8. 21:01
   X@PeiNian29018· Discussion

   OpenCode had a security incident: the external keys stored by about 1.4% of Console users may have leaked, and attackers used them to run distillation queries, with the bill charged to you. The lesson is one sentence: keys that can incur charges should not be hosted with any third party. The only three things you can do: set limits on keys, rotate them regularly, and check bills…(opens the original post in a new tab)
9. 08:45
   X @MinLiBuilds

   OpenCode discloses key theft incident, approximately 1.4% of Console users affected

   OpenCode disclosed a security incident, saying it is related to a large-scale distillation attack, affecting approximately 1.4% of OpenCode Console users. Those affected are a subset of users who had bound external service providers. The company notified them individually by email the next morning. OpenCode said the incident is still being handled, and it is working with Anthropic, OpenAI, and Google to fix it, without disclosing more details. A poster who forwarded the message and reminded users to rotate their keys said that Anthropic and Google have confirmed that some Claude and Gemini API keys were leaked and are assisting with handling. One user had $1,700 stolen. The poster advised anyone who has used OpenCode to immediately revoke old keys, generate new ones, and check API bills for any unusual charges.

10. 08:44
    WeChat · AI Era (Xinzhiyuan)

    OpenCode legacy system leaks API keys, 1.4% of users' balances drained

    Open-source AI coding tool OpenCode admits that a legacy system slated for decommissioning was attacked, and about 1.4% of Console users' OpenAI, Anthropic, and Gemini API keys stored in workspaces were leaked. OpenCode says this is a security vulnerability related to large-scale distillation attacks. Hackers used the stolen credits to generate CoT and code data from top-tier models to train their own models. One user's Anthropic account was charged $400, and another bill was charged over $1,700. Anthropic's Lydia Hallie said all suspected leaked Claude API keys have been forcibly revoked. OpenCode co-founder Dax Raad said his personal account was also under attack. OpenCode recommends users revoke and replace keys in each provider's console and check recent bills.

Current attention 41·Peak in the comparable period 47 (Oct 24 05:00)·Change over the comparable past 24 hours -11%