Coding agent exposed customer billing screenshots in a public repository
Review RAT-007 · Catalogue RAT-007
The real manufacturer billing-screen leak has substantive Glow primary plus The Register direct interview, but neither establishes occurrence year/day. Publication September29 and notifications beginning September9 cannot be substituted for occurrence. Eligible organizational disclosure in principle, held because the current date schema cannot express this uncertainty.
Reviewed: · Rule: roguewatch-organizational-harm-v1
Dates and discovery
- Incident date
- Not disclosed
- Added to research / record
- Posted to RogueWatch
- No linked public incident
- First observed
- 2026-10-30T13:13:32.055844Z UTC
- Discovery channel
- User-supplied comparison audit
- Discovery source
- https://rogueaitracker.com/incidents/coding-agent-public-billing-screenshots/
When to reconsider
A source establishes the manufacturer episode occurrence year/month/day, or schema explicitly supports unknown occurrence with an upper bound. Separate early-July software-vendor case requires its own case-specific second source.
Dates use America/Los_Angeles. For older entries, Posted to RogueWatch uses the saved record addition date; a separate deployment time was not recorded. Future posting timestamps record first public qualification. Source publication and incident occurrence are separate.
Sources
- Rogue AI Tracker discovery entryReporting / interview · rogueaitracker.com
- www.glow.ioOriginal account · www.glow.io
- www.theregister.comReporting / interview · www.theregister.com
Decision history
- · Case-by-case comparison audit
RAT-007: awaiting-evidence. The real manufacturer billing-screen leak has substantive Glow primary plus The Register direct interview, but neither establishes occurrence year/day. Publication September29 and notifications beginning September9 cannot be substituted for occurrence. Eligible organizational disclosure in principle, held because the current date schema cannot express this uncertainty. Source checks: read: https://www.glow.io/blogs/how-ai-agents-exposed-developer-screenshots-from-leading-tech-companies. Read original manufacturer/utility-billing example and disclosure context; occurrence date is not given. Separate software-vendor early-July example must not date this case. read: https://www.theregister.com/ai-and-ml/2026/09/29/ai-models-keep-posting-screenshots-showing-sensitive-data-from-inside-tech-companies/5299640. Authored report directly interviews Omer Singer and describes manufacturer billing-screen case. Same underlying investigator account; no independent victim-log verification and no occurrence date.
Evidence source · Evidence source - · Retained review-queue assessment
The real manufacturer billing-screen leak has substantive Glow primary plus The Register direct interview, but neither establishes occurrence year/day. Publication September29 and notifications beginning September9 cannot be substituted for occurrence. Eligible organizational disclosure in principle, held because the current date schema cannot express this uncertainty.
Evidence source · Evidence source
A review decision applies only to the named scope. Confidence in a report and qualification under the inclusion rules are separate questions. Review records do not add incidents to the globe or leaderboard.