Skip to main content
Emerging Threats

Luxury Hotels Expose Weakness in Email-Based Refund Scams

Hotel staff member working at a computer with a blurred screen.

"This is a good illustration why 'just don't click on links' is bad advice," the blog post observed.

Fake booking request opened a reservations inbox

Attackers gained initial access to a luxury hotel's reservations inbox by sending a fake booking request. Once inside that shared mailbox, they had the visibility and the communication context needed to carry out the next steps of their scheme. The blog post reports that the attackers targeted the very channel hotel staff use every day to serve guests — the reservations inbox — rather than exploiting a technical vulnerability or a public-facing web form.

Copying genuine refund requests to obtain fraudulent approvals

With access to the reservations inbox, attackers copied genuine refund requests and used those real messages as templates to craft fraudulent refund requests that were then approved. The tactic relied on reusing authentic content and context already present in the inbox, enabling the fraudulent requests to appear legitimate to staff who processed refunds.

Why "just don't click on links" fails for reservations and front-office staff

The incident underlines a practical constraint for employees who must routinely handle unsolicited communications: "It can't work when answering strangers' emails is the job," the post states. Front-office and reservations teams are expected to respond quickly and courteously to booking inquiries, change requests, and refund claims. Advice that reduces security to a simple behavioral prohibition — "don't click" — ignores the reality that answering emails from unknown senders is intrinsic to these roles.

Guest-first culture punishes hesitation

The attackers' approach leveraged cultural incentives as much as technical weaknesses. The blog notes that a guest-first culture in luxury hotels "punishes hesitation," creating pressure on staff to act decisively and favorably on customer-facing requests. That dynamic makes careful verification harder: employees who slow a transaction to confirm legitimacy risk customer dissatisfaction, negative reviews, or escalation from managers, while those who comply preserve the perceived service standard.

Splitting security between owner, operator, and brand left nobody accountable

The case study also highlights an organizational fault line: security responsibilities split among owner, operator, and brand. According to the post, that division "leaves nobody accountable." When the technical controls, policies, and day-to-day processes for handling guest communications sit across distinct entities, gaps can form in training, access control, inbox governance, and incident response. In such an environment, the blog warns, "blaming staff becomes the convenient answer" — a reflex that treats frontline employees as the weakest link rather than addressing structural failures.

What this means for owners, operators, and guests

  • Owners: Re-examine contractual divisions of responsibility. The incident shows that when security is fragmented across owner, operator, and brand, accountability gaps can enable abuse of operational channels.
  • Operators (hotel management and reservations teams): Reassess inbox governance and approval workflows. Because attackers exploited standard reservations messages as templates, operators will need to consider controls that detect copied or templated content being used to authorize refunds.
  • Guests: Expect that customer-facing cultures designed to deliver seamless service can be manipulated by attackers. The trade-off between frictionless hospitality and verification-driven processes is at the heart of this case.

The episode is a compact, practical lesson. It demonstrates that attackers will target the human and organizational contours surrounding routine systems — the shared mailboxes, the reply templates, the incentive structures — not only software bugs. It shows too that easy platitudes about avoiding links or relying on staff prudence are insufficient when the job requires engaging with strangers and when operational responsibilities are split across multiple parties.

The unresolved, practical question the case poses is this: if neither a single employer nor a single brand holds end-to-end control of guest communications, who will be tasked with redesigning the controls and workflows that prevent this particular vector from recurring? The blog post leaves that accountability gap as the central policy and operational challenge hotels must address.

Read the original post: https://www.schneier.com/blog/archives/2026/11/usable-security-at-luxury-hotels.html