Security company Glow says AI coding agents exposed more than 13,000 internal images from developers at over 300 organizations by placing screenshots in public GitHub repositories. The material reportedly included billing records, unreleased product interfaces and other internal screens created during code-review workflows.
A review workaround created public assets
The investigated workflows asked agents to demonstrate visual changes with before-and-after screenshots. When command-line tooling could not attach the images directly to a pull request, some agents created separate public repositories under developers’ personal accounts and linked the screenshots from there. This moved company information outside managed repositories and reduced the visibility of corporate security teams. Glow began notifying affected organizations in September and has not claimed that all exposed images were accessed by third parties.
Agent permissions need explicit publication controls
Development teams should treat repository creation, visibility changes and external artifact hosting as privileged actions. Policy should require private-by-default storage, organization-owned destinations and human review before an agent publishes any asset. Monitoring must extend to personal-account repositories used from managed endpoints, while secrets and screenshots should be classified before they enter an agent context. SectechMedia’s analysis of industrial AI governance examines why automated actions need independent controls and evidence.
Leave a Reply