BreachesSupply ChainData Protection

Expedia Confirms a Supply Chain Breach. The Vendor Was a Former One.

November 17, 2026 · Brian Deitch

I'm a few days late on this one, but if you've ever booked a hotel online, it's worth a read.

On November 12, Expedia confirmed to Skift that it was hit by a supply chain attack: "attackers compromised a third-party data platform provider." An extortion group called n0n says it walked away with nearly a billion traveler records. Expedia hasn't confirmed that number, and neither have I.

What Expedia Confirmed

Per Skift and Security Affairs:

  • A supply chain attack through an unnamed third-party data platform provider.
  • Contained as soon as it became aware, with outside experts investigating.
  • Its platforms remain safe for travelers and partners, per Expedia.
  • Not disclosed: which vendor, what data was exposed, or how many people are affected. The investigation is ongoing.

What Researchers Say

Wiz and Sentra tie a broader campaign, which ran from about October 14 to 26, to Qubole, a cloud data platform and onetime Expedia vendor, via a stolen vendor key or compromised credentials. Sentra found that former Qubole customers never revoked the access they had granted. Skift is careful to note Expedia has not said its breach is related to Qubole, and researchers haven't publicly named Expedia as an affected Qubole customer. I'm holding the same line.

What the Attackers Claim

Everything here is n0n's claim, reported via Forbes and Security Affairs, and none of it is verified:

  • 830+ million loyalty program records (emails, membership IDs, points balances)
  • 58 million traveler profiles
  • 333+ million account and credential records with "password-like" tokens
  • Source code, taken with live credentials it says it captured the same way

Security Affairs describes n0n as a newly formed Russian extortion group that appeared in mid-September and claims hundreds of victims since.

The Real Story: Your Former Vendors Still Have Keys

I keep writing the same sentence this month, and this is why. Maersk was breached through a system it inherited. Barracuda through a vendor key nobody retired. And here, researchers say former customers of a data platform never pulled the access they'd granted.

When you onboard a data vendor, you hand it credentials into your cloud data. When the contract ends, the vendor goes away but the grant often doesn't. It just sits there, valid, unmonitored, waiting for someone to compromise the vendor.

I work at Zscaler, where I spend a lot of time on least-privilege access, so you know my bias. But this one doesn't need a product. It needs a spreadsheet and an owner.

What To Do If You Have an Expedia, Hotels.com or Vrbo Account

  • Change your password from a trusted device, and if you reused it anywhere else, change it there too. Credential stuffing comes next.
  • Expect very convincing phishing. If attackers really have loyalty IDs and points balances, "your points are about to expire" emails will look legit. Log in through the app or by typing the site address, never from a link.
  • Watch your loyalty balance and bookings for changes you didn't make.
  • Turn on MFA wherever these accounts offer it.

What To Do If You're the One Granting Vendors Access

  • List every third party with access to your cloud data, including ones you stopped paying.
  • Revoke on offboarding. Make "kill the credentials" a contract-exit step with an owner.
  • Prefer short-lived, scoped credentials over static keys, and alert when an old grant suddenly wakes up.

Bottom Line

The scariest vendor is the one you forgot you still trust. Clean up the old grants before an extortion group finds them for you.

Sources: Skift, Security Affairs, TravelUpdate

expediahotels-comvrbon0nquboledata-breachthird-party-riskphishingcredential-stuffingloyalty-programs
All postsDiscuss on LinkedIn