Keisei Skyliner data breach may have exposed 3.37M records
Part of the Keisei Electric Railway story · since 18 Nov
- Wed 18 Nov, 05:42 UTC. cybersixt, first report. Keisei Skyliner data breach may have exposed 3.37M records. This article, 1st of 1.
Keisei Electric Railway, which runs the Skyliner airport express between central Tokyo and Narita Airport, says a third party broke into the Skyliner seat reservation system late on Wednesday 11 November and may have taken customer information from its Skyliner Ticketless Service and Skyliner e-ticket service. In a notice first published on 13 November and updated on 16 November, it puts the number of records at up to about 3.37 million. The information listed is user IDs, passwords, names in katakana, phone numbers, email addresses, dates of birth, gender and nationality. Keisei says the passwords were hashed, so they "cannot be recovered by the third parties". It posted an English version of the notice on 18 November.
Keisei says it will email affected customers at their registered addresses at a later date. The notice does not say whether data was confirmed taken, only that it may have been, and it does not mention payment card data.
Online booking is still down
Keisei had already suspended its online Skyliner services on 12 November "to conduct maintenance for the purpose of enhancing the security of the relevant services", according to a separate notice. The suspension covers the Skyliner Ticketless Service, Skyliner e-ticket, the e-ticket's face check-in system and Skyliner ticket sales through travel agencies, and the whole reservation system was still suspended in the 16 November notice. Skyliner tickets are still sold at station ticket windows and ticket machines. Customers who had already bought through the suspended services must buy a new ticket at the station and tell station staff they had used those services; Keisei says it will refund the original purchase later and that credit card refunds may take some time.
What customers should do
Anyone who has used the Skyliner Ticketless Service or e-ticket should expect phishing emails, messages and calls that use their name, phone number, email address or nationality, and should not follow links or give details in unexpected messages that claim to come from Keisei or a travel agency about refunds. Keisei has not said which hashing method protected the passwords, so anyone who used their Skyliner password on another site should change it there.
What is not known
Keisei has not said how the attacker got into the reservation system, how it found the intrusion, whether the 3.37 million records correspond to fewer individual customers, or when online booking will resume. Its notice does not list face data from the e-ticket face check-in system among the information that may have been taken, and it has not said whether that system was affected.
How the story developed
1 article from 1 outlet since 18 Nov. Still developing; the latest report was 13 hours ago. This was the first report.
- Wed 18 Nov, 05:42 UTC. cybersixt, first report. Keisei Skyliner data breach may have exposed 3.37M records. This article, 1st of 1.
- No CVE
- Larger: an outlet’s first report
- Coverage over time
Show all 1 articles as a listHide the list
- Wed 18 NovDay 01
- Keisei Skyliner data breach may have exposed 3.37M records05:42 · cybersixt · First report · This article, 1st of 1
Sources
- Keisei Electric Railway: unauthorised access to the Skyliner seat reservation systemPrimary sourcekeisei.co.jp
- Keisei Electric Railway: Unauthorized access to Skyliner seating reservation systemPrimary sourcekeisei.co.jp
- Keisei Electric Railway: Temporary Suspension of Skyliner Ticketless ServicesPrimary sourcekeisei.co.jp
More reporting
- Drupal vulnerability CVE-2026-132165 can lead to takeover18 Nov
- Visa data breach claim: supplier blamed as n0n names 5918 Nov
- nginx2root (NGINX2Shell): CVE-2026-123007 RCE exploit published18 Nov
- LUKSO email recovery flaw lets attacker drain 300 profiles18 Nov
- Valcour security incident takes Vermont police system offline18 Nov
Written by CyberSIXT from the sources above.How we reportCorrectionsRSS