Peach Aviation disclosed on 20 November 2026 that unauthorised access to Cuenote FC, an email-delivery service operated by vendor Ymirlink Inc., exposed 8,997,106 customer records. The exposed data includes names, dates of birth, gender, postal addresses, telephone numbers, email addresses and itinerary details. Credit card information and passport information were not included. Peach's reservation systems and flight operations were not affected. Peach dates the incident in the vendor's server environment to 18 October 2026 and confirmed the scope of its impact on 6 November 2026. No misuse of the exposed information or secondary damage had been confirmed at the time of the disclosure.
The disclosure makes Peach the largest single client disclosure so far in the wider Ymirlink breach, in which the vendor reported 47,864,147 records exported from 49 client systems. AliasFleet covered the vendor incident in an article on the Ymirlink data breach. Peach confirmed its scope on 6 November, eleven days after Ymirlink's second report.
What Peach said leaked#
Peach's official notice lists seven fields in the exposed data and gives the count as 8,997,106 items. The notice uses the Japanese counter for items; neither Peach nor Ymirlink describes the figure as a count of unique individuals. One person can appear in the count more than once, through several bookings or subscriptions, so the number of distinct people affected is not stated in the sources read for this article.
| Field | Included |
|---|---|
| Name | Yes |
| Date of birth | Yes |
| Gender | Yes |
| Postal address | Yes |
| Telephone number | Yes |
| Email address | Yes |
| Itinerary details | Yes |
| Credit card information | No |
| Passport information | No |
The fields combine to support targeted impersonation. An email address on its own supports spam. Paired with a name, a date of birth, a phone number and a travel itinerary, it supports targeted impersonation: a message that names the recipient, cites a real route and asks for a booking or refund confirmation. Peach stated this risk in its notice, warning that mail, SMS or calls impersonating Peach may be sent to the leaked addresses and numbers.
The wider Ymirlink breach#
The two totals for the wider breach need care. Ymirlink's second report gave 51,628,280 records as a cumulative maximum. Its third report gave 47,864,147 records after deduplication. The lower figure is not a correction but the same data counted without duplicates. The third report also gives the field breakdown for the whole incident: every record includes an email address, about 30.5 million a member ID and about 6.67 million a name. Peach's 8,997,106 records are part of that total. JapanHacked's incident page tracks the same figures.
Peach's own systems were not breached, and the data left Peach's control when it was handed to a vendor for a routine job, sending email, and the vendor's systems were the ones accessed. The client list reported for the wider incident includes railways, a card company, a bookseller, a newspaper and a prefectural government, each exposed through the same flaw in one email service.
AliasFleet and travel bookings#
A booking address used only for Peach can only ever appear in a Peach leak. The same address reused across an airline, a hotel and a car hire company ties those bookings together in every leak touching any of them. AliasFleet's guide to using email aliases for travel bookings describes the setup, and the guide on hiding an email address online covers the wider practice. An alias does not undo this leak. It limits what the next one can connect.
Dates in the incident#
| Date | Event |
|---|---|
| 16 October 2026 | Ymirlink detects unauthorised access after an employee notices something wrong with their own account. |
| 18 October 2026 | Peach dates the vendor incident to this day; Ymirlink finds malicious programs on further systems and stops its data centre systems as a precaution. |
| 19 October 2026 | Ymirlink publishes its first report: about 9 million records estimated exported from five systems. It reports to the Tokyo police and Japan's Personal Information Protection Commission. |
| 25 October 2026 | A review of login records finds unauthorised access and data export on 42 further systems. |
| 26 October 2026 | Ymirlink publishes its second report and notifies the 42 newly affected clients. The cumulative maximum is 51,628,280 records. |
| 6 November 2026 | Peach confirms the scope of its impact: 8,997,106 records. |
| 11 November 2026 | Ymirlink publishes its third report: 47,864,147 deduplicated records from 49 client systems. |
| 20 November 2026 | Peach publishes its notice and starts contacting affected customers at registered email addresses. |
How the attackers reached the data#
Cuenote FC is Ymirlink's email-delivery service, used to send newsletters, notification emails and other bulk mail, and to send that mail it holds the customer data the mail needs: email addresses, names, and whatever fields the client adds for personalisation. Peach used it for its email magazine and notification emails, including Peach Points expiry notices. That is why an email-delivery vendor held 8,997,106 Peach customer records containing names, birth dates, addresses, phone numbers and itineraries.
Ymirlink describes two attack methods. In the first, the attackers used a vulnerability to plant a malicious program on a server, read data directly from the database, and moved through an internal management network to other servers. Ymirlink says the spread came through a maintenance and quality-assurance account shared across its infrastructure, which it has since begun deleting everywhere. In the second, the attackers used the vulnerability to steal the sessions of legitimate users logged in at the time. They signed in to the Cuenote web console as those users and downloaded data with the console's ordinary CSV export feature. That activity looked like normal administrator work. Ymirlink found it only after reviewing the access and authentication logs of every system.
Ymirlink has not named the vulnerability. Its fixes include stricter input validation, removal of the shared support credentials, constant monitoring for malicious programs, and IP limits on its consoles and APIs. The vendor says its other services, including email engine, SMS, authentication and survey products, were not accessed.
Peach response and disrupted services#
Peach's notice, dated 20 November 2026, opens with an apology. Translated from the Japanese:
Peach deeply apologises for the great inconvenience and concern caused to customers and all related parties.
The notice is listed in Peach's news index.
The breach stopped three services: email newsletters, automated emails including Peach Points expiry notices, and the refund form used at airports. The refund form is used during irregular operations, such as flight disruptions, so Peach says alternative procedures will be used if refunds are required. Affected customers are being contacted in sequence from 20 November rather than all at once. Peach reported the incident to Japan's Personal Information Protection Commission, and the notice says the airline will disclose further facts promptly on its website if the ongoing investigation establishes anything new. The notice contains no dedicated contact phone number, email address or enquiry form for affected customers, and no compensation or credit-monitoring offer. Customer contact is outbound only, from Peach to the registered email addresses.
A separate Peach email incident took place a month earlier: on 7 October 2026 a ransomware attack on IDC Frontier's IDCF Cloud disrupted Peach's reservation-email delivery, delaying itinerary emails for new bookings. About 1.89 million records sat on that system, with no leak of personal information confirmed, and Peach restarted delivery through alternative servers from 8 October. The two incidents are distinct: different vendors, different causes, different outcomes. Ymirlink told Peach the Cuenote incident was not caused by ransomware. TRAICY reported the IDC Frontier incident on 9 October 2026.
What customers should do next#
Peach's own advice is narrow and specific. The notice asks customers to be careful with mail, SMS or calls claiming to be from Peach, and not to open URLs or attachments in mail or SMS they do not recognise. Peach's advice matches the leaked data: the attacker holds real email addresses, phone numbers, names and itineraries, so an impersonation message can quote true details.
A notice from Peach at a registered email address confirms the recipient's record was among the exposed data. Customers who receive no notice should not assume they are unaffected: Peach said contact would proceed in sequence from 20 November and gave no completion date.
Passwords were not part of the exposed data, but any account sharing a password with another service remains exposed through credential reuse, so changing reused passwords and enabling two-factor authentication where available reduce the follow-on risk. Messages claiming to be from Peach and asking for payment details, login credentials or a booking confirmation should be checked against Peach's official site or customer support, not through links in the message. A guide to checking whether an email is phishing covers the signs to look for.
Your address is probably in this file. Check whether it is, do the password work above, and then fix the part you control: the address you hand out next time. One AliasFleet alias per service means the next leak can only point back to the service that leaked it. Founders Club is $7 a month, locked forever, instead of $12. Early members only.
What remains unresolved#
Ymirlink has not named the vulnerability or said when the attackers first gained access. The intrusion route is still under investigation, according to both Peach and Ymirlink. An outside forensic firm is finishing its examination of the servers where the malicious program was found, and Ymirlink says it will publish a final report when the work is done.
No source states whether the exported data has been published, sold or misused. Peach says no misuse or secondary damage has been confirmed so far, and Ymirlink said the same in its second report, while noting spam emails posing as Saison Card had been sent using its domain. The absence of confirmed misuse is a statement about what has been confirmed to date, not evidence that the data is unused.
The count carries one open question. Peach reports 8,997,106 records and does not say how many distinct people that represents, while Ymirlink's total counts records across clients, so one address held by several clients appears more than once. Whether Peach's figure overlaps with other clients' figures is unstated. Peach said it would disclose further facts if the investigation establishes them; Ymirlink's final report is still to come.
