TL;DR
Get privacy and security gear delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
Apiiro reports that it found passwords and other secrets in 1,122 public GitHub files associated with use of Claude Code’s “Don’t Ask Again” option. The supplied report does not establish how many credentials remain valid, whether the files were exposed because of that option alone, or whether Anthropic has confirmed the findings.
Security firm Apiiro says it found passwords and other secrets in 1,122 public GitHub files associated with developers using Claude Code’s “Don’t Ask Again” permission option. The finding points to a possible way sensitive information can enter public code repositories, but the material available for this report does not establish that the option itself caused each exposure or whether any of the credentials are still usable.
Apiiro’s report describes exposed credentials in files available on public GitHub repositories. The reported total is 1,122 files; it is a count of files, not necessarily a count of unique passwords, accounts, developers, or affected organizations. The supplied source does not provide a breakdown by credential type or repository, nor does it state when the files were collected.
The report connects the exposures to Claude Code’s “Don’t Ask Again” option, which is presented in the story’s title as the relevant feature. The source material provided here does not explain the exact technical sequence that led secrets to be included in the files, or give examples sufficient to independently verify the relationship. The connection should therefore be understood as Apiiro’s report, not as a confirmed finding by Anthropic or GitHub.
The supplied material identifies Apiiro as the source but does not include a direct quotation from its researchers, a methodology, or a response from Anthropic. It also provides no information about whether repositories or credentials were removed, whether affected parties were notified, or whether the company has changed Claude Code’s behavior. Those details are needed to gauge the extent and current status of the exposure.
Risks of Secrets in Public Repositories
Passwords and other credentials committed to public repositories can create security risks for the people and organizations that rely on them. If a credential remains active, someone who obtains it could potentially use it to access a service or account. The report does not say that any such access occurred, so exposure should not be equated with confirmed misuse.
The finding also draws attention to how developer tools and their permission choices interact with routine coding work. If files created, modified, or handled during an agent-assisted workflow contain secrets, those details can become public when developers publish code without spotting them. The Apiiro report suggests a pattern worth investigating, but the available evidence does not show how often it occurs across Claude Code users or other coding assistants.
For developers, the immediate practical concern is whether their own public repositories contain credentials that should not be there. For organizations, the count raises questions about secret detection, repository review, and how coding tools handle sensitive data. These are implications of the reported discovery, not proof that a particular product defect or organizational failure caused every file to be exposed.
Products Worth Considering
eufy Security 4G LTE Cam S330 4K Solar Outdoor Camera with Pan and Tilt, AI Tracking, SIM Card and 32GB SD Card
eufy Security SoloCam E42 4K Solar Security Camera with AI Motion Tracking
eufy Security SoloCam E42 4-Camera Kit with HomeBase 3, 4K Solar Security Cameras
As an affiliate, we earn on qualifying purchases.
Claude Code and the Reported Setting
Claude Code is Anthropic’s coding assistant. In this report, “Don’t Ask Again” is the named permission option linked to the discovered files. The supplied source does not explain the option’s full function, how it stores or applies permissions, or whether its behavior changed over time. It would be inaccurate to infer a specific technical mechanism from the headline alone.
Apiiro’s source page is presented as a report about coding agents and secrets on GitHub. However, the source material supplied for this article consists largely of page text and the report title; it does not include the article’s detailed evidence. No collection dates, search terms, file examples, validation process, or comparison baseline are provided. The figure should be treated as Apiiro’s reported observation, rather than a verified measure of all exposed secrets connected to Claude Code.
Public code repositories can make files visible beyond their authors and intended collaborators. That is why even a single exposed, active credential may warrant attention, while a raw file count alone cannot show the number of people affected or the degree of harm. Apiiro’s figure provides a reason to examine the issue, but more information is needed to establish its scope.
““Claude Code’s ‘Don’t Ask Again’ exposes passwords in 1,122 public GitHub files.””
— Apiiro, in the report title
Scope and Credential Status
Several central details remain unknown from the material provided. It does not specify the investigation’s date range, how Apiiro identified the files, whether researchers verified each suspected secret, or whether the 1,122 files contain distinct credentials. It also does not say whether the files remain publicly accessible.
The report material does not establish how many credentials are active, whether any were used by unauthorized parties, or whether affected developers and organizations were contacted. Nor does it include a response from Anthropic or GitHub. Without those details, the scale of practical harm and the precise relationship between the permission option and each exposure cannot be determined.
Verification and Remediation Steps
The next developments to watch for are publication of Apiiro’s underlying methodology and any response from Anthropic. More detail about how the files were identified, whether the credentials were validated, and the dates involved would help clarify both the count and the link to Claude Code’s setting.
Developers and organizations concerned about the report can review their public repositories for accidentally committed secrets. If a credential is found, it should be treated as exposed: removing the file from a repository may not make an existing credential safe, so the account owner should follow the relevant provider’s process for revoking or replacing it. This general precaution does not mean that Apiiro has confirmed any specific account was compromised.
Key Questions
What did Apiiro report?
Apiiro reported finding 1,122 public GitHub files containing passwords or other secrets in a pattern it linked to Claude Code’s “Don’t Ask Again” option.
Does the report prove Claude Code caused every exposure?
No. The supplied source connects the files with the option, but it does not provide enough technical detail to establish that the setting alone caused each secret to be published.
Were the exposed credentials used?
The available material does not say whether any credential was active or used for unauthorized access. It reports files containing secrets, not confirmed account compromise.
Are the 1,122 files 1,122 separate passwords?
That is not established. The figure counts files according to the report title; the source material does not state how many unique credentials or affected accounts they represent.
Has Anthropic responded to the finding?
No Anthropic response is included in the supplied source material. It is also unclear whether the files were removed, whether affected parties were notified, or whether the product’s behavior has changed.
Source: apiiro.com
![Paged Out #9 [Pdf]](https://security-zone.info/wp-content/uploads/2026/07/paged-out-9-pdf-featured-560x300.jpg)
