What was exposed
Tabiq exposure
- 1
Guest images stored
May 2026Tabiq stored hotel guests’ identity documents and verification photos in a publicly accessible S3 bucket.
- 2
Public access verified
May 2026A researcher reported that a web browser could retrieve identity documents and verification photos without a password.
- 3
Found and closed
By May 15, 2026Reqrea closed public access after TechCrunch contacted the company and Japan’s cybersecurity coordination center, JPCERT.
Impact
More than one million images were exposed, including passports, driver’s licenses and verification photos. Reqrea’s investigation found no confirmed misuse. The number of people represented is unknown.
Could this have been prevented?
Keep guest identity images private in S3
If guests can submit and retrieve documents through the check-in application, enable all four S3 Block Public Access settings on the guest-image bucket. The application can use authorized access while S3 refuses public access through bucket policies and access-control lists.
Incident control assessments
- 1
- Prevented
- 1
- Contained
- 1
- Not covered
How it could have been prevented
The same replay with the controls in place. Green marks where a step is refused, blue where it is bounded, and red where no control reaches it. Open a row to read the control, why it acts, and its caveat.
Tabiq exposure
1 · Guest images stored
1 Prevented2 · Public access verified
1 Contained3 · Found and closed
1 Not coveredKey facts
- Reqrea discovered the exposure on May 13 and blocked outside access by May 15.
- Anurag Sen reported that the images were accessible without a password. TechCrunch contacted Reqrea and Japan’s cybersecurity coordination center, JPCERT.
- The exposed files included facial photos, signatures and identity documents. Reqrea said credit card information was outside the exposed data.
- The operator’s independent investigation found no confirmed external disclosure or subsequent misuse. TechCrunch’s count of more than one million refers to images.
Sources
Every fact in this breakdown comes from the public reporting below. The replay is a model of that reporting, not a reconstruction of the environment it describes.
- 1.Notice of Data Security Incident Regarding Our Check-in SystemReqrea · Sep 17, 2026 · Vendor reportThe operator’s English report dates discovery to May 13 and closure to May 15 at the latest. It identifies the exposed images and reports the findings of its independent investigation.
- 2.A hotel check-in system left a million passports and driver’s licenses open for anyone to seeTechCrunch · May 15, 2026 · NewsTechCrunch received the finder’s report, notified Reqrea and JPCERT, and reported that public access was closed. Reqrea’s director acknowledged the exposure in an email to the reporter.
- 3.Blocking public access to your Amazon S3 storageAWS · undated · Vendor reportBucket-level public-access blocks, policy and ACL enforcement, and the combined effect of more restrictive settings.
- 4.Resource control policiesAWS · undated · Vendor reportScope of effective denies for supported member-account resources and service exceptions.
The estate in the replay is illustrative and drawn at the level of the exposure; the owner's real environment is not public. Verdicts describe what a control does when it is in place before the data is exposed. They are not an assessment of the owner's security program.