Skip to content
Rush Commerce
Commerce & Retail Tech3 min read

Expedia data breach: a third-party data platform was the way in

Expedia confirmed a breach through a third-party data platform. Researchers tie the attack to vendor access never revoked. Audit your cloud grants.

Expedia confirmed last week that attackers got into its systems through a third-party data platform provider. It has not named the vendor or said what data left. An extortion group now claims nearly one billion traveler records. The Expedia data breach matters to small retailers for one reason: researchers say the attack path ran through vendor access that former customers forgot to revoke. You almost certainly have a few of those grants too.

What actually happened

Expedia confirmed the breach to Skift on Thursday, November 12. Expedia called it a supply chain attack reported by security researchers. It said it contained the issue, is investigating with outside experts, and that its platforms are safe. It has not said what data was exposed.

The likely path, per Skift:

  • The vendor. Wiz and Sentra documented an October 14–26 attack on customers of Qubole, a cloud data platform and a onetime Expedia vendor.
  • The method. Attackers used compromised credentials to get into several customers' cloud environments and download data.
  • The gap. Sentra found that former Qubole customers never revoked Qubole's access permissions.

Expedia has not confirmed that its breach is the Qubole attack.

The claims come from an extortion group called n0n. Security Affairs lists them: over 830 million loyalty records from 35 programs, 58 million traveler profiles, and 333 million consumer account records. Expedia has not confirmed any of these numbers. Treat them as the attacker's sales pitch, not as fact.

Why vendor access matters for your business

You do not run a billion-row data lake. But you have probably given a vendor a key. An analytics tool with a service account in your Google Cloud. A reporting app with read access to your Shopify store. A freelancer's API token in your database. The contract ends. The access does not.

Here is the hour we would spend this week:

  1. List every grant. Cloud IAM roles, service accounts, OAuth apps, installed store apps, API keys. Write down who owns each one.
  2. Revoke what you no longer pay for. If the vendor is gone, the key goes too. Same day.
  3. Put revocation in the offboarding checklist. Cancelling the invoice is not offboarding.
  4. Warn your loyalty customers about phishing. Leaked loyalty data makes very convincing fake "points expiring" emails.

Key takeaways

  • Expedia confirmed on November 12 that attackers came in through a third-party data platform provider
  • Expedia has not named the vendor or said what data was exposed
  • Researchers tie a Qubole attack to vendor access that former customers never revoked
  • n0n's claim of 830 million loyalty records is unconfirmed
  • List every vendor grant you have, and revoke the ones you no longer pay for

The vendor you fired can still have a key to your data. We audit the cloud roles, app installs and API keys around your store, and build systems where access ends when the contract does. See what we build, or ask us for an access audit.

Sources: Skift, Security Affairs.

  • #data-breach
  • #vendor-risk
  • #supply-chain
  • #cloud-security
  • #ecommerce
TR

Tommy Rush — Founder, Rush Commerce

Operator turned builder. 15+ years running operations — now shipping the systems businesses run on. More

Get The Rush Report weekly — one email, zero fluff.