// AI threat desk · 15 Nov 2026
Home/LEAK · Data Leaks
Data LeaksMediumAISECCVSS not assigned

Claude Code command saved credentials to public Git repos, report says

A Claude Code command saved credentials and sensitive files to public Git repositories, Dark Reading reported. Glow Labs disclosed related research on Oct 16.

· 1 min read
AI-generated image of a developer reviewing code and repository settings on a laptop.
AI-generated image, not a photo of the event.
Key takeaways
  • Dark Reading reported that a Claude Code command inadvertently saved credentials and other sensitive files to public Git repositories.
  • Glow Labs identified more than 13,000 internal images published on GitHub by developers at more than 300 organizations.
  • The PixelLeak exposure affected more than 900 code repositories across enterprises with more than 100,000 employees.

A command in Claude Code inadvertently saved files containing credentials and other sensitive data to public Git repositories, creating security gaps for organizations, Dark Reading reported.

The exposure reached more than 13,000 internal images published on GitHub by developers at more than 300 organizations. Glow Labs found that the PixelLeak exposure affected more than 900 code repositories across enterprises with more than 100,000 employees.

Glow Labs published its research on Oct 16, 2026.

On this page

Gitshot and agent skills helped publish internal images

Glow Labs found that around a third of affected organizations had developers running gitshot, an open-source tool that publishes screenshots for code reviews.

In 93% of cases, the images sat in a repository created by an employee under the employee’s own username.

Glow Labs recommends controls for personal repositories

Glow Labs began notifying organizations identified during its PixelLeak research on Sep 9, 2026, but said others are likely affected.

What to do now

  1. Remove exposed images everywhere they exist, ask anyone with a copy to do the same, and rotate whatever is legible in the pictures.

FAQ

What happened with Claude Code?

Dark Reading reported that a command in Claude Code inadvertently saved files containing credentials and other sensitive data to public Git repositories.

How many organizations and repositories were affected by PixelLeak?

Glow Labs identified more than 13,000 internal images published on GitHub by developers at more than 300 organizations, and found that the exposure affected more than 900 code repositories across enterprises with more than 100,000 employees.

What is gitshot?

Glow Labs described gitshot as a small open-source tool that publishes screenshots for code reviews. Around a third of affected organizations had developers running it.

Were credentials or other sensitive files exposed?

Dark Reading reported that Claude Code inadvertently saved files containing credentials and other sensitive data to public Git repositories.

How should organizations respond to exposed images?

Glow Labs recommends removing exposed images everywhere, asking recipients to remove copies and rotating credentials visible in the images.

Did Glow Labs notify affected organizations?

Glow Labs began notifying organizations identified during its PixelLeak research on Sep 9, 2026, but said others are likely affected.

Sources

  1. PixelLeak: How AI Coding Agents Leak Screenshots to Public GitHub, Glow LabsPrimary
  2. AI Coding Agents Leak Thousands of Secrets to GitHub, Dark Reading
  3. Three AI coding agents leaked secrets through a single prompt injection. One vendor's system card predicted it, VentureBeat
How we checked this story
ClaimSourceStatus
Dark Reading reported that a Claude Code command inadvertently saves files containing credentials and other sensitive data to public Git repositories.Dark ReadingAttributed
VentureBeat reported that a security researcher and Johns Hopkins University colleagues used a malicious GitHub pull-request title to test Claude Code Security.VentureBeatAttributed
Glow Labs identified more than 13,000 internal images openly published on GitHub by developers at more than 300 organizations.Glow LabsConfirmed
Glow Labs found that the PixelLeak exposure affected more than 900 code repositories across enterprises with more than 100,000 employees.Glow LabsConfirmed
Glow Labs found that around a third of affected organizations had developers running the open-source gitshot screenshot-publishing tool.Glow LabsConfirmed
Glow Labs said 93% of cases involved images stored in repositories created by employees under their own usernames.Glow LabsConfirmed
Glow Labs began notifying organizations identified during its PixelLeak research on 9 September 2026.Glow LabsConfirmed
glow.io published its report on Oct 16, 2026.glow.ioConfirmed

Could not verify

  • Whether the exposed secrets were used is not established
  • Whether the incidents reported by S1, S2, S3, S4 and S5 are the same event is not established
  • How many organizations were affected by the credential exposure is not established
  • Whether Anthropic or GitHub made changes in response is not established
anthropic
See all in Data Leaks →
Explore with AI
ChatGPT
Claude
Perplexity
Grok