For: anyone who has booked a hotel or ryokan in Japan (including through a travel booking site), and anyone who runs an accommodation business. This article is based on Temairazu, Inc.'s official notice and on notices from hotels that use its system, and does not cover attack or scam techniques.
Final report published
- Who is affected
anyone who has booked a hotel or ryokan in Japan (including through a travel booking site), and anyone who runs an accommodation business.
- Confirmed so farSee the table ↓
- Unauthorized access
- Card data and booking-site logins
Listed as possibly affected
- Whether guest data was taken
- Not yet confirmed
- Number of hotels
- Period and range of bookings affected
- The specific method of intrusion (the company does not disclose technical details)
- What to do nowSee the steps ↓
- Know whether you could be affected (travel-site bookings included)
- Do not open links in the message, and do not reply
- Check through the booking site's official app or the hotel's official phone number
2 more
- If you entered details or paid, contact your card issuer immediately
- Tell the people traveling with you (messages in Japanese have appeared too)
- Where to verify (source)All sources ↓
- Temairazu, Inc., notice of apology regarding suspicious messages and unauthorized access to its system (September 28, 2026, Japanese)
- Last checked
- As of November 20, 2026
Follow-up plans and what we checked
On November 20, 2026 Temairazu, Inc. published the final report of the forensic investigation by an external security firm. The number of people whose information may have been viewed or obtained by a third party was revised from up to about 4.45 million to up to about 1 million. The company says it will keep working on support for hotels and guests and on preventing recurrence, and will promptly announce any new material facts.
What guests should do today
Know whether you could be affected (travel-site bookings included)
The company has not announced which period or range of bookings is affected. What is known is an upper bound of up to about 1 million people (final report of November 20; the October 9 timely disclosure said up to about 4.45 million). That covers not only people who booked directly with the hotel but possibly also those who booked through a travel site (the reason is explained further down).
A hotel's notice (Hotel Grand Hill Ichigaya) says fake WhatsApp messages were observed for some bookings that meet all three conditions: made by September 21, 2026, for a stay on or after September 21, and the guest uses WhatsApp. Those are the conditions under which fake messages were seen, not the range of bookings whose data may have been taken. Not meeting them does not mean you are safe.
Several hotels using the system have posted their own notices on their websites, so check your hotel's official site. A missing notice is not proof of safety, though. Handle every message claiming to be from a hotel with the steps below.
Do not open links in the message, and do not reply
The messages the company confirmed pose as hotels or booking sites and, under pretexts such as confirming a booking, advance check-in or keeping a reservation valid, lead recipients to external websites to enter card details or pay. They also push you to act urgently. According to the company's first notice, they arrived through messaging apps such as WhatsApp, by email, by SMS and by other means. The company asks for the same caution if a message arrives through WeChat or another messaging app.
The company gives four pieces of advice:
- Do not open URLs or links
- Do not reply
- Do not enter card or personal details
- Do not make a payment
Check through the booking site's official app or the hotel's official phone number
To check your booking, do not use the links or phone numbers in the message. Use an official channel you open yourself.
- If you booked through a travel site: open your booking from the app on your home screen (or the official site you bookmarked yourself) and look at the payment method and status
- If you booked directly: search for the hotel's official website and call the phone number listed there yourself
If you are asked for a payment that is not in your booking confirmation, that alone is reason enough to refuse. How to judge such messages is covered in detail in the Booking.com booking data breach.
If you entered details or paid, contact your card issuer immediately
The company says that if you entered credit card or other details on a suspicious website, you should contact your card issuer promptly. Ask for the card to be blocked and reissued, and check your statements for charges you do not recognize.
In Japan you can also call the police consultation line (#9110) or the consumer hotline (188). If you entered your booking-site password, change it and turn on two-step verification (see Choosing multi-factor authentication).
Tell the people traveling with you (messages in Japanese have appeared too)
Tell not only the person who made the booking but also family members staying with you and companions arriving from abroad. According to a hotel's notice, on October 5 scam messages in Japanese, not only English, were confirmed.
Do not assume an awkward English message is the only kind to expect. Whatever the language or app, check in the same way.
What happened (from Temairazu, Inc.'s notice)
Temairazu, Inc. published its first notice on September 28, 2026 (English version September 29) and its second report on October 7 (English version October 8), followed by a timely disclosure for shareholders and investors on October 9. Of the dates below, September 26 and the conditions of the bookings for which fake messages were observed come from notices published by hotels using the system.
Aug 26, 2026
According to the final report, an attempted access from outside was found (the intrusion itself was on September 21).From late at night on Mon, Sep 21, 2026
Several hotels contacted the company saying their guests were receiving suspicious messages. While investigating, the company confirmed unauthorized access to its system.Thu, Sep 24
To contain the damage and investigate, part of the system's functions was suspended at about 10:58 a.m. and resumed at about 9:48 p.m. the same day (October 9 disclosure). The company says the core engine linking bookings, inventory and rates was not stopped.Sat, Sep 26
According to hotels' notices, the cause was identified and the fix completed.Sep 28
The company published its notice. It said it was taking the required steps, including reporting to the Personal Information Protection Commission, and had contacted the police. According to the final report, it finished isolating the server where the intrusion was found on the same day.Sep 29
English version of the notice published.Oct 5
According to a hotel's notice, scam messages in Japanese, not only English, were confirmed.Oct 7
The company published its second report (English version October 8), listing names, phone numbers, email addresses, property names, check-in and check-out dates and charges as information that may have been taken.Oct 9
In a timely disclosure, the company put the number of people involved at up to about 4.45 million, said it had commissioned an external security firm, and said the effect on its earnings cannot yet be reasonably estimated.Nov 17
The company received the external security firm's final report (per its November 20 final report).Nov 20
The company published its final report and revised the number of people involved to up to about 1 million. It completed the submission of its final report to the Personal Information Protection Commission the same day.
- System
- TEMAIRAZU Series, a booking management system for accommodation
- What happened
- Unauthorized access to the company's system. Some guest information may have been viewed or obtained by a third party (company notice)
- People involved
- Up to about 1 million (final report of November 20; people whose information may have been viewed or obtained by a third party, not a confirmation that everyone's information was). The October 9 timely disclosure said up to about 4.45 million. The number of hotels has not been announced
- Items that may have been taken
- Guest names, telephone numbers, email addresses, accommodation property names, check-in dates, check-out dates, accommodation charges (second report). The October 9 disclosure lists them with "such as" and "including"
- Fake messages
- Pose as hotels or booking sites and, under pretexts such as advance check-in or keeping a reservation valid, lead to external sites asking for card details or payment. The company describes them as confirmed in connection with this incident and says they appear to be phishing scams
- Not held by the company
- Credit card information and booking-site login credentials (company notice)
- Cause
- The company says it identified and fixed the cause and will not disclose technical details. Its final report confirms that a third party abused part of the application's functions. According to hotels' notices (September), a security problem in part of the functions of an installed product that the company provided in the past
- Findings of the final report
- The intrusion was on September 21 (an attempted access from outside on August 26). No trace of administrator privileges being obtained and no malicious program planted for re-entry was found, and no new malicious activity has been found since September 21. The server where the intrusion was found was isolated on September 28
- Hotels' credentials
- The TEMAIRAZU admin-screen credentials of some hotels may have been obtained by a third party. The hotels concerned were told individually, and passwords were changed or invalidated
- Date of the intrusion
- According to a hotel's notice, the company reported that the unauthorized access confirmed so far is limited to access that occurred on September 21, 2026, and that no similar access has been confirmed at any other time
- Response
- Access blocked; access control and monitoring strengthened. Part of the functions was suspended for about 11 hours on September 24 and resumed the same day; the system is operating normally (company notice)
- Reporting and investigation
- Reported to the Personal Information Protection Commission (final report submitted on November 20) and consulted the police. The external firm's forensic investigation ended with the final report of November 20; support for hotels and guests and recurrence prevention continue
- Recurrence prevention
- Isolating the intruded server; fixing programs and improving how information is recorded; changing or invalidating credentials that may have been affected; promoting two-step verification and strengthening the authentication base; strengthening vulnerability assessment and detection and monitoring; reviewing how logs are collected, kept and analysed
- Contact
- The company's emergency help desk (helpdesk@temairazu.com, as given in its official notice)
What is known and what is not
Status as of November 20, 2026 (up to the final report of November 20). This table will be updated when the company publishes more.
| Item | What has been announced | Status |
|---|---|---|
| Unauthorized access | Confirmed on the company's system | Confirmed |
| Whether guest data was taken | May have been viewed or obtained | Possible |
| Items that may have been taken | Names, phone numbers, email addresses, property names, check-in and check-out dates, charges (second report; the October 9 disclosure says "including") | Announced |
| Card data and booking-site logins | The company does not retain them | Confirmed |
| Period and range of bookings affected | Not stated by the company (only the upper bound on the number of people) | Not announced |
| Bookings where fake messages were seen | Some bookings meeting all of: made by Sep 21, stay on or after Sep 21, guest uses WhatsApp (a hotel's notice) | Via hotels' notices |
| Date of the intrusion | The access confirmed so far is limited to September 21 (a hotel's notice, citing the company) | Via hotels' notices |
| People involved | Up to about 1 million (final report of November 20; the October 9 disclosure said up to about 4.45 million). Not a confirmation that everyone's information was viewed or obtained | Upper bound announced (revised) |
| Number of hotels | Not announced | Not announced |
| Link to the fake messages | The company describes them as confirmed in connection with this incident and as apparent phishing | Link described by the company |
| Cause | Identified and fixed; a third party abused part of the application's functions (final report); technical details not disclosed; part of an older installed product (hotels' notices) | Partly disclosed |
| Administrator privileges and re-entry tools | No trace of administrator privileges being obtained and no malicious program planted for re-entry was found (final report) | Not found (company) |
| Hotels' admin-screen credentials | Some may have been obtained; hotels told individually and passwords changed or invalidated (final report) | Handled (company) |
| Reporting to authorities | Reported to the PPC (final report submitted on November 20); consulted the police | Done |
| External investigation | Final report from the security firm dated November 17; the company's final report of November 20 closes the investigation | Completed (investigation) |
| Effect on earnings | Cannot yet be reasonably estimated | Not determined |
Why booking through a travel site does not rule you out
Most hotels and ryokan in Japan list their rooms on several travel booking sites (OTAs, online travel agencies) and on their own website at the same time. When a room sells on one site, availability on every other site has to drop, or the same room gets sold twice.
The system that does this automatically is called a channel manager (in Japan, a "site controller"). TEMAIRAZU is one of them; the company provides it as a booking management system for accommodation.
Booking site A
Guest books in the app
Booking site B
Guest books on the web
Hotel's own website
Direct booking
↓ bookings, availability and rates passed along together
Channel manager (TEMAIRAZU)
Booking data from multiple hotels gathers in one system → unauthorized access confirmed here
↓
Each hotel's admin screen
Handles guest contact details, stay dates, booking numbers
So even if the booking site itself has no problem, booking data can be taken from the management system the hotel uses. Not having heard from your booking site is not proof of safety.
What names, contact details and stay dates can be used for
The announced items combine contact details (name, phone number, email address) with booking details (property name, check-in and check-out dates, charges). In general, this combination makes good material for scams because:
- A correct hotel name, date and price makes a message look like it really came from the hotel or booking site
- When the stay is close, "pay now or your booking will be cancelled" or "advance check-in required" creates pressure
- With a phone number and email address, a scammer can reach you by SMS, email or a messaging app registered to that number while posing as the hotel
Because check-out dates are included, messages about a "refund" or "settling extra charges" may also arrive after your stay. Check those in the same way.
What stands out here: fake messages arrived before the announcement
According to the company, hotels began reporting suspicious messages from late at night on September 21, and the announcement came on September 28. Messages that arrived before the announcement need the same caution.
If you entered card details in response to a message claiming to be a hotel from late September onward, contact your card issuer now, even if some time has passed.
This site's view: judge by how payment is requested, not by whether the hotel name is right
With hotel bookings, the payment method almost never changes after you book. The payment terms are written in your booking confirmation.
However accurately a message describes your booking, if it asks for a payment that is not in the confirmation or for card details to be re-entered, that alone is reason to refuse. This rule works the same whatever app or language the message arrives in.
For people who run an accommodation business
What the company has asked hotels to do
Change your TEMAIRAZU login password
As a precaution, the company has asked hotels to change their TEMAIRAZU login password. In its final report of November 20 it says the admin-screen credentials of some hotels may have been obtained by a third party, and that it told those hotels individually and changed or invalidated the passwords. If you use the same password on other admin screens (booking-site extranets, email and so on), change those too.
Check the admin screen for logins or changes you do not recognize
The company asks hotels to contact it immediately if they find logins they do not recognize or unintended changes to registered details on the admin screen.
It has asked booking sites and connected partners to check for unrecognized logins, unintended changes to accounts or permissions, unintended changes to payout bank accounts or other registered details, and suspicious messages or activity logs. Checking the same four points on the booking-site extranets your property uses is a sensible step too.
Give guests the same answer every time
The company asks hotels to tell guests who inquire not to open URLs in the messages and not to enter personal or card details.
So that front desk and call-center answers do not vary, settle on one sentence, such as "We never ask you to re-enter card details or pay through a message", plus the correct contact details. Telling upcoming guests in advance, for example through the booking site's messaging feature, reduces harm.
What to ask Temairazu, Inc.
The company's notice does not say which hotels' bookings are in scope. To explain the situation to guests and decide on legal steps, ask the company:
- Whether your property's bookings are in scope, and if so the period and number
- Which of the announced items actually apply to your property's bookings
- Whether your property ever used the older installed product, and whether that software or its connection settings remain
- How far the company has reported to the Personal Information Protection Commission, and whether your property also needs to report or notify guests
Reporting to the Personal Information Protection Commission and notifying guests
According to Japan's Personal Information Protection Commission (PPC), a leak that may have been caused with wrongful intent, such as unauthorized access, must be reported regardless of the number of people. The time frames are:
- Preliminary report: promptly after becoming aware (roughly within 3 to 5 days)
- Final report: within 60 days (where wrongful intent is suspected; otherwise 30 days)
- Notice to the people affected: promptly, as the situation allows. Where that is difficult, alternatives such as publishing the incident and setting up an inquiry desk are accepted
Under the PPC's guidelines, if an entrusted service provider notifies the business that entrusted it with the data, the provider is exempt from reporting and the entrusting business reports. Whether the hotel or the system provider reports, and whether your property is in scope, depends on the contract and the facts. Base the decision on the answers to the questions above, and consult the PPC if unsure.
The check specific to this incident: old products and connections still in place
According to hotels' notices, the cause was part of an installed product the company provided in the past. Where that function sat has not been disclosed, but any property can end up with old software it thinks it no longer uses, or connection settings for it, still in place.
- List every system that handles bookings or guest data, and write down for each: current version, who manages it, and whether old versions or integrations remain
- Uninstall old products you no longer use after checking with the provider, and close related accounts and connections
- Turn on multi-factor authentication for admin logins if available, and replace shared IDs with individual ones (so login history shows who did what)
The other lesson is about detection. Here, the problem first surfaced as guests asking hotels about strange messages. Decide in advance that a guest report of "a suspicious message claiming to be from your hotel" is not just an individual complaint and goes straight to the system provider.
For another case where hotel guest data leaked, see the Quest Apartment Hotels breach in Australia; for how customers can respond when a provider's system is breached, see When your web hosting provider is breached.
Sources (public record)
The facts in this article are based on the public information below. Items, numbers and intrusion methods that have not been announced are not guessed at.
- Temairazu, Inc., notice of apology regarding suspicious messages and unauthorized access to its system (September 28, 2026, Japanese) — temairazu.co.jp
- Temairazu, Inc., "Notice and Apology Regarding Suspicious Messages and Unauthorized Access to TEMAIRAZU" (September 29, 2026, English) — temairazu.co.jp
- Temairazu, Inc., second report on the unauthorized access (October 7, 2026, Japanese) — temairazu.co.jp
- Temairazu, Inc., "Update on Unauthorized Access to Our Systems and Our Response (Second Report)" (October 8, 2026, English) — temairazu.co.jp
- Temairazu, Inc., timely disclosure on the status of the investigation into unauthorized access to its system and its response (October 9, 2026, Japanese) — temairazu.co.jp
- Temairazu, Inc., report of the investigation results into unauthorized access to its system (final report) (November 20, 2026, Japanese, PDF) — temairazu.co.jp
- Example of a hotel's notice (cause, the September 26 fix, date of the intrusion, conditions of bookings where fake messages were seen): Hotel Grand Hill Ichigaya (September 29, 2026, Japanese) — ghi.gr.jp
- Example of a hotel's notice (Japanese-language scam messages on October 5): Super Hotel (updated October 5, Japanese) — superhotel.co.jp
- Personal Information Protection Commission, "Responding to leaks and useful materials" (Japanese) — ppc.go.jp
- Personal Information Protection Commission, Guidelines on the Act on the Protection of Personal Information (General Rules), section 3-5 on leak reports and notice to individuals (Japanese) — ppc.go.jp
Update history
2026-11-20: Reflected the company's final report (November 20). Revised the number of people involved from up to about 4.45 million to up to about 1 million, and added the course of the intrusion (an attempt on August 26, intrusion on September 21, isolation on September 28), the cause (abuse of part of the application's functions), that no administrator privileges or re-entry programs were found, the possible exposure of some hotels' admin-screen credentials, the final report to the Personal Information Protection Commission and the recurrence-prevention measures. Warnings about fake messages (WhatsApp, email, SMS and so on) continue.
2026-10-22: In Read next, described the Commune figure of 166,505 as counted per community.
2026-10-11: Rechecked the facts against the official notices. The conditions in a hotel's notice (made by September 21, stay on or after September 21, guest uses WhatsApp) describe the bookings for which fake messages were observed, not the scope of the leak, so the text was corrected (the company has not announced the scope). Added that the confirmed unauthorized access is limited to September 21 (hotel's notice). Aligned the message channels with the first notice (messaging apps such as WhatsApp, email, SMS and others).
2026-10-10: Reflected the company's October 9 timely disclosure: up to about 4.45 million people involved, the partial suspension and same-day restart on September 24, the external security firm commissioned to investigate, and the effect on earnings (not yet estimable), in the title, body and table. The number of hotels and the intrusion method remain undisclosed.
2026-10-09: Reflected the company's second report (October 7; English version October 8): the seven items that may have been taken, information the company does not retain (booking-site logins), and the pretexts used in fake messages (advance check-in, keeping a reservation valid). Numbers and the intrusion method remain undisclosed.
2026-10-07: Official notice rechecked (no update). Added the "what is known and what is not" table, the Japanese-language scam messages of October 5, and hotels' reporting and notification steps. Because the company has not announced which items leaked, the description of items was narrowed to what the company's notice says.
2026-10-03: First version, based on Temairazu, Inc.'s notices of September 28 (Japanese) and September 29 (English) and on notices from hotels using the system.
Read next
- Another platform-provider incident that may have exposed client organisations' data: Pokepay (Enterprise) unauthorized access
- The same scam pattern: The Booking.com booking data breach / What is phishing?
- Another accommodation case: Quest Apartment Hotels (Australia, card and passport numbers)
- A travel booking site case: the skyticket (Adventure Inc.) breach (bookings and passwords)
- A travel booking site case: Rakuten Travel unauthorized access (overseas hotel bookings, up to about 2.6 million records)
- When a provider is breached: When your web hosting provider is breached
- Contact details leaked through a vendor: JR East, VIEW Card and JR Kyushu email address leak
- Member data of many companies leaked through one provider: Unauthorized access to Commune (166,505 community members, counted per community)
- Protecting your accounts: Choosing multi-factor authentication / Choosing a password manager
- Other 2026 incidents: list of breaches and cyberattacks (Japan and worldwide)