← All posts

The Screenshot Tool Nobody Approved: What the Gyazo Breach Means for Every Board

Somewhere in your company, right now, an employee is probably using a free screenshot tool to quickly share a screen capture with a colleague, a customer, or a vendor. It is not on your approved software list. Nobody in IT signed off on it. It is just there, the way sticky notes and personal Gmail accounts are just there — useful, invisible, and, as of this month, the reason 23.62 million user accounts and 490 million image records ended up in the hands of an unauthorized third party.

The tool is Gyazo, a widely used screenshot-sharing service operated by the Japanese company Helpfeel. On September 16, Helpfeel disclosed that an attacker had exploited a vulnerability in Gyazo's image upload server, executed unauthorized commands, and accessed the company's database. The breach itself is worth understanding. What it reveals about a blind spot most boards have never discussed is worth more.

What Actually Happened

According to Helpfeel's own public notice, the intrusion unfolded over five days in mid-September. On September 11, 2026, an attacker exploited a vulnerability in Gyazo's image upload server to gain unauthorized access and run arbitrary commands. Helpfeel detected the activity and blocked the attacker's access the following day, September 12, and remediated the underlying flaw the same day. On September 14, the company confirmed that data had actually been taken and suspended its image delivery service as a precaution. On September 15, it reported the incident to Japan's Personal Information Protection Commission, the country's data protection regulator. The public notice followed on September 16.

The exposure itself is unusually large for a tool most executives have never heard of. Approximately 23.62 million user records were compromised, including names, email addresses, password hashes, user and device IDs, session IDs, OAuth tokens from connected accounts, profile data, and subscription and billing status. Helpfeel says payment card numbers were not among the exposed fields. Separately, roughly 490 million image metadata records — mostly tied to images uploaded through January 2019, plus another 2.4 million records obtained through more targeted access — were also taken. That metadata includes image IDs, the IP addresses used to upload them, EXIF location data embedded in the images, and, notably, OCR-extracted text pulled from the images themselves.

No attacker has been named publicly, and Helpfeel has not said how the vulnerability worked beyond describing it as a flaw in the image upload server. Both of those gaps are normal at this stage of an investigation and worth watching for updates, not treating as settled facts.

Why This Isn't Just a Consumer Privacy Story

It would be easy to read this as a story about a Japanese screenshot app and move on. That would miss the part that should worry a board.

Gyazo, like dozens of similar free tools, is not primarily a consumer product inside most companies that use it. It is shadow IT: software an employee downloaded because it made a task faster, without anyone in security or procurement ever evaluating it. Engineers use tools like this to quickly share a screenshot of an error message. Support staff use them to document a customer issue. Salespeople use them to share a snippet of a dashboard. None of that shows up on a vendor risk register, because as far as the organization's formal records are concerned, the tool does not exist.

The OCR detail in this breach is what turns that convenience into exposure. A tool that automatically extracts and indexes the text inside every image it stores has effectively built a searchable archive of whatever people put in front of their screen when they hit the capture button — internal URLs, error messages that might contain system details, snippets of customer data, sometimes credentials visible in a terminal window. None of that was the point of the breach. It is simply what accumulates when a tool nobody vetted becomes part of how work actually gets done, at a scale of 490 million images.

This is the compliance-versus-security gap in miniature. A company can pass every audit on its approved software list and still have no idea what its employees are actually uploading to unapproved tools every day. The list being clean is not the same as the exposure being small.

The Three Questions This Raises for Your Board

This is where the Three Questions framework I write about in Cyber Risk Is Business Risk earns its keep — not just for a named vendor, but for the tools nobody named at all.

Exposure: Do we actually know what free or unapproved SaaS tools our employees use to move company information around — screenshot tools, file converters, transcription apps, quick-share utilities? Most organizations don't, and that answer is itself the finding.

Response: If a tool like this were breached tomorrow, would we even know our people used it, or would we find out from a headline, the way most companies affected by this breach probably will?

Validation: For the tools we do know about, have we actually looked at what employees upload to them — not to police behavior, but to understand what would be exposed if the vendor had a bad month?

What to Ask Your CISO This Week

  • Do we have any visibility into unapproved or free SaaS tools employees use for screenshots, file sharing, or quick document conversion?
  • Is there a process for employees to request approval for a tool they've started relying on, or does shadow IT only get discovered after an incident?
  • For the tools already on our approved list, do we know whether any of them extract and index text or metadata from what employees upload — and where that index lives?
  • If Helpfeel's notification email lands in an employee's inbox this week, do we have a way to even know that happened?

Nobody is going to get fired over a screenshot tool. But the pattern behind it — a useful, invisible piece of software quietly holding more of the company's information than anyone realized — is the same pattern behind a lot of the breaches that do end careers. The tool that gets you is rarely the one on the list.