Skip to content
[ SIGNAL VERIFIED ] INDEPENDENT CYBERCRIME JOURNALISMCLASSIFIED // THE UNDERGROUND HAS A NEWSROOM / RSS
.COM
Latest News
ALL NEWS
Newsroom

skyticket Discloses Additional Booking-Data Leak Affecting About 1,166 People

skyticket's November 18 update identifies a September booking-data leak affecting about 1,166 people, including passport information for 15 travelers.

skyticket Discloses Additional Booking-Data Leak Affecting About 1,166 People
PUBLISHED

Adventure’s November 18, 2026 fourth incident report confirms an additional skyticket leak involving 1,045 bookings and approximately 1,166 people, including passport details for 15 travelers. The information was obtained through a payment-server function on September 20, not during the disclosure day.

An external-access permission scheduled for removal in 2024 remained enabled. Adventure discovered the September activity on November 12 while reviewing earlier logs; access to the function had been blocked on October 28.

Exposed information includes contact, booking and itinerary details. Some companion names were encrypted, but encryption information had also been obtained, creating a risk they could be read. Cards, bank details, passwords, driving-license details and passport images are excluded.

The finding revises an earlier passport-number assurance because this exposure used a different route. Individual notifications begin November 18, and the company has reported to Japan’s privacy regulator.

IPCRIME analysis: connect remediation to older logs

This is a useful review pattern for service operators: when closing an unintended interface, preserve enough history to ask whether the same route was used before the most recent alert. A fix and a historical impact assessment answer different operational questions. Record the intended purpose of each permitted connection and verify that retirement work removes the permission as well as the application that once needed it.

Travelers evaluating a suspicious reservation message should open the booking service independently and check the reservation there. Familiar trip details should not be accepted as proof that the sender is authorized. Avoid forwarding an entire reservation thread when asking someone to verify a message: share only what is needed, and use a communication channel whose identity has already been established.

Source

Adventure fourth incident report, November 18, 2026.

Related reading: Surveillance Watch: What to Do When a Data Breach Exposes Identity Documents.

Featured image: conceptual IPCRIME artwork, not a photograph or screenshot of this incident or product.

Editorial note

IPCRIME distinguishes public records and documented findings from allegations, analysis and commentary. Report corrections through our contact page.