Cyber & AI intelligence
Briefs indexed3943
Issues37
Published Mondays07:30 CT
▣ Breach PEACH-AVIATION-CUE 2026-11-20

Peach Aviation: Nearly 9 Million Customer Records Exposed in Cuenote FC Supplier Breach

"Japanese low-cost airline Peach Aviation has confirmed that 8,997,106 customer records were exposed when attackers broke into Cuenote FC. Cuenote FC is a bulk email service run by Tokyo-based Ymirlink, and Peach uses it…"

Japanese low-cost airline Peach Aviation has confirmed that 8,997,106 customer records were exposed when attackers broke into Cuenote FC. Cuenote FC is a bulk email service run by Tokyo-based Ymirlink, and Peach uses it to send newsletters and customer notifications. In a customer notice published on November 20, 2026, the airline said the leaked data includes names, dates of birth, gender, postal addresses, phone numbers, email addresses and travel itineraries. It said credit card and passport details were not on the affected servers, and that reservations and flight operations were not affected. Peach is one of 49 Ymirlink client systems caught up in the breach. Ymirlink's own count of stolen records across all clients now stands at 47,864,147.

What Happened

The breach took place at Ymirlink, not on Peach's own systems. Ymirlink's first report, published October 19, says one of its staff found unauthorized access to some systems early on Friday, October 16. Japan Cyber Watch, working from Ymirlink's disclosures, puts the first sign at 06:49 that morning, the blocking of the attacking IP address at 10:10, and the rollout of a fix to all platforms at 20:46. Ymirlink says it disconnected the affected servers, shut down server operating systems, suspended the service and reported the matter to police.

The dates differ between accounts. Peach's notice, as reported by TRAICY Global and Japanese outlet Saisoku News, gives October 18 as the date the incident occurred at the contractor. Ymirlink's own reports say the intrusion was detected on October 16. Japan Cyber Watch's timeline shows malicious activity continuing through October 17 and 18, which may explain the gap, but Peach has not explained its choice of date.

Peach says the scope affecting its customers was confirmed on November 6, and it began notifying customers by email on November 20. Analysis site Vedfolnir counts this as a 33-day gap between the incident and customer notification. Vedfolnir also says this is the second time in 11 days that Peach has been hit through outsourced email infrastructure. Peach has not addressed that claim, and no other outlet has reported a second incident.

Peach says it has reported the breach to Japan's Personal Information Protection Commission. Citing Ymirlink, the airline says ransomware was not involved. It also says Ymirlink is still investigating how the attackers got in and the full extent of the damage.

The outage has knocked out three Peach services: email newsletters, automated messages such as notices about expiring Peach Points, and the refund request forms used at airports during flight disruptions. Peach says it will use alternative procedures for refunds until the forms are restored.

What Was Taken

Peach Aviation: 8,997,106 records containing names, dates of birth, gender, postal addresses, phone numbers, email addresses and itinerary information. Peach says no card or passport data was involved and that no misuse of the data has been confirmed so far. The figure counts records, not people. Peach has not said how many unique customers are affected, and IPCRIME warns against reading the number as a headcount.

Ymirlink's total across all clients: The vendor's estimate has changed with each report: - First report (October 19): about 9 million records, including email addresses, taken from 5 systems - Second report (October 26): a maximum estimate of about 51.62 million records once more systems were added - Third report (November 11): revised down to 47,864,147 records across 49 systems, after duplicates and records that were never actually exported were removed

Ymirlink's first-report estimate for the first five systems happens to be close to Peach's figure. Neither company has said whether Peach's data was among those first five systems.

Ymirlink's third report breaks the 47.86 million records down by field. Every record contains an email address. About 30.5 million include a member ID and 6.67 million a name. The report also lists 2.06 million with gender, 1.82 million with a postcode, 1.21 million with a prefecture, 949,217 with a date of birth, 412,794 with a phone number and 152,868 with a street address. More sensitive data was also taken: 226,158 hashed passwords and 420,419 sets of login credentials for a client service that closed in February 2026. Separately, Ymirlink's own customer management system, Cuenote BASE, exposed 190 contacts at client companies. Ymirlink says it has found no payment card data in the stolen material.

Why It Matters

