Extortion Group n0n Claims Theft of Nearly 1 Billion Expedia Traveler Records via Compromised Third‑Party Data Platform
What Happened – In mid‑November 2026, the Russian‑based extortion group n0n announced that it had exfiltrated data belonging to almost one billion travelers from Expedia Group, the world’s second‑largest online travel agency. The claim was first reported by security sites and later confirmed by Expedia, which said the breach originated from a “compromised third‑party data platform provider” that supplies big‑data services to its ecosystem. According to the group, the stolen material includes more than 830 million loyalty‑program records (email addresses, membership IDs, points balances), 58 million traveler profiles (home airports, account details), 333 million consumer‑account records containing password‑like tokens, roughly 2.5 million credit‑card‑spending records linked to hashed email addresses, 72 million matching records, and 500 000 guest‑stay records with accommodation details.
Cyber‑security firms Wiz and Sentra traced the intrusion to a stolen vendor key belonging to Qubole, a Google Cloud Platform partner that hosts Expedia’s data lake. The attacker used that key to obtain trusted access to the big‑data platform, then moved laterally to harvest data from multiple Expedia services (Hotels.com, Vrbo, Travelocity, Orbitz, Hotwire, Trivago). The group also alleges it captured source‑code and live credentials through the same vector.
Expedia’s public response confirmed the supply‑chain compromise but stopped short of verifying the exact volume of records taken. The company said its investigation is ongoing, that it has contained the incident, and that it engaged external cyber‑forensics experts. Expedia also asserted that its platforms remain safe for travelers and business partners, and it urged customers to change passwords and avoid credential reuse.
The extortion model employed by n0n is atypical: victims are listed on a dark‑web “leak site” only as numbered entries with a countdown timer. If a ransom is not paid before the timer expires, the group publishes the victim’s name and data. This pressure tactic is designed to force payment without the overt disruption of ransomware. Industry observers note that Expedia’s decision to publicly acknowledge the breach may undercut the group’s leverage, but it also provides transparency for affected travelers.
The breach highlights a broader trend of attackers targeting the supply‑chain relationships that underpin modern SaaS and cloud‑native environments. By compromising a single vendor key, the adversary gained a “trusted path” into a high‑value target, bypassing many traditional perimeter defenses. The incident underscores the need for continuous verification of third‑party access, robust key‑management practices, and real‑time monitoring of vendor‑derived traffic.
Regulators have not yet issued formal enforcement actions, but the scale of the alleged data exposure—potentially affecting millions of EU residents—could trigger GDPR investigations, while U.S. consumer‑protection agencies may scrutinize the adequacy of Expedia’s incident‑response and notification processes. The breach also raises questions about the adequacy of contractual security clauses with cloud‑service providers and the effectiveness of existing third‑party risk‑assessment programs.
Why It Matters for Trust & Control Assurance – The incident tests an organization’s ability to monitor, assess, and enforce security controls over third‑party providers, a core control‑area that maps to many frameworks (e.g., NIST CSF 2.0).
Who Is Affected – Travel‑technology firms, online travel agencies, loyalty‑program operators, cloud‑service partners, and the millions of consumers whose personal and payment data were exposed.
Recommended Actions –
- Conduct an immediate inventory of all third‑party keys and credentials that grant access to critical data platforms.
- Rotate or revoke any compromised keys and enforce short‑lived, just‑in‑time access mechanisms.
- Augment continuous monitoring of vendor‑originated traffic with anomaly‑detection rules.
- Update third‑party risk‑assessment documentation to include evidence of security‑posture (e.g., SOC 2, ISO 27001 reports) and verify contractual security obligations.
- Notify affected consumers in line with applicable data‑protection regulations and provide clear guidance on credential hygiene.
Technical Notes –
- Attack vector: stolen vendor API key from Qubole (cloud‑partner) → trusted access to Expedia’s GCP‑based big‑data platform.
- Data types: loyalty‑program records, traveler profiles, hashed credential tokens, limited credit‑card spending data, accommodation details, source code.
- Tools/Indicators: use of vendor‑issued access keys, lateral movement within GCP, exfiltration to unknown external C2.
- Investigators: Expedia engaged external cyber‑forensics firms (unnamed) and is cooperating with law‑enforcement.
Source: SecurityAffairs article

