Japan Airlines Data Breach via Amadeus IT Group

Japan Airlines Breach Exposes 92,000 Customers via IT Provider

HIGH
October 29, 2026
4m read
Data BreachSupply Chain AttackCyberattack

Impact Scope

People Affected

92,000

Affected Companies

Japan AirlinesJapan Transocean Air

Industries Affected

TransportationHospitality

Geographic Impact

Japan (national)

Related Entities

Other

Japan AirlinesJapan Transocean AirAmadeus IT Group

Full Report

Executive Summary

On October 28, 2026, Japan Airlines (JAL) announced a significant data breach affecting approximately 92,000 customers of JAL and its subsidiary, Japan Transocean Air. The incident was a supply chain attack, with the breach occurring at Amadeus IT Group, the Spanish technology provider for JAL's passenger service system. Unauthorized access to customer data, including names, flight information, and in some cases passport numbers, occurred over several weeks. JAL has stated that no financial data or passwords were compromised and is in the process of notifying affected individuals.

Threat Overview

The breach originated within the systems of Amadeus IT Group, which provides critical reservation, ticketing, and check-in services for JAL. Amadeus discovered traces of external access and notified JAL on October 23, 2026. The investigation determined that an unauthorized party had viewed customer data between August 10, 2023, and September 23, 2026. This long dwell time highlights the challenges of detecting intrusions within complex, interconnected third-party environments. The attack vector was a compromise of a trusted third-party supplier, a classic example of a supply chain attack (T1199 - Trusted Relationship).

Technical Analysis

While specific technical details of the intrusion at Amadeus have not been released, the incident underscores the risks associated with third-party dependencies. Attackers targeted Amadeus likely recognizing it as a central hub holding valuable data for multiple airlines. The compromised data included:

  • For ~90,000 customers: Name, reservation code, flight date, and travel class.
  • For ~2,000 customers: The above data plus passport numbers, frequent flyer numbers, nationality, email addresses, and phone numbers.

The absence of compromised credit card data or passwords suggests the attackers may have targeted a specific reservation database rather than a system processing financial transactions or user authentication.

Impact Assessment

The primary impact is the exposure of sensitive Personally Identifiable Information (PII) for 92,000 travelers. The stolen data, particularly passport numbers and contact information, creates a significant risk of follow-on attacks, such as highly targeted phishing campaigns, identity theft, and fraud. Customers may receive fraudulent emails or calls impersonating JAL, using the stolen flight details to appear legitimate. The incident also causes reputational damage to both Japan Airlines and Amadeus IT Group, eroding customer trust and highlighting weaknesses in their supply chain security posture.


IOCs — Directly from Articles

No specific Indicators of Compromise (IOCs) were mentioned in the source articles.

Cyber Observables — Hunting Hints

No specific observables can be generated from the article's content. The focus for defenders is on third-party risk management rather than technical indicators.

Detection & Response

For organizations like JAL, detection and response must extend to the supply chain.

  1. Third-Party Risk Management (TPRM): Implement a robust TPRM program that includes security assessments, contractual security requirements, and rights to audit for all critical vendors like Amadeus. This involves D3FEND Decoy Object placement in shared environments.
  2. Data Minimization: Review data-sharing agreements with vendors to ensure they only have access to the minimum data necessary for their function.
  3. Incident Response Planning: Ensure incident response plans explicitly cover supply chain breaches. This includes clear communication protocols, defined responsibilities, and joint investigation procedures with the vendor.

Mitigation

Mitigation efforts fall on both the breached entities and the affected customers.

  • For JAL and Amadeus: Amadeus has reportedly implemented security measures to secure its environment. Both companies must conduct a thorough root cause analysis and enhance their security controls to prevent recurrence. This includes better monitoring of access to sensitive data repositories.
  • For Affected Customers: JAL is notifying all 92,000 affected individuals. These customers should:
    1. Be extremely vigilant for phishing emails or phone calls that mention their travel with JAL.
    2. Avoid clicking on links or providing personal information in unsolicited communications.
    3. Verify any communication by contacting JAL directly through official channels.
    4. Consider placing a fraud alert on their credit files if their passport information was exposed.

Timeline of Events

1
August 10, 2023
Start of the period of unauthorized data access at Amadeus IT Group.
2
September 23, 2026
End of the period of unauthorized data access at Amadeus IT Group.
3
October 23, 2026
Amadeus IT Group notifies Japan Airlines of the security incident.
4
October 28, 2026
Japan Airlines publicly discloses the data breach.
5
October 29, 2026
This article was published

MITRE ATT&CK Mitigations

Training affected customers to recognize and report phishing attempts is a critical mitigation for the consequences of this data breach.

Audit

M1047enterprise

Enhanced auditing and monitoring of access to sensitive data repositories within third-party environments can help detect unauthorized activity sooner.

Mapped D3FEND Techniques:

D3FEND Defensive Countermeasures

For companies like Amadeus, implementing Resource Access Pattern Analysis on critical data stores, such as the passenger reservation database, is essential. This involves establishing a baseline of normal access patterns (e.g., which applications, users, and IP ranges typically access the data, and at what volume). The system should then alert on deviations, such as access from an unrecognized source, unusually large data queries, or access during non-business hours. This could have detected the unauthorized viewing of 92,000 records, potentially shortening the attacker's dwell time from weeks to hours and minimizing the scope of the breach. This is a key detective control for protecting high-value data assets in any environment.

To prevent data exfiltration in a supply chain context, monitoring data flows between the primary organization (JAL) and its vendors (Amadeus) is critical. Implementing User Data Transfer Analysis can help detect anomalies in data movement. For example, if attackers within Amadeus's network attempted to exfiltrate the JAL customer data to an external server, a system monitoring for unusual data transfers could flag the activity. This involves baselining normal data exchange volumes and protocols between trusted partners and alerting on any large, unexpected, or unencrypted transfers to unknown destinations. This provides a crucial layer of defense focused on the 'Collection' and 'Exfiltration' stages of an attack.

Timeline of Events

1
August 10, 2023

Start of the period of unauthorized data access at Amadeus IT Group.

2
September 23, 2026

End of the period of unauthorized data access at Amadeus IT Group.

3
October 23, 2026

Amadeus IT Group notifies Japan Airlines of the security incident.

4
October 28, 2026

Japan Airlines publicly discloses the data breach.

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Editorial Standards & Analyst Review

CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.

Tags

Data BreachSupply Chain AttackAirlinesPIIPassportThird-Party Risk

📢 Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

🛡️ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

🔗 STIX Visualizer

Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.

⚡ Sigma Generator

Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.