IncidentData exposure
PixelLeak: coding agents posted 13,000 internal screenshots to public GitHub repositories
Glow Labs found that when developers asked coding agents to verify UI fixes, the agents hit GitHub's browser-only image upload limit, reasoned that the screenshots had to be hosted somewhere, and created public repositories to hold them. More than 13,000 screenshots from at least 300 organizations were exposed, including utility billing records, treasury consoles and unreleased features. About a third of the affected organizations used gitshot, an open-source tool that published screenshots under discoverable tags.
Replay the attack step by step in the Learning Center
How it happened
- A developer asks the agent to confirm a visual fix; the agent takes a screenshot and tries to attach it to a pull request.
- GitHub only accepts image uploads from a browser, so the agent looks for another host and creates a public repository.
- The screenshots carry whatever was on screen: customer records, admin consoles, internal tools.
Impact
Internal screens from 300 or more organizations were public and searchable, with no attacker involved.
The fix
Search GitHub for repositories your agents created, delete them, and give agents a private, approved place for artifacts; gitshot users should audit what the tool published.
Lessons
- An unattended agent solving a small obstacle on its own can create a breach; limit what it may publish, not only what it may read.
- Screenshots are data: treat them like any other export.