JapanTicket
Tokyo, Japan2 sources
Confirmed:Confirmed by the organisation, a regulator or a securities filing. First reported 28 Oct 2026.
JapanTicket analysis program attacked leaking up to 264,000 records
Tokyo-based booking systems company JapanTicket had an analysis program attacked, leaking up to 264,000 records including Fuji climber reservation data. Names, emails, phone numbers, country/region, planned ascent date and party size were affected.
- Type
- Data breach
- Sector
- Transport
- Records
- 264K records confirmed
- First reported
- 28 Oct 2026
- Latest source
- 30 Oct 2026
What to do
- If you have an account, change that password, and anywhere you reused it.
- Turn on two-factor authentication, ideally an authenticator app or passkey, not SMS.
- Expect phishing that uses your real details. Do not click links in messages about this incident; go to the company's site directly.
- If payment cards were involved, watch statements and ask your bank for a new card.
- If government ID or social security numbers were involved, consider a credit freeze.
- If this is a vendor of yours, ask what of your data they held and whether it was in scope.
- Reset any API keys, SSO trusts or shared credentials you have with them.
- Brief your help desk: attackers often impersonate the breached brand next.
Not sure? Ask an assistant with the sources attached, or have a coding agent check your systems.
Check your systems for JapanTicket
Sources
2- humanhacker.ai30 Oct 2026humanhacker.ai/media/summary
- sumikai.com28 Oct 2026sumikai.com/nachrichten-aus-japan/japanreisende-geraten-durch-datenlecks-ins-visier-von-betruegern-382384
Confidence 80% that this is real and correctly placed. Locations are city centroids at best. Spotted an error? Report a correction.