Peach's message that no cards or passports were taken is accurate, but it understates the risk. A record that combines a real name, a phone number, a date of birth and an exact flight itinerary is ideal material for convincing phishing. A scammer can write about a trip the victim has actually booked, offering a fake rebooking, refund or baggage notice. Vedfolnir notes that a leaked card can be cancelled with one phone call, but a leaked itinerary and identity cannot. Peach itself warns customers to expect fake emails, text messages and phone calls pretending to be from the airline.

The bigger lesson is about concentration risk in suppliers. One email delivery vendor held customer data for dozens of Japanese brands. Japan Cyber Watch ranks the Ymirlink breach as Japan's third-largest of 2026. Every client, Peach included, is now running its own notification process weeks after the vendor detected the intrusion. Bulk email platforms often hold more than email addresses. In Peach's case, the platform held itinerary data, which shows how much personal data can end up in a system that is classed as marketing infrastructure.

The exposed hashed passwords and the credentials from the closed service also create a risk of attackers reusing those passwords on other sites, and that risk reaches beyond the clients named so far.

The Attack Technique

Ymirlink's reports, along with coverage by CyberSIXT and Japan Cyber Watch, describe two stages.

Stage one: direct compromise. The attackers exploited a flaw in Ymirlink's software and obtained the login credentials of a Ymirlink support and quality assurance staff member. They planted a malicious program, read data straight out of the database, and then used the staff credentials to try to log in to other systems. Ymirlink says this maintenance and QA account existed on all of its platforms, which let the attackers move between systems over an internal management network. These were the five systems identified in the first report.

Stage two: stolen sessions. Ymirlink then reviewed web access and authentication logs across all of its systems, working with an outside security firm. That review found that the attackers had stolen the sessions of users who were logged in at the time. They used those sessions to enter the admin console as those users and downloaded data with the platform's built-in CSV export. Japan Cyber Watch notes that this looked like normal admin work, and it was found only about nine days after the first detection.

Accounts of how many systems fell to each method differ. Japan Cyber Watch says 42 systems were hit through stolen sessions. Ymirlink's third report says 45 systems were added in the second report, for a total of 49. The figures do not add up cleanly, and Ymirlink has said its investigation is still going on.

Ymirlink says it has patched the flaw and removed the shared support account from all systems. It says it is also removing standing shared admin rights and restricting admin consoles and APIs to approved IP addresses. Japan Cyber Watch reports that some environments had no such IP restriction before the breach.

What Organizations Should Do

  1. List what your marketing and messaging vendors actually hold. Bulk email platforms should receive the minimum needed to send a message. Itineraries, dates of birth and full addresses rarely need to be there. Remove extra fields and set retention limits on the data you sync to them.
  2. Require the vendor's admin consoles and APIs to be restricted by IP address and protected with phishing-resistant MFA. Also require short session lifetimes, and sessions tied to the user's device where possible, so a stolen session token cannot simply be reused from somewhere else.
  3. Alert on bulk exports, not just on intrusions. In stage two, the attackers used the console's normal CSV export. Ask vendors to log large or unusual exports and send alerts on them, and make sure the export logs are passed to your own security team.
  4. Ban support or QA accounts that exist on every platform. Write into vendor contracts that support access must be per-tenant, granted just in time, and logged. One shared account let this breach spread across Ymirlink's whole infrastructure.
  5. Prepare customer warnings about phishing before an incident happens. Have templates ready that tell customers which channels you will and will not use to contact them, especially about refunds and rebooking. Airlines and travel firms should assume leaked itineraries will be used as bait.
  6. Check for credential exposure. If your users' hashed passwords or credentials for a closed service could be in the Ymirlink data, force password resets and watch for login attempts using leaked credentials.

Sources: Peach Aviation Confirms Nearly 9 Million Customer Records Exposed T... | Can You Relax Just Because 'No Credit Cards Were Leaked'? Breaking... | ピーチの個人情報、約900万件が漏えい 氏名・住所・旅程が対象、カード情報は含まず - サイソクニュース | How Yumil Link's Cuenote Was Breached: Stolen Sessions, a Normal CS... | Ymirlink data breach: 47.8M records stolen from Cuenote | 当社システムへの不正なアクセスに関するご報告(第三報)|NEWS|メッセージングソリューションのユミルリンク | Peach Aviation Customer Data Leak Affects Nearly 9 Million Records... | 当社システムへの不正なアクセスに関するご報告(第一報 2026年10月19日 19:05更新版)|メールマーケティングのCuenote