Skip to content
A considered view of the world.
TravelGuys

Expedia cyberattack: the risk goes beyond payment details

Expedia confirmed on November 12 that it had suffered a cyberattack through a vendor. The group says it has contained the incident and that its platforms remain secure. As of November 17, the public information we had reviewed did not identify the vendor, establish which data was affected or give the number of people involved.

That is the starting point. The attackers’ claims about how much data they obtained have not been verified. Nor can we say that passwords, payment-card details or booking data were stolen. Confirmation of the attack, reported by TravelUpdate following information obtained by Skift, does not fill those gaps.

The uncertainty does not make this a minor issue. A travel record can be valuable to a scammer without containing a single card number. A hotel name, dates and a guest’s name may be enough to make a request convincing. That is why booking data matters: the information that helps arrange our trips can also be used to deceive us.

Cover photograph. The south entrance of Expedia Group’s Seattle campus on December 23, 2019. Archival photograph. Photo: T014y / Wikimedia Commons, CC BY-SA 4.0. Resized.

The right hotel, the right dates—and a fraudulent request

On June 2, 2026, Switzerland’s National Cyber Security Centre warned of two scams: fake WhatsApp refunds citing guests’ names, hotels and exact dates, and hijacked hotel accounts used to contact travelers through booking messages. Both sought banking details. The warning concerned Booking.com, months before the Expedia incident, with no established connection between them.

The refund example is particularly telling. The stay is over. There is no upcoming arrival to confirm, but a message about an overpayment or billing error can still sound plausible. The correct hotel name helps sell the story. Travel data can still be useful to a scammer after the customer gets home. It does not become harmless the moment the suitcase is unpacked.

The other method puts travelers in an even more difficult position. They have used a platform to keep their bookings and hotel conversations in one place. A message arrives in that familiar setting and appears to continue a normal exchange. Checking a logo or sender’s address is no longer enough when the hotel’s own account has been hijacked. The channel may be familiar, but the sender may not be who the guest thinks.

Hands holding a phone over a café table. Illustrative photograph published in 2016.
Using a phone at a café table. Illustrative photograph published in 2016. Photo: Maliha Mannan / Wikimedia Commons, CC0 1.0. Resized.

That does not make every exchange with a hotel suspicious. Messaging would lose much of its value if customers had to call after every reply. But an unusual payment request, new bank details or a threat of immediate cancellation warrants checking through another channel. Finding a phone number independently, or opening support through the usual app, allows the traveler to check the request without relying on the message’s instructions.

We will not blame customers for recognizing the details of their own stay. That is precisely what makes these scams convincing. Travel companies cannot promote the convenience of a booking platform and then act surprised when travelers trust it. Clear warnings should explain when an extra check is needed and give examples, rather than simply tell customers to stay vigilant.

Travel payments follow different rules

Travel offers plenty of plausible reasons to request money: a deposit, an outstanding balance, a guarantee, a local tax, a refund or a change fee. Some may be entirely legitimate for a particular booking. The challenge is distinguishing a payment required by the agreed terms from a new demand in a message. Telling travelers to reject every payment request after booking would not help them.

Expedia’s French privacy statement, updated on November 3, describes how payment data is used for options such as “Pay Now” and “Pay Later.” Booking and payment do not necessarily happen at the same time. To understand a request, customers need to return to their confirmation and the terms they accepted, rather than treat the latest message as a new set of rules for the stay.

Consider a prepaid room. A message demanding another payment to “validate” that same room deserves checking. If payment is due at the property, however, the absence of a charge before departure is not, on its own, a sign that something is wrong. These are different situations. They show why support staff need to be able to read the actual booking and explain the payment due, rather than give everyone the same instruction.

An easy-to-use app does not remove that complexity. Interfaces have made booking much quicker; they have not made every contract identical. An agency adds real value when it helps customers understand those differences. Fake customer support tries to exploit them instead, inventing one final step, claiming to correct an error or rushing the customer so there is no time to check.

A reception desk and armchairs in the Down Town Hotel lobby in January 2019.
The Down Town Hotel reception on January 21, 2019. Illustrative photograph. Photo: The Down Town Hotel / Wikimedia Commons, CC BY-SA 4.0. Resized.

Customers cannot control a vendor’s access

The confirmed intrusion at Expedia came through a vendor with trusted access. Such access allows different tools and companies to work together. It would be unrealistic to expect an agency to build every piece of software it needs, whether for data, distribution or support. A specialist can bring useful expertise and safeguards. Working with one is not inherently a mistake.

The problem arises when a useful permission grants access to too much, or remains in place after it is no longer needed. A Wiz investigation published on November 9 into Qubole integrations documented the abuse of vendor permissions. In several cases, researchers observed no legitimate use of those permissions during the period studied. The report does not name Expedia or identify its compromised vendor. It illustrates a mechanism, not the proven cause of this incident.

For customers, that distinction matters. A strong password protects their own login. It does not let them control what a business tool can access elsewhere. Advice to individuals therefore addresses only part of the problem. Asking travelers to strengthen their accounts may be useful; it does not relieve the company of the need to control the access it grants.

Nor does an incident, by itself, prove negligence throughout a company. Capable security teams can suffer an attack and need time to reconstruct what happened. Criticism should rest on established facts. Here, the details of the access used in the attack remain unclear.

One account can span Expedia, Hotels.com and Vrbo

Expedia’s French terms of service, revised on October 28, allow an Expedia Group account to be used across other group services, including Hotels.com and Vrbo, with the same login details. That convenience is welcome. Login details are easier to keep track of, especially for a brand used only occasionally. But a shared account is not evidence of how far the attack reached: nothing here establishes that all those brands were affected.

Someone who mainly books through Hotels.com may therefore use a group account without being accustomed to messages from Expedia. That matters when an alert asks them to do something. The brand they recognize and the company notifying them may have different names. A clear explanation of which brands are involved helps them avoid deleting a genuine message—or trusting any message that happens to mention the group.

A British Airways check-in kiosk at London Heathrow Terminal 5 in February 2008.
A check-in kiosk at London Heathrow Terminal 5 on February 26, 2008. Archival photograph. Photo: Terminal 5 Insider / Wikimedia Commons, CC BY 2.0. Resized.

For customers with loyalty benefits, credits or prepaid trips, account access also means being able to look up a travel credit, check a balance or retrieve a confirmation. The ability to make a new booking is not enough. They need to review existing reservations and spot activity they did not authorize. We are not saying any of this was compromised at Expedia; whether it was affected remains to be established.

A shared account can also help when access needs to be secured: a single action may save customers separate steps with several brands. But they still need to understand what it covers. If a shared login changes, travelers need to know which services are affected. If they contact one brand’s support team, they expect it to distinguish an account issue from a problem with that particular reservation. That is a reasonable expectation in return for the simplicity promised at sign-up.

Closing an account does not erase everything

After a cyberattack is announced, closing an account may seem the quickest way to regain control. But doing so does not remove a copy that may already have been taken. It can also make it harder to access information about an upcoming stay, an invoice or a useful conversation. It is better to understand what will be deleted and keep the documents needed before making a hasty decision.

Expedia’s privacy statement explains that data may be retained to meet obligations, including those related to transactions, and that residual copies may remain in backups. So closing an account may not immediately erase every trace of a trip. Those retention rules, in themselves, tell us nothing about which data was involved in the current intrusion.

Even before a crisis, it is worth considering what information is kept in an account. A booking history can help retrieve an invoice or book the same hotel again. The contact details of a former travel companion, an outdated preference or documents sent for a one-time request may be less useful. Customers should be able to clear those out without losing information they still need for a stay.

The distinction between convenience and necessity matters for the agency too. Keeping more information can help with personalization and service, but it also means having more details to protect over time. An old booking may remain useful to a scammer: the Swiss fake-refund example shows how it can make a message convincing long after the guest has checked out.

Several people hold out their closed passports. Illustrative photograph taken in August 2024.
Passports from several countries on August 11, 2024. Illustrative photograph. Photo: Bobbyshabangu / Wikimedia Commons, CC0 1.0. Resized.

It would be equally unreasonable to demand that every piece of data be erased as soon as a trip ends. Disputes, invoices and other obligations may justify retention. The useful step is to separate those needs from optional uses and make the choices accessible. Customers should be able to understand what they are keeping for a future booking and what the company retains for other reasons. The discussion deserves better than a choice between keeping everything and deleting everything.

Booking direct is not a guarantee of privacy

At TravelGuys, we have already made the case for booking hotels directly. The relationship with the property, the terms for making changes or the handling of a request can all favor booking direct. But a cyberattack against an agency does not automatically make direct booking a guarantee of privacy. A hotel’s name at the top of a page does not reveal every tool working behind it.

A property may use a booking engine, a payment provider and software for communicating with guests. Those are not necessarily weaknesses: specialists may be better at protecting certain transactions. Conversely, removing an agency from the commercial relationship can simplify communication without removing IT vendors. Those two sets of relationships are not always equally visible to the customer.

Expedia’s role also extends beyond its own website. Through Rapid API, the group lets partners add accommodation options and booking functions to their own services. Travel distribution may therefore involve a company whose name is not the most prominent one on screen. That does not establish that those partners’ customers were affected by the attack. It simply shows the limits of judging a booking by the seller’s logo alone.

An agency remains useful when it lets customers compare properties, understand an offer and manage a booking in a familiar setting. A traveler may prefer that relationship to dealing with an unfamiliar hotel overseas. It is perfectly reasonable to expect a major intermediary’s support to be easier to reach or use. That choice still makes sense after a cyberattack, as long as travelers do not assume a familiar name is risk-free.

Two YubiKey hardware authentication keys with USB-A and USB-C connectors. Photograph from 2018.
Two YubiKey hardware authentication keys, photographed on August 14, 2018. Illustrative photograph. Photo: Tony Webster; crop by SUM1 / Wikimedia Commons, CC BY 2.0. Resized.

For us, choosing where to book depends on the trip: price, terms, who we deal with and the ability to resolve a problem. Security belongs in that decision too. Slogans do not settle it. “Direct” does not prove that data stays within the hotel; “major group” does not prove it can never be misused. In either case, the response when something goes wrong matters more than a promise of invulnerability.

What travelers can do without panicking

The available information does not justify telling every Expedia customer to cancel their trips or have their payment cards blocked. The right response depends on their own circumstances and verified instructions. A booking that matches the original confirmation does not call for the same action as a change of dates, an unfamiliar payment or other activity the customer does not recognize.

The Cybermalveillance.gouv.fr guidance updated on October 1 recommends reading information from the organization concerned, checking its contact details independently and preserving evidence of fraudulent use. Action should respond to something specific, rather than pressure from a message demanding an immediate response.

If a reservation changes when the customer has not requested it, the agency’s official support service is the right place to start. For an unfamiliar bank transaction, customers also need to contact their bank. Keeping confirmations, messages and screenshots can help explain the sequence of events. The point is not to investigate the attack themselves, but to show what does not match their own actions.

Use a different password for each service. Reusing a password creates a risk regardless of what the Expedia investigation finds. Changing a password, however, does not erase information already copied or establish that an incident had no consequences. It may be useful without being a universal answer.

Finally, a code requested during a login the customer initiated is different from one demanded by a stranger. Expedia sends one-time codes when extra verification is needed. Its terms say customer support will not ask for a password by phone or email, or request a bank transfer or payment details by text message. Going back to the usual app gives customers a way to check a request, rather than trust it simply because it mentions the group.

A traveler pulling a red suitcase along a platform at a Tokyo train station. Illustrative photograph published in 2015.
A traveler with a suitcase at a Tokyo train station. Illustrative photograph published in 2015. Photo: Israel Sundseth / Wikimedia Commons, CC0 1.0. Resized.

What Expedia needs to explain next

The assurance that the platforms remain secure is useful to someone who needs to book or change a trip today. It does not, on its own, explain what may have been accessed before. One customer may find nothing wrong with their booking and still have questions about older data. Another may read about the attack and wrongly assume it automatically cancels their stay. Those misunderstandings need separate explanations.

We therefore expect a dated update separating established facts from checks still underway. Once the investigation allows it, the group will need to specify the categories of data, brands and people affected, followed by any action required. That information does not require revealing confidential safeguards. Customers should be able to understand their situation without piecing together statements published in the press.

The legal framework also needs to be described accurately. France’s data protection authority, the CNIL, distinguishes between documenting a breach, notifying the authority and informing individuals, depending on the risk. Not every breach calls for the same steps. We do not have the information needed to assess Expedia’s compliance here. The fact that a reader has not received a message is not enough, on its own, to reach a conclusion either way.

An investigation can take time. The group should not rush out findings it will later have to retract, and a provisional answer can be entirely honest. But the involvement of a vendor does not change where travelers should turn. They booked through a service they know. That is where they should find explanations and help, rather than being referred to an IT company with which they have no relationship.

Our view

The first mistake would be to treat the attackers’ claims as an established account of what happened. The second would be to assume that, as long as bookings are possible, there are no further questions about data. Expedia needs to investigate what happened and explain the findings to its customers, rather than leave them with either of those assumptions.

This incident also reminds us of the value of a travel record. The information that makes our trips easier can make a scam much more convincing. A strong password and attention to payments help, but they cannot replace controls over access to business systems or information customers can use when an incident occurs.

Online travel agencies and specialist vendors serve a real purpose. We expect them to handle the complicated work behind an easy booking. Travelers should be able to prepare for a stay and know what to do if something looks wrong. They should not have to become IT investigators to get an answer.

Olivier Delestre-Levai
Olivier Delestre-Levai
Olivier has been into airline blogging since 2010. First a major contributor to the FlyerTalk forum, he created the FlyerPlan website in July 2012, and writes articles with a major echo among airline specialists. He now co-runs the TravelGuys blog with Bertrand, focusing on travel experience and loyalty programs.
1,324FansLike
954FollowersFollow
1,272FollowersFollow
370SubscribersSubscribe

Trending posts

Recent posts

Bacchanal: a welcome renovation, but booking needs to be clearer

Caesars Palace will renovate its flagship buffet in 2027. We welcome the decision. But guests booking today should already be able to find the price of their dinner more easily and understand what their chosen time guarantees.

Hyatt and Delta: a partnership with uneven benefits

The Hyatt–Delta partnership is now up and running. Medallion members gain a new hotel benefit. For Hyatt loyalists, Delta’s ticket restrictions and the choice of airline program make the deal less appealing, especially for those who use Flying Blue.

Expedia cyberattack: the risk goes beyond payment details

Expedia has confirmed an intrusion through a vendor, but its scope remains unclear. Even without card numbers, booking details can make a scam convincing. Our view on protecting travel accounts.

FAA outage: the cost of a fragile air traffic control system

US airlines spent the weekend rebuilding their schedules after the November 13 outage. We look at which flights they prioritized, the rebooking options and the refund rights available to passengers.