Latest

Cybersecurity

Expedia confirms the breach and does not verify a single figure

Expedia admits a breach through an external provider. The n0n group claims to have 830 million loyalty rows and the company does not confirm the scope.

Expedia confirms the breach and does not verify a single figure
Expedia confirms the breach and does not verify a single figure

Expedia Group acknowledged on November 12, 2026 that attackers reached its systems through an external data platform provider. It did so with a brief statement that leaves almost everything open: there was a supply chain attack, that provider served as a gateway to several companies and the company does not intend to say which one it was or what data was taken. The confirmation of the Expedia breach does not include a single figure on the scope, and the company has also not clarified whether the incident it admits to is the same one the group describes.

In parallel, the extortion group n0n maintained its own version on the leak site: 830,069,282 loyalty program rows in 800 files and 35 programs, with emails and member identifiers, balances in 21 currencies and reservation values. These are figures that no one has verified, that the company has not validated and that the group published without offering an auditable sample of what it claims to hold.

The distance between what a company signs off on and what an extortionist publishes is the most informative part of this case. What is confirmed here is the path, not the loot: a third party with trusted access opened the door and closed it late.

What Expedia confirmed and what it left unanswered

The statement does not include a single figure. Expedia Group says it contained the problem as soon as it became aware of it, that it is investigating with external security experts and that its platforms remain safe for travelers and partners, without naming the compromised provider or detailing what data was exposed. It also does not clarify when the intrusion occurred, which of the group's brands are affected or how many people could be within the balance.

The group owns Expedia, Hotels.com, Vrbo, Orbitz, Travelocity and Hotwire, and none of those brands has so far received a different explanation. The lack of a single verifiable data point contrasts with the precision of the claim that has been circulating since the first week of November 2026, when n0n added the company to its list of victims.

The silence on the scope lasted until November 12, 2026. Before that date, the company declined to comment on the group's claims, and the statement came when the inventory had been circulating among security analysts for more than a week, without anyone having been able to verify its content.

What the company does admit to carries technical weight, even if it sounds like a textbook formula. A compromised data provider does not need to attack anyone: it enters with the keys it was given to do its job and from the inside everything looks normal for days.

The figures n0n puts on the table

The group published its inventory on the leak site and kept it even after marking the company as a victim that had not paid. There is no ransom amount in the listing, the list of claimed volumes exceeds one terabyte and the breakdown contains more than one figure that should be examined closely.

What does n0n claim to have? Claimed volume Verified
Loyalty program 830,069,282 rows in 800 files and 35 programs No
Traveler profiles More than 58 million No
Accounts and credentials More than 333 million records No
Trips More than 22 million, with Vrbo reservations and payments No
Guest communications Almost 500,000 No

The row count does not equal the number of people: the same customer appears in the loyalty table, in the traveler profile and in the reservation, and each appearance adds a different line. That detail turns the 830 million into a figure that has not been translated into victims, and explains why the company has neither confirmed nor denied it in any of its statements.

The inventory the group describes also includes work credentials for the data platform, source code repositories and a production cloud environment. If that part were true, the problem would no longer be the booking history but the ability to get back in without asking anyone's permission.

With that data, a cheap and credible scam can be put together. A message citing the destination, the exact dates of a reservation and the loyalty program points balance does not need to earn anyone's trust: it has it in advance.

The Sega's breach through its newsletter provider showed the mechanism with 2.19 million emails exposed and no password involved: the value was in the list, not in the key. Here the package would be richer, because it includes reservation history and loyalty tiers.

The AWS role that outlived the provider

The technical analysis by Wiz documented between October 14 and 26, 2026 the mechanism that fits that description. An attacker used IAM credentials from the AWS account through which Qubole operates, a data platform for large volumes, to assume the roles that customers had created to trust that account. Each request carried the correct external identifier and each request worked.

With those permissions, the attacker enumerated resources, read secrets from Secrets Manager, from the parameter store and from Lambda function variables, tested the keys found and copied objects from S3 without writing or deleting anything. The Sentra investigation added the uncomfortable detail: the roles were still live at customers that had stopped using the platform, dormant since the spring and with no one having revoked them.

The addresses from which the requests were made did not help raise suspicion either. Wiz places the first calls at an IP from a commercial virtual private network and most of the rest at a rented server, while the provider logged no activity of its own in that window: to AWS, the visitor was the provider.

The root of the flaw

Therein lies the underlying flaw. The external identifier does not authenticate anyone: it is a code that the provider presents, and if the provider loses it, the code remains valid for whoever holds it.

Expedia is a long-standing Qubole customer and its statement fits that scenario, but neither the company nor Wiz nor Sentra has publicly identified it as a victim of that specific campaign. The link between the two events remains a reasonable and unconfirmed hypothesis, and writing it as fact would repeat the mistake this case punishes.

The checklist for any company that outsourced its data platform fits in four lines, and none of them requires buying anything or hiring a new team for a quarter.

  • Review which external identities retain permissions over your data and revoke those you no longer use.
  • Enable S3 data events in CloudTrail, because management logs do not see object reads.
  • Rotate the secrets that role could read, not just deactivate the role.
  • Treat the external identifier as a contract condition, not as proof of identity.

The attack with AI agents that exposed Chainstack customer data left the same lesson from another angle: a factory credential forgotten on a test server was enough to get into production, and no one had removed it because the server was still running for other tasks.

The key no one returned

Closing an integration does not erase the permission. That sentence sums up the incident better than any tally, because the access the attacker used was not stolen from Expedia or the other companies: they had granted it themselves, in writing, so that a provider could do its job.

The Gnosis Pay breach showed the same asymmetry from the cardholders' side: sensitive data in the hands of a third party and customers with no way of knowing until it was too late.

José Maldonado

Author

José Maldonado

Activist and blogger on technology, free software and blockchain.

The latest
From Huang to Botín, from Zara to Byron: corporate responsibility in global capitalism

Keep reading