Expedia Group has confirmed that attackers reached its systems through a compromised third-party data platform provider, while a Russian extortion group called n0n claims it stole nearly one billion traveler-related records. Expedia said on November 12 that the supply-chain attack also hit other companies.
What Expedia Has Confirmed and What It Has Not
Expedia says its investigation is ongoing and that it has not confirmed n0n’s figures. The company says its platforms remain safe. It has engaged external investigators and moved to contain the incident, and it advises users of Expedia, Hotels.com and Vrbo to change passwords and watch for phishing. The wider Expedia Group family of brands, including Vrbo, is within the scope of the reporting.
The Stolen Qubole Key Behind the Intrusion
Researchers at Wiz and Sentra say the intrusion used a stolen vendor key from Qubole, a Google Cloud Platform partner. That key gave the attackers a trusted path into Expedia’s big data platform.
n0n’s Claimed Haul of Expedia Group Records
n0n claims to hold more than 830 million loyalty records from 35 programs and 58 million traveler profiles. It also claims 333 million consumer account records with password-like tokens, which are hashed, along with about 2.5 million card spending records, 72 million matching records and 500,000 guest records. The group also claims to have taken source code. None of these figures is verified, and the claimed total approaches roughly one billion records.
How n0n Runs Its Extortion Operation
n0n is a Russian group that emerged in mid-September. It steals data without deploying ransomware and lists victims as numbered “companies” with countdown timers. The group claims 224 attacks since September. A ransom negotiator noted that Expedia’s public confirmation of the breach weakens n0n’s pressure tactic, because the secrecy that gives a countdown its force is gone.
Risk for Expedia, Hotels.com and Vrbo Customers
If the claims are accurate, the exposure includes phishing and credential-cracking risk for users of Expedia, Hotels.com and Vrbo. The password-like tokens n0n describes are hashed, which raises the effort required to crack them but does not remove the risk. The attackers’ claimed access to loyalty and matching records could also give them material for targeted phishing aimed at travelers.
Timeline From n0n’s Emergence to Expedia’s Confirmation
n0n first appeared in mid-September and claims 224 attacks in the weeks since. Expedia’s confirmation came on November 12, and the group’s claims about the traveler records were reported widely two days later. Expedia has not confirmed the group’s numbers, and the company says containment is under way with external investigators engaged. The claimed total combines several distinct datasets, from loyalty program records to hashed account tokens and card spending data, which makes the figure difficult to check until Expedia or the vendor publishes its own count.
What the Expedia Incident Shows About Third-Party Data Platforms
The incident follows a pattern in which attackers compromise a single vendor credential and gain access to multiple customers. Wiz and Sentra’s finding that one stolen key opened a trusted route into a large data platform illustrates why vendor keys function as high-value targets: they carry the trust of the customer relationship without the monitoring applied to employee logins.
n0n Extortion Without Encryption Loses Leverage
The n0n model also reflects a broader change in extortion tactics, in which groups skip file encryption and rely on stolen data and public pressure alone. Expedia’s public confirmation removes one lever the group depends on. Whether the claimed data volumes hold up will depend on the outcome of Expedia’s investigation, which remains open, and on whether n0n publishes samples to back its numbers.
