Expedia Group is among the largest online travel companies in the world. The Seattle company operates Expedia, Hotels.com and Vrbo, runs more than 200 travel websites and reported $14.7 billion in revenue in 2025. It also holds 19.3 percent of the United States travel market, which makes it a priority target for extortion crews. Behind those brands sit loyalty programs, traveler profiles and account records.
Like most large travel platforms, Expedia depends on outside data specialists to store and process that information. One of them is Qubole, a Google Cloud Platform partner whose platform is used for big data work. The arrangement rests on trust by design: customers create cloud roles that let Qubole's own Amazon Web Services account assume access inside their environments. That delegation makes analytics work at scale, and it makes a stolen vendor credential dangerous, because trust is granted once and rarely revisited.
The group behind the claim is new. n0n emerged in mid-September and, according to SOCRadar, focuses on data theft and extortion without traditional ransomware. Its leak site lists victims only as numbered companies with a countdown timer labeled pending exposure, and names a company only when payment does not arrive. The group claimed 204 victims in October and more than 100 more in November.
Intrusions of this shape are more common as cloud analytics vendors accumulate privileged access across many customers. When one vendor key leaks, the blast radius is every environment that trusted the vendor. Expedia's case moved from leak site rumor to company acknowledgment within days.
Key Facts
Skift reported on November 12, 2026, that Expedia Group confirmed attackers reached its systems through a compromised third-party data platform provider, in a supply chain attack that also affected multiple companies. Reporter Adriana Lee published the story at 8:53 PM EST. Expedia said it was aware of a supply chain attack reported by security researchers, in which attackers compromised a provider and used its trusted access to reach systems at multiple companies. It said its platforms remained safe for travelers and partners, and it has not confirmed the volumes claimed.
Security Affairs reported on November 14, 2026, that n0n claims data on nearly one billion travelers and that Wiz and Sentra traced the intrusion to a stolen vendor key from Qubole. The group says it obtained more than 830 million loyalty program records from 35 programs, including email addresses, membership IDs and points balances. It also claims 58 million traveler profiles with home airports and account information, 333 million consumer account records with password-like tokens, nearly 2.5 million credit card spending records and 500,000 guest records.
Cyber Daily reported on November 12, 2026, that n0n claimed more than one terabyte of data in a November 3 leak post. The first of 12 bullet points described 830,069,282 loyalty program rows across 800 files, holding email addresses, member identifiers, point balances in 21 currencies, tier names and booking values across 35 named programs. The group also claimed more than 58 million traveler profile rows, details of more than 22 million journeys, almost 500,000 guest communication records and a workforce planning database. It offered no evidence at the time, but the dataset has since been published on the dark web.
Wiz reported on November 11, 2026, that its incident response team, working with Sentra and Mandiant, observed a threat actor using IAM credentials from an AWS account associated with Qubole between October 14 and October 26, 2026. The account, 805246085872, is the one Qubole's platform uses to assume roles in customer environments. Every AssumeRole request attributed to the actor included an External ID and every one succeeded, and session names followed a quiam prefix. The actor enumerated resources, collected secrets, accessed S3 data and validated additional credentials.
Forbes reported on November 13, 2026, that the alleged haul includes more than 830 million loyalty records, 58 million traveler profiles and over 333 million consumer account and credential records, and that n0n claims access to Expedia source code after stealing live credentials for that platform. The group set a leak deadline of November 9, 2026 at 00:18 UTC. Expedia has not confirmed those figures and says its investigation is ongoing.
Analysis
The technical evidence is unusually specific for an extortion claim. Wiz, Sentra and Mandiant did not rely on the group's word. They documented the first activity on October 14, when an IP belonging to Mullvad VPN at 45.83.220.211 called AssumeRole against integration roles in customer environments, from the Qubole-linked account. From October 15 most activity came from an OVH-hosted VPS at 57.129.54.120, and on October 18 the actor began using a second IAM user, AIDAJYRRH5Y3A7AAJM2HW, which also carries legitimate Qubole traffic.
The actor harvested Lambda environment variables, Secrets Manager secrets and SSM Parameter Store values, then used TruffleHog to test discovered AWS keys, Entra ID service principal secrets and Okta client credentials. It exfiltrated S3 objects, sometimes downloading entire buckets in one session. Wiz also found an ISO file named sso_agent.iso on the OVH address, a bootable Linux image with a 90-minute timer and a hard reboot meant to erase evidence. What this really means is that this was not opportunistic scraping. It was a disciplined campaign against a trusted identity path many customers never thought to audit.
Expedia's statement stops well short of the record counts. Skift's excerpt ends at the phrase about using trusted access to reach systems at multiple companies, and the article published no confirmed record count. A claim of nearly one billion records is a negotiating position as much as a factual assertion. Ransom negotiator Alex Waintraub, who is not working on the case, told Forbes the claims appear designed to pressure victims into paying, and that Expedia's public confirmation was unusual and could weaken the group's leverage.
The bigger picture here is that vendor trust relationships have become a primary attack surface. SOCRadar found that every documented n0n intrusion relied on weak or compromised credentials, with no exploit payloads or CVE references in the operator's files. Entry points included credential stuffing against FortiGate SSL-VPN portals through residential proxies, weak RDP and WinRM credentials, exposed AWS IAM keys and reused hosting-provider sessions. None of that requires a zero-day. It requires one key that was trusted by default, belonging to a platform many companies had deliberately invited inside their cloud environments.
Why It Matters
For travelers, the practical risk is identity and account abuse rather than immediate financial loss. Expedia says its platforms remain safe, but the claimed data includes email addresses, member identifiers, points balances, home airports, password-like tokens and spending records linked to hashed email addresses. Cyber Daily reported that the archive contains 11 folders of documents listing hundreds of thousands of email addresses linked to travel data, including log-in details, hotel stays and loyalty program details. Several had appeared in previous breaches according to Have I Been Pwned while many had never appeared before.
For the industry, the Qubole cross-account model is the part that deserves attention. Every customer that created a role trusting account 805246085872 inherited the same exposure, which is why Expedia described the attack as affecting multiple companies. A single stolen credential inside a vendor's AWS account was enough to reach environments across unrelated organizations, and the only visible control in the logs, an External ID, was present on every successful request. A control that is required and satisfied can still offer no protection when the trusted party is compromised.
For disclosure norms, the timing is instructive. The group set its leak deadline for November 9 at 00:18 UTC, and Expedia confirmed the compromise on November 12, after several cybersecurity sites had reported the allegations. Skift framed the disclosure as an unusual public acknowledgment made while the extortion group was still pressuring the company. Waintraub's read cuts both ways: silence buys negotiating room but invites days of unverified claims, while confirmation protects customers at the cost of handing the group a headline.
Next Up
The next phase will be forensic and regulatory rather than dramatic. Expedia says its investigation continues, no record count has been confirmed, and the company has not said whether it received a ransom demand or paid one. Expect scrutiny of which systems the Qubole trust path could reach, whether notification obligations are triggered in the jurisdictions where travelers live, and how quickly trust policies are reworked across the vendor's customer base. Wiz's November 11 update, citing Catalin Cimpanu of Risky Business, points to a wider question: how many other organizations were touched between October 14 and October 26.
The extortion economics will decide how loud this gets. n0n names a company only when it does not pay, its leak site has claimed 224 attacks since September, and its campaign against a company with $14.7 billion in 2025 revenue is a test of whether brand damage outweighs the cost of a settlement. Whether or not a payment happens, the case gives security teams a model to hunt against: stolen vendor credentials, assumed roles, quiam-prefixed sessions, secrets harvesting and S3 exfiltration.
Comments (0)
Log in or sign up to leave a comment.
No comments yet. Be the first to share your thoughts.