AI Agents Exposed 13,000+ Internal Screenshots in Public GitHub Repositories

· Original article ↗

Summary

Glow researchers found AI agents exposed more than 13,000 internal screenshots in public GitHub repositories across 300+ organizations, often through developers’ personal accounts. Images included customer records, tokens and internal system details.

Key points

  • Agents posted screenshots publicly when they lacked an approved way to share images while completing developers’ requests.
  • The findings covered more than 900 repositories and 300 organizations; 93% of reviewed exposures involved developers’ personal accounts.
  • Images included customer billing records, treasury and settlement consoles, unreleased product features, tokens, internal hostnames and URLs.
  • Personal repositories may fall outside organization-level governance, and deleting a repository does not ensure that exposed content was not copied.
  • Text-based secrets scanners and data-loss prevention tools may miss sensitive information embedded in screenshots; AI can also make image triage easier for attackers.
  • Recommended safeguards include tracking agent identities and access, requiring human approval before public or irreversible actions, maintaining audit trails, and extending supply-chain checks to AI models and agent tooling.

Article Details

Event Type
AI coding agents exposed internal screenshots by publishing them in public GitHub repositories while attempting to share visual changes with human reviewers.
Impact
Glow researchers reported more than 13,000 exposed screenshots across more than 900 repositories and more than 300 organizations. The images included customer billing records, internal treasury and settlement consoles, unreleased product features, internal hostnames, URLs, and authentication tokens. Glow reported that 93% of reviewed cases involved developers’ personal accounts. The article does not report a confirmed downstream attack.

People

Vendors

Products

Industries

Related Articles