OpenCode Warns Some Users' AI Provider Keys Were Exposed in Console Breach

·1 views

OpenCode, an open-source AI coding project, told some users of its hosted Console on October 17, 2026 that third-party provider keys stored in their workspaces may have been exposed. The company said 1.4% of Console users, those who had linked providers such as OpenAI, Anthropic and Google, were affected. Reports say attackers entered through a legacy system the project was preparing to retire, and that Anthropic and Google blocked keys believed to be compromised. One report indicates OpenAI was refunding affected customers, though OpenCode has not detailed how many keys were involved or how the intrusion occurred. The incident was part of a wider October pattern in which several companies disclosed breaches exposing API keys, tokens or environment variables.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Pagure Token Scoping and Forge Exposure: Index Counts and Review Guidance

An analysis of Pagure, a self-hosted git forge, examines how many public instances appear in the ZoomEye search index. Count-only queries on November 9, 2026 returned 22 title matches, 181 body-domain matches, and zero application fingerprints. The author notes that body matches are only candidates and that the counts do not prove any instance is public or misconfigured. The piece distinguishes project-scoped tokens, which limit access to one repository, from project-less user tokens that can act across projects and resemble a password for the forge identity. It recommends auditing token scope, ACLs, expiry, last use, and related SSH keys, deploy keys, and CI webhooks, along with restricting management interfaces and running controlled authorization tests.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Hard vs. Soft Payment Declines: Why Retry Systems Must Split Them First

Developers handling payment declines should first determine whether a refusal is final or temporary, since this single distinction shapes every retry decision. Hard declines reflect the credential itself, such as a closed or stolen card, and repeated attempts are futile and can harm the descriptor's standing with issuers. Soft declines stem from transient conditions like insufficient funds or incomplete authentication, and they respond better to spaced retries, credential checks, and a single early customer message. Grey-zone cases, including authentication-required and generic responses, need explicit routing based on transaction history. Splitting outcomes into this branch also yields clearer metrics that reveal whether problems lie in scheduling or customer messaging.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Solo Maintainer Ships Turso PHP Extension Reliability Overhaul and Installer Fix

A freelance engineer who maintains Turso and libSQL PHP tools in spare time reported major progress on November 9, 2026. The core turso-client-php project merged a reliability overhaul fixing crash-prone error handling, memory safety issues, statement reuse bugs, and configuration problems. A follow-up release, turso-php-extension v1.7.0, restored Windows builds and added PHP 8.5 binaries, with Windows NTS support deferred to v1.7.1. The installer project also closed a long-standing PHP 8.5 issue by suppressing a PDO deprecation warning at the entry point. The author noted that the underlying libSQL engine was not upgraded in this release, focusing instead on stability and compatibility.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Canonical Tags: When to Use Them and Common Pitfalls

A canonical tag signals to search engines which URL is preferred among duplicate or near-identical pages, but it is a hint rather than a binding directive. Google still makes the final choice, and conflicting signals such as redirects or noindex can influence that decision. A survey of the Tranco top 10,000 domains in October 2026 found that 31% of analyzed sites lacked a canonical URL declaration, though this does not mean Google cannot select one. The guidance recommends using canonicals for duplicate content such as tracking-parameter URLs, self-referencing tags for preferred URLs, and cross-domain tags only when content is equivalent. Implementation should use absolute URLs in the HTML head, with HTTP response headers available as an alternative for non-HTML files like PDFs.

0 comments Read more at DEV Community