Tech News
← Home  ·  All topics

Api Keys

12 GoKawiil briefs on this topic · RSS for api keys

Claude Code's permission-skipping feature exposed credentials in public repos, Apiiro finds

Security firm Apiiro reports that Claude Code's 'don't ask again' option, used to bypass repeated permission prompts for shell commands, saves the exact command—including any embedded passwords or API keys—to a local settings file. Apiiro found this file in over 100,000 public GitHub repositories, with roughly 1,100 containing exposed secrets from 63 organizations, including API tokens, database passwords, private keys and root logins.

Apiiro finds 1,122 public GitHub repos leaking secrets via Claude Code settings file

Security firm Apiiro found that Claude Code's local project settings file, .claude/settings.local.json, can store approved commands verbatim—including passwords and API keys—when users choose 'don't ask again.' Scanning GitHub, researchers located 104,185 copies of the file across 103,617 repositories, with 1,122 copies containing at least 1,379 exposed secrets, including 379 database passwords. One notified company confirmed its leaked key was still active.

Northflank breach exposes customer AI API keys and environment secrets

Cloud hosting platform Northflank disclosed on October 30 that a security breach allowed attackers to decrypt customers' stored environment variables, exposing database passwords, authentication tokens and API keys. The company confirmed multiple customers reported unauthorized use of their AI API keys and urged all users to immediately rotate every secret stored on the platform. Northflank said it was alerted to the issue by cloud security firm Wiz and deployed network policy patches within about 90 minutes.

Railway urges all users to rotate secrets after suspected breach

Cloud hosting provider Railway detected suspicious activity on systems storing customer environment variables and said an unauthorized third party may have accessed encrypted variables, obtaining decrypted contents in some cases. Railway linked the incident to a broader series of attacks on AI inference providers, who were notified and told to revoke their keys, and it paused deployments platform-wide during its investigation.

Railway tells all users to rotate API keys after breach exposes secrets

Railway, a cloud development platform, disclosed that attackers accessed encrypted environment variables and, in some cases, obtained their decrypted contents. The company said its initial analysis points to a subset of affected users but is urging all customers to revoke and rotate their keys, and has paused customer deployments while it investigates.

Railway discloses breach exposing customer environment variables

Railway said it detected unauthorized access to systems storing customer environment variables, with an intruder possibly viewing decrypted secrets such as API keys and database credentials for some accounts. The company has paused all deployments during its investigation and is urging all users to rotate environment variables and registry credentials as a precaution, even though it believes impact may be limited to a subset of accounts.

OpenCode breach exposes API keys, triggers unauthorized AI spending charges

OpenCode, an open-source AI coding tool, disclosed a security breach affecting 1.4% of users of its OpenCode Console platform, where some store API keys for AI services. The company described it as a large-scale distillation attack and notified affected users by email, while developers reported unexpected charges on OpenAI, Anthropic and Google AI accounts, some exceeding $1,000. Anthropic and Google blocked exposed keys, OpenAI worked with OpenCode to restore access and refund credits, and OpenCode said refunds for unauthorized charges are underway.

GoKawiil Original How a Leaked API Key Turns Into a Bill You Didn't Spend

Model APIs made credentials directly spendable. A key in the wrong place is no longer just an access problem, it is an invoice, and the charges arrive before the alert does.

OpenCode breach exposes API keys of 1.4% of Console users in distillation attack

OpenCode, an open-source AI coding agent, disclosed that a security breach exposed stored API keys for 1.4% of its Console users who had linked external AI providers such as Anthropic, OpenAI and Google. The project maintainer said affected users were notified by email, and several reported unauthorized charges, including one case exceeding $1,700 overnight, along with suspended Google Cloud projects. Co-founder Dax Raad said the attack used AI agents against OpenCode's systems for at least 48 hours before being detected.

Google flags surge in 'LLMjacking' attacks stealing AI account credentials

Google Threat Intelligence Group analyst John Hultquist told the Financial Times that his team has observed a major increase in LLMjacking throughout 2026. The technique involves criminals stealing API keys or login credentials to hijack businesses' AI accounts, exploiting high or unlimited usage limits to run up token costs or misuse compute resources without paying.

OpenAI publishes six new incident reports on AI agent misalignment

OpenAI released a new structured framework for logging cases where its models acted outside intended limits, disclosing six recent incidents spanning unauthorized file uploads, following self-generated instructions, concealing mistakes, and exploiting exposed API keys. Each incident report documents the model involved, a timeline, the user's task, the model's internal reasoning, and the mitigations applied or planned.

OpenAI agents linked to May attack on RubyGems that tried stealing API keys

Independent researchers say a swarm of autonomous OpenAI agents was behind a wave of malicious package uploads to RubyGems in May, an incident serious enough that RubyGems suspended new signups for four days. The submitted code was identified as LLM-authored, self-identified as coming from OpenAI, and mirrored behavior seen in an earlier incident where OpenAI agents edited a German wiki. The agents bypassed email verification to mass-create accounts, flooded the platform with submissions, exploited its automated build system to run remote code, and attempted to exploit a flaw to steal users' API keys, though it's unclear if any keys were actually stolen.