---
title: "Skyticket Discloses Breach Hitting 14.64 Million Customers"
date: "2026-10-12"
author: "Ahsan Luqman"
canonical_url: "https://aliasfleet.com/blog/skyticket-data-breach"
tags: ["Data Breaches", "Privacy", "Email Aliases"]
description: "Skyticket disclosed three intrusions exposing about 14.64 million records, the biggest travel breach of October's wave. The bus flaw leaked full itineraries."
---

# Skyticket Discloses Breach Hitting 14.64 Million Customers

Skyticket disclosed three intrusions exposing about 14.64 million records, the biggest travel breach of October's wave. The bus flaw leaked full itineraries.

Skyticket's 14.64 million exposed records are the biggest travel-site slice of Japan's October breach wave, and booking records are the most weaponisable breach file there is: this one pairs travel plans with contact details and partial financials. Adventure, the company behind the booking site, disclosed three separate intrusions on Friday. I run [AliasFleet](https://aliasfleet.com), an email-alias service: one forwarding address per site, so a leak names its source. The sharpest edge of the disclosure is the bus-booking incident, where about 12,000 reservations sat viewable without logging in for almost two months, itineraries and all.

## Three intrusions, one notice

Adventure's notice, dated 9 October, was carried in full by [ABEMA TIMES](https://news.yahoo.co.jp/articles/4d84b62a2c605b147889fd1e18d7249c22e9a7d2), with [Reuters](https://www.reuters.com/jp/world/japan/OICG5G6XQNNYJKVOXJDDKZSKGI-2026-10-09/), [NHK World-Japan](https://www3.nhk.or.jp/nhkworld/news/20261009de57465/) and [TRAICY](https://en.traicy.com/posts/2026100941030/) reporting the disclosure. The honest split:

| Confirmed | Still unconfirmed |
| :--- | :--- |
| The disclosure: Adventure announced three intrusions itself on 9 October | Which admin function was misused in the server intrusion |
| Server intrusion: Oct 2 to 4, found Oct 5; attackers used admin functions to reach other servers and cloud-stored data | Whether the 14.64 million records were taken or only accessed |
| About 14.64 million records: names (including passport romanisation), DOB, emails, phones, postal codes, addresses, bank remitter names, hashed login passwords; about 4.13 million include passwords | Which algorithm protects the 4.13 million hashed passwords |
| Business management system intrusion: Sep 20, found Sep 28, via a system vulnerability; 17,780 records (duplicates included) with refund bank details: institution, branch, account type, number, holder name | Whether the 17,780 count grows as the investigation continues |
| Bus booking flaw: Aug 3 to Oct 1, found and fixed Oct 1; about 12,000 reservations viewable without login, itineraries and companions' details included | Whether the dataset has surfaced publicly or is being traded |
| One member account was logged into without authorisation on Sep 9 | Passport numbers: cleared for the server intrusion, still being checked for the management system |
| No credit card numbers or passport images are stored, so neither leaked in any incident | |

Note the company's own framing: "leaked or may have leaked" for the first two incidents. Only the bus incident is described as actually viewed. Two things deserve plain language on top of that. The passwords are hashed but Adventure names no algorithm, so treat the 4.13 million as crackable rather than safe. And passport numbers were confirmed not leaked in the server intrusion, yet names are stored in passport romanisation, so whoever holds the file can match a victim to their passport without the number.

## A travel plan is a phishing kit

The bus reservation flaw exposed booking dates and times, boarding and alighting stops, the operator, the bus name, the operator's booking number, payment method and amount, plus the names, ages and genders of everyone travelling with the booker. That is not an identity file. It is a calendar with contact details stapled to it.

Picture the call. A scammer knows you board a bus on Friday evening, which means they know your flat is empty on Friday evening. They know the operator's name and the booking number, so the call "from the bus company" about a schedule change opens with facts only a real company should have. Then the second intrusion completes the picture: 17,780 records carrying refund bank account details, institution and branch names, account numbers and holder names. A caller who can recite your trip and your bank account does not sound like a stranger. That is the whole trick.

This is why booking records are the most weaponisable breach file there is. Contact lists get you spam. Travel plans get you believed.

<Callout type="warning" title="Do not click any Skyticket email">
Adventure is notifying victims by email, and it names fraudulent emails asking for passwords and card numbers as the threat. A real notification and a forged one will carry identical content, because the forger holds the same customer file. Open skyticket yourself and type the address. No link in any email about this breach is worth clicking, including the real one.
</Callout>

## Counting the October wave

The [Japan Times' Oct 10 roundup](https://www.japantimes.co.jp/business/2026/10/10/tech/japanese-firms-data-breaches/) lists JR East at 6.09 million accounts, Bookoff at up to 6.43 million, Daiichi Kosho at 8.72 million karaoke records, and Adventure at 14.64 million: the largest single disclosure of the lot. [Lawson's 2.15 million member records](https://www.aliasfleet.com/blog/lawson-data-breach) were confirmed the same week, and [Daiichi Kosho's contractor-side incident](https://www.aliasfleet.com/blog/daiichi-kosho-data-breach) showed the wave reaching beyond the brands themselves. Among travel companies the gap is wider still: the [Japan Times' Oct 9 travel roundup](https://www.japantimes.co.jp/business/2026/10/09/tech/travel-companies-data-breach/) puts H.I.S. at passport information for up to 627 people via its Thailand subsidiary, with [Temairazu](https://www.aliasfleet.com/blog/temairazu-data-breach) in the same batch. Skyticket stands alone.

The pattern across the wave keeps repeating. Personal data collected for a booking, a loyalty account or a membership ends up reachable through systems the customer never sees. Adventure just did it three ways at once, across two months, including a booking page that sat open to anyone for almost two months.

## The only field you get to choose

The email address you gave skyticket is the one item in that 14.64 million you could have ring-fenced. A unique [email alias](https://www.aliasfleet.com/blog/what-is-an-email-alias) for the booking site, forwarding to your real inbox, changes what a forged notification can do: it arrives on an address nobody but skyticket ever had. The [leak-tracing mechanism](https://www.aliasfleet.com/blog/which-website-leaked-my-email) means a phishing email on that alias identifies its own source. The [set-up guide](https://www.aliasfleet.com/blog/how-to-set-up-an-email-alias) takes about two minutes.

An alias would not have kept your itinerary out of the file. Nothing you typed into the booking form could do that. What it does is contain the contact channel, so the notification forgeries and the "schedule change" calls land on an address you can kill without touching your real inbox.

## If you booked through Skyticket

1. Change your skyticket password now, and change it everywhere else you reused it. 4.13 million hashed passwords will be attacked, not read. If yours matches another site, that site is in play too.
2. Check your reservation history and your card statements. Adventure suspended saved-card payments on 7 October, but look for charges you did not make anyway.
3. Click no link in any email, SMS, call or letter about this breach. The genuine notification arrives by email, which is exactly the format the forgeries copy. Go to skyticket yourself.
4. Treat any caller quoting your trip as hostile. Schedule changes, refunds or rebooking that name your route, date or booking number are the specific shape of this breach's abuse. Any request for payment details ends the conversation.
5. If your bank details were in the refund records, watch for account movements you do not recognise and talk to your bank. Adventure itself flags unexplained deposits and withdrawals.
6. Check [Have I Been Pwned](https://haveibeenpwned.com/) once the incident is listed, and walk the [breach-response order of operations](https://www.aliasfleet.com/blog/what-to-do-when-your-email-is-in-a-data-breach).

## Scammers do not wait for the report

The open questions are the expensive ones. Whether the 14.64 million records were taken or only accessed. Which algorithm protects the 4.13 million hashed passwords, and how fast it falls. Whether the 17,780 management-system records grow, and whether the whole file surfaces anywhere public. Adventure will spend months answering them, one by one, while notifying victims by email about a breach whose main threat is forged emails. The investigation runs on company time. The impersonation will not.
