Products Lemma APIProof issuance & verification platformTrust402Delegate to agents, and transactSealSign-in for the agent era — no keys handed over
Use cases Manufacturing & Critical InfraInspection Record AssuranceFinance & FinTechCounterparty Record VerificationPublic SectorCertificate-less ProceduresHealthcareQualified Worker AssuranceProcurement & Supply ChainSupplier Credential MonitoringMedia & ContentContent AuthenticityService & RetailCross-group IdentityAI Adoption (cross-industry)AI Run GovernanceDevelopers & Agent OpsAgent Authority Control ▸ Browse the use-case index
Pricing
Resources Critical BriefThe frontier of AI × trustBlogThinking and implementation notesDocumentationAPI & specsVerification CenterReal verification & issuance countsAbout usFRAME00, Inc.ContactSales & press inquiriesGlossaryDefinitionsFAQFrequently asked questions
Dashboard ↗ JA
Home / Critical Brief / No. 194
No. 194 Critical Brief · Regulatory Attribute Proof

Club Tourism: Unauthorised access to a reservation system server may have leaked online members' records, including emergency contacts (company disclosure)

About 4.32Mrecords
Online members' records that may have leaked (company's first notice). Customers who never registered as online members are not affected
9fields
Fields concerned: name, nationality, sex, date of birth and age, address, phone, email, member ID and emergency contact. Passwords, passport, card and bank account data are not included
10-30 05:45→10-31
From detecting the unauthorised access from outside and blocking the traffic to the first notice (company's first notice)
CountryJapan
Incident date2026-10-30
Published2026-11-08
Revised v1.1 · 2026-11-09
AuthorsLemma Critical Team
Contents
  1. 01Summary
  2. 02What got through
  3. 03Pre-execution check
  4. 04What Lemma does
  5. 05Facts and timeline
  6. 06Sources

Summary

  1. 01What happened

    At 05:45 on 30 October 2026, Club Tourism detected unauthorised access from outside to part of its servers (the company’s first notice). After blocking the traffic and investigating, it confirmed that some of the online members’ data registered in its online reservation system may have leaked. About 4.32 million records are concerned.

  2. 02What was found

    The fields are name, nationality, sex, date of birth and age, address, phone number, email address, member ID and emergency contact. Login passwords, passport data, credit card data and bank account numbers are not included. The company says it identified and fixed the intrusion route and method, but has not disclosed what they were. It took its website down, consulted the police, and reported to the Personal Information Protection Commission and its supervisory authority.

  3. 03Why it got through

    Member data in a reservation system, the member’s own and other people’s contact details alike, can be taken in a single access unless the read is checked against a request.

Exhibit 1Detection vs pre-execution check

A pre-execution check means checking a read of member data against the record of work requests before it runs, and keeping a record. Detection means noticing the unauthorised access and blocking the traffic. Dates rely on the company's first notice and the parent company's disclosure.

Pre-execution check · not known from the disclosuresCheck a read of member data against the record of work requests before executing it
What was confirmedAbout 4.32 million records may have leaked
Emergency contacts included
Detection · workedUnauthorised access detected, traffic blocked, server isolated
10-30 05:45
Unauthorised access detected; traffic blocked
10-30
Server isolated; website taken down
10-31
First notice (about 4.32 million records)
11-01
Parent company KNT-CT discloses

What got through

What got through
Unauthorised access from outside to part of the servers, and a read of online members’ data (company’s first notice). The company says the data “may have” leaked; it does not say that removal was confirmed.
What reached the accepting side
In general, a reservation system server receives only the connection’s authentication and the read command. It does not receive which task the read serves: processing a booking, sending notices or handling an enquiry. The member’s own data and the emergency contact the member registered (another person’s contact details) are read together as one member record.
Not disclosed
The intrusion route and method (the company says it identified and fixed them). When the unauthorised access began and how long it lasted. Whether removal was confirmed and what was actually taken. How many people other than members are in the emergency contacts. The role of the affected server (which part of the reservation system).

Pre-execution check

Whatever the route, the condition for telling them apart is that, before member data is read, the read is checked as resting on a specific reservation or notification task, against a record of work requests kept apart from whether the server connection is allowed.

Pre-execution gate
Before member data is read, check which reservation or notification task the read is for, against the record of work requests rather than whether the server connection is allowed.
Who approves
The side that uses member data for its work (booking, notices, enquiries). For each task it sets the scope of reads (which members, which fields, how many records) and issues requests in a form that anyone able to connect to the server cannot produce.
Where it is checked
The step in the reservation system that accepts and executes a read of member data. Even when the connection is allowed, a read not tied to the record of requests, or beyond the scope, is held. Fields about other people, such as emergency contacts, are returned only to requests for tasks that need them during the trip.
What is recorded
Who read which member’s which fields under which request. It is kept apart from the reservation system, so that the scope of a leak can be established and the members and their emergency contacts informed.

Detection worked: the company blocked the traffic and isolated the server. Even so, about 4.32 million records may have leaked. Cases where large volumes of member data were taken through unauthorised access to a system managing it include Sourcenext (a member-data API) and Comic Cmoa. A case where the retention of former customers’ data was found at fault is Free Mobile, and one where customer files sat in a public storage area is GMO Trust Login. Here, the data of people other than the members, the emergency contacts they registered, fell within the same scope.

What Lemma does

Lemma builds the pre-execution check into the side of the reservation system that accepts and executes reads of member data. It does not look for unauthorised access; it checks, before execution, that a read rests on a booking or notification task.

Industries and operations to watch

IndustryRetail & services
Travel, hospitality and event businesses whose membership reservation systems also hold contact details of people other than the member, such as emergency contacts and travel companions. Member counts are large, and one read can cover a wide scope.
OperationData access
Reads and exports of member data.
OperationAccounts & permissions
Rights to connect to servers and admin consoles, and management of connection sources.

Current controls vs Lemma

The route in this case is column 1 (unauthorised access to the server from outside), though the intrusion route and method have not been disclosed. Column 2 covers a takeover of a staff member’s account, and column 3 removal by an insider within their rights; nothing disclosed says either happened here.

Control Unauthorised access to the server from outside Takeover of a staff account Removal by an insider
Restricting connections from outside (source restrictions and the like) Partial Not effective Not effective
Multi-factor authentication on staff logins Not effective Effective Not effective
Detecting and blocking unauthorised access Partial Partial Partial
Lemma (pre-execution check) Effective Not effective Effective

Restricting connections from outside narrows the entry point, but the intrusion route here has not been disclosed, so which entry was used is unknown. Multi-factor authentication protects a person’s login but is often absent on direct server connections. Detection and blocking worked here, but after the read (the possibility of a leak remained). Lemma checks, before execution, not whether the connection is allowed but whether the read rests on a work request.

Note: Lemma’s check works only when it is built into read execution in the reservation system and the record of work requests is managed apart from the rights to connect to the server. If the server is breached and the database read directly, data can be read without passing this check. The route here has not been disclosed, and it cannot be said that this mechanism would have stopped it. The table compares what each control checks; it does not show whether this incident would have been stopped. Lemma does not detect or prevent intrusions, and it does not recover leaked data.

CheckChecklist

Three things to confirm about reservation and membership systems

  • Have you decided which fields about people other than the member (emergency contacts, travel companions) you hold, and for how long?
  • Do you record reads of member data tied to booking or notification requests, with limits on record counts and fields?
  • After unauthorised access, can you establish from your own records which members’ which fields were read?

Facts and timeline

Party
Club Tourism Co., Ltd. (travel; a group company of KNT-CT Holdings).
What happened
According to the company’s first notice, on 30 October 2026 unauthorised access from outside to part of its servers meant that some of the customer data it holds may have leaked. The data concerned is that of online members registered in its online reservation system: name (kanji and kana), nationality, sex, date of birth and age, address, phone number, email address, member ID and emergency contact, about 4.32 million records. Login passwords, passport data, credit card data and bank account numbers are not included, and customers who never registered as online members are not affected.
How it was found
At 05:45 on 30 October, the company detected unauthorised access from outside. It began investigating at once, blocked the traffic at the affected point and put the necessary security measures in place.
Impact and response
It isolated the affected server and blocked traffic from the attack source. It says it identified the intrusion route and method, fixed the problem, and checked the scope of impact and for similar events. It took its website down to prevent further harm and to investigate (to be restored once safety is reconfirmed). As of 31 October, no specific secondary harm attributable to the incident had been confirmed. It consulted the police and reported to the Personal Information Protection Commission and its supervisory authority. It will contact affected customers in turn.

Glossary
Online member — A member registered in the company's online reservation system, with the name, contact details and date of birth used for booking tours and sending notices.
Emergency contact — The person to contact if the member cannot be reached during a trip. The name and phone number registered belong to someone other than the member, such as a family member.

Timeline

  • At 05:45, unauthorised access from outside is detected. Traffic is blocked and the server isolated. Further investigation confirms that some customer data may have leaked. The website is taken down.
  • First notice (about 4.32 million records; fields concerned and excluded; no secondary harm confirmed; police consulted and authorities notified).
  • The parent company, KNT-CT Holdings, discloses the incident as a personal data leak through unauthorised access at a group company and says it will strengthen its management of group companies.

The facts rely on Club Tourism’s first notice (31 October) and KNT-CT Holdings’ disclosure (1 November), both primary. The company says the data “may have” leaked; it has not disclosed whether removal was confirmed, the intrusion route and method, the duration of the access, or the server’s role. The first notice says only that the website is “currently” down, so this Brief places the shutdown on the day of detection. What has not been disclosed does not mean there were no controls. This Brief does not evaluate the company’s response. Written as of 5 November.

After disclosure

  • Club Tourism: Is contacting affected customers in turn. It says it will never ask customers, by phone, email, SMS or post, for card numbers, bank account details, PINs, IDs and passwords or My Number in connection with the incident, and warns of suspicious contacts. It recommends changing any password reused on other services and enabling multi-factor authentication. It opened a dedicated help desk, open on weekends and holidays through November.
  • KNT-CT Holdings: Says it will strengthen its management of group companies.

Sources

  1. Primary, company disclosureClub Tourism「不正アクセスによる個人情報漏えいに関するお詫びとお知らせについて (第1信)」2026-10-31 · club-tourism.co.jp/jpn/news/2026/1031
  2. Primary, parent company disclosureKNT-CT Holdings「グループ会社における不正アクセスによる個人情報漏えいに関するお詫びとお知らせ」2026-11-01 · kntcthd.co.jp/ja/release/2026/20261101

References: “The last layer left in AI-era cyber defense”

The same method elsewhereSee all 28 "Lookup & data access" cases

This Brief sets out, from disclosed facts, what organisations in a similar position can check. It is not guidance on individual losses or procedures.

This material is a structured analysis of public information; it is not an audit, diagnosis, or recommendation for any specific organization.

Cite this Brief

Lemma Critical Team. (2026).
"Club Tourism: Unauthorised access to a reservation system server may have leaked online members' records, including emergency contacts (company disclosure)".
Lemma Critical Brief No.194. Lemma / FRAME00, Inc.
https://lemma.frame00.com/critical/briefs/194-club-tourism-member-data-emergency-contacts/
Read nextNext
All Briefs →
Revision History

Current version: 1.1

Lemma

If it can't be verified,
it doesn't enter your operation.

Lemma is a pre-execution check: logins, payments, records and publishing that look genuine are checked before they run, with cryptographic proofs the receiving side verifies without asking the issuer. Detection stays; the check sits in front of it.