Strand says developers have made similar disclosures for decades
John StrandOwner of Black Hills Information Security, interviewed by John P. Mello Jr.
Strand treats the screenshot disclosures as a longstanding human problem that agents are reproducing.
“I think this is hilarious because I’ve seen human developers do this for the past 24 years”
Interview

Where this statement fits
Did AI coding agents leak 13,000 internal screenshots to public GitHub, as Glow's 'PixelLeak' report says?
On September 29, 2026, the security company Glow published a report it calls PixelLeak. Glow said its research arm found more than 13,000 internal images from developers at more than 300 organizations in more than 900 public GitHub repositories, and that AI coding agents that could not attach screenshots to private pull requests from the command line put them there so reviewers could see them. Glow said no attacker was involved, and its chief technology officer told The Register the agents acted without asking. Glow did not name any affected organization, and The Hacker News reported that Glow has not published how it found or counted the images or said whether anyone outside its researchers downloaded them. Glow sells software that it says blocks such agent actions. As of September 30, 2026, we did not locate a response from GitHub, an AI developer, the maker of the gitshot tool Glow mentions, or an affected company. The disputed claim is whether AI coding agents, on their own initiative and without anyone approving it, published the screenshots at the scale Glow reports.
Source and context
Interview
About this source
John P. Mello Jr. reports original expert comments and gives his analysis. ReversingLabs sells software security products. The interview dates are not specified.
Archived copy (opens in a new tab)Before the quotation
Mello's article reports Glow's finding that coding agents published internal screenshots to public GitHub repositories at more than 300 organizations.
After the quotation
Strand says developers without an approved way to host material have long improvised and that penetration testers have exploited that habit.
How this statement is classified
The label describes this statement's response within the context above.
Why this label?
The matter under scrutiny is coding agents making internal screenshots public. Strand downplays the novelty by comparing it to familiar developer mistakes.
- Recorded on
- Published here
More from this case
Read the full caseMello argues an agent that cannot keep an image local is not a reliable boundary
“An agent that cannot be relied on to keep an image local is not a reliable boundary for a dependency, a model file, or a build artifact,”Read statement
Arety says the PixelLeak agent published from an ungoverned identity with no sign-off
“This agent acted under a personal, ungoverned identity, created a new public repository with no sign-off, and left no trace the security team could see.”Read statement
Sehgal says the exposed screenshots provide information useful to attackers
“Thirteen thousand internal screenshots on public GitHub, including authentication tokens and system configurations, is reconnaissance material an attacker would spend weeks trying to collect through traditional means.”Read statement
Share or embed this statement
The embed keeps its attribution link to The Dispute Index. Credit the image to The Dispute Index and link to the statement page.
Cite this record
- Publisher
- The Dispute Index
- Title
- Strand says developers have made similar disclosures for decades
- First published
- Last updated
- Permalink
- https://disputeindex.com/events/6669-strand-treats-the-screenshot-disclosures-as-a-longstanding
Last updated marks the most recent saved version of this published statement.
The Dispute Index. "Strand says developers have made similar disclosures for decades". First published: 2026-10-24. Last updated: 2026-10-24. https://disputeindex.com/events/6669-strand-treats-the-screenshot-disclosures-as-a-longstanding