OpenCode Reports Possible Exposure of Third-Party API Keys After Legacy System Breach
OpenCode has disclosed a security incident in which an attacker gained access to a legacy system on the night of October 16, potentially exposing API keys from third-party providers that users had saved in the Console.
The company stated that the breach affected only 1.4 percent of Console users. The legacy system was already in the process of being decommissioned at the time of the incident. OpenCode did not provide details on how the access occurred, how long it lasted, or how many keys were stored in the system.
The exposure was described as possible rather than confirmed. The company has not stated that any keys were copied or used. Some users have reported unrecognized charges on their provider accounts following the incident.
According to cofounder Dax Raad, the incident was limited to the Console and did not affect the core OpenCode platform. Keys added through the command-line interface or desktop applications remain stored locally on users' machines.
On October 17, OpenCode sent emails to affected users and confirmed that anyone who did not receive a notification was not impacted. In the same statement posted on X, the company said it was working with Anthropic, OpenAI, and Google while the incident was ongoing.
The company linked the event to a large-scale distillation attack but did not explain the connection or name any responsible party. The article notes the lack of technical evidence linking the two events.
Users are advised to revoke and rotate keys directly in each provider's dashboard, as deleting a key from the Console does not revoke it. They should also update any applications that used the old keys and review provider usage and billing starting from October 16.
Related articles
Moscow Court Places Dodo Pizza Cyberattack Suspect Denis Fridman Under House Arrest Until 2026
The Tverskoy District Court of Moscow has ordered Denis Fridman to remain under house arrest until December 8, 2026, in connection with a cyberattack on Dodo Pizza that occurred in late September. Fridman faces charges under paragraphs a and v of part 3 of Article 272.1 of the Russian Criminal Code, which covers the illegal circulation of computer information containing personal data. Investigators detained three of the four suspects after Fridman failed to mask his real IP address while accessing the stolen dataset. The breach lasted two days, but Dodo Pizza quickly blocked access and confirmed that payment details were not compromised because the company does not store them. Authorities notified Roskomnadzor of the incident and implemented measures to forcibly terminate active user sessions where necessary. House arrest remains a preventive measure, and Fridman’s guilt has not yet been established by the court.
Yandex Disk Data Center Incidents Leave Photos and Videos Inaccessible, Custom Recovery Tool Emerges
Following incidents at Yandex data centers in Sasovo and Vladimir, large numbers of photos and videos stored on Yandex Disk became unavailable for normal download. The company attributed the restrictions to load reduction, yet analysis indicates permanent loss of certain data clusters with no confirmed backups. Photos remain partially recoverable through lower-resolution S3 copies such as XXXL and XXL, while videos suffer from missing byte ranges that produce truncated or corrupted files. A researcher developed a specialized tool using mitmproxy to intercept browser requests and download available file variants in parallel streams. The utility also attempts block-by-block video retrieval to salvage whatever segments remain accessible. Users are warned that continued use of the tool may violate service terms and risk account suspension. The developer advises downloading data immediately rather than waiting for potential further degradation.
AT&T to Pay $177 Million to Settle Two 2024 Customer Data Breach Class Actions
AT&T has agreed to pay a total of $177 million to resolve two separate class-action lawsuits stemming from major customer data leaks that occurred in 2024. The settlement, approved on October 2 by Judge Sidney Fitzwater in the Northern District of Texas, allocates $149 million to the first breach and $28 million to the second, covering compensation, attorney fees, and administrative costs. The first incident, disclosed on March 30, 2024, exposed personal information of 73 million individuals, including names, addresses, phone numbers, dates of birth, account passwords, billing numbers, and Social Security numbers for some victims, with records dating from 2019 or earlier found on the dark web. The second breach originated from unauthorized access to AT&T’s Snowflake cloud environment between April 14 and 25, 2024, affecting nearly all mobile customers and revealing call metadata such as phone numbers, interaction counts, durations, and cell tower identifiers from May to October 2022 plus January 2023. No evidence of direct system intrusion was found in the first case, and the second exposure did not include Social Security numbers or call content. Individual claimants can receive up to $5,000 or $2,500 respectively for documented losses, with the claims deadline set for December 18, 2025. AT&T settled without admitting any wrongdoing or liability.
EY Confirms Data Breach Exposing Goldman Sachs and Man Group Client Details via Checkmarx Vulnerability
EY has confirmed a data breach involving client documents accessed through a third-party technology services management platform used to support its tax operations. The unauthorized access occurred via a vulnerability in Checkmarx software and lasted from March 28 to April 12, with detection only on April 23. Exposed information included names, addresses, tax identification numbers, email addresses, and financial details belonging to clients in Goldman Sachs wealth management and the Man Group investment fund. Neither Goldman Sachs nor Man Group systems were compromised, confirming the exposure originated solely from EY's environment. The leaked materials consisted of attachments from support tickets rather than core system data. EY has engaged independent security firms, notified regulators in California, Texas, Massachusetts, and Vermont, and offered credit monitoring to affected individuals.