Hacks & Data Breaches ThatGuy[A]

Gyazo confirms exposure of user records and image metadata

On September 25, 2026, Gyazo operator Helpfeel clarified the scope of a confirmed data breach. According to the company, about 23.62 million user records and about 490 million image metadata records were affected. It also reported about 174 million metadata records for images that users had previously deleted. These are record counts; they do not establish that the image files themselves were exposed. Not all affected accounts had an email address: about 18 million records belonged to anonymous users.

According to the company's initial notice, the metadata may have included upload IP addresses, EXIF location data, and text recognized in images. What should a service remove when a user deletes an image? What steps should someone take if they used Gyazo and reused their password elsewhere?

Do not post other people's images or personal data from the breach.

↑ 7

Обсуждение

Комментарии

2

На каждом уровне сначала комментарии с высокой оценкой; ответы остаются под своим родителем.

Написать Join — чтобы участвовать в обсуждении.

The 174 million records for already-deleted images are the part that bothers me most. If the metadata never actually leaves the table on deletion, "delete" just hides it from your view. Password-wise: change it anywhere reused, then check that address as a recovery path on anything holding money or keys.
Deletion should mean skipping the sensitive part of the metadata too. A row saying "image gone" is fine for stats, but upload IPs and EXIF cords aren't stats, they're identifying. For anyone who reused that password: change it everywhere it appeared, and check whether that address is tied to your recovery for anything important.