Cyber security for small hotels: 5 gaps to close before the season
Fake "Booking.com" emails, shared Wi-Fi, one password at reception. Five gaps a small hotel or holiday rental should close before the season starts.
An email "from Booking.com" lands at reception: a guest has complained and you need to respond today. The link asks you to "verify" and then tells you to press two keys and paste a command. A few minutes later someone else has your extranet login and is messaging your guests to "confirm their card".
This is not hypothetical. Microsoft, Bitdefender and Booking.com itself have described this pattern in public. Winter is the best time to close these gaps, before bookings and seasonal staff arrive.
Why accommodation businesses are targets
A hotel or rental has three things fraudsters want: access to booking platforms, guest data and payments. It is usually run by a small team, with a shared computer at reception and very little time.
- Microsoft tracked a campaign from December 2024 that impersonated Booking.com and targeted hospitality organisations in several regions, including all parts of Europe. The emails mentioned negative reviews, guest requests or "account verification" and installed malware that steals credentials.
- Bitdefender described a new campaign in December 2025 that sent fake "guest complaints" to Booking.com partners and told staff to press Windows + R and paste a command.
- According to Krebs on Security, Booking.com said these attacks start with malware on partners' computers, and that criminals then message customers to get them to pay outside the platform.
The 5 most common gaps
1. The extranet is protected by a password only
Booking.com sends a verification code to your mobile if someone logs in with your credentials, and says staff education, multi-factor authentication (MFA) and anti-malware software are "critical" (Booking.com). The same applies to every other platform and to your email.
What to do: turn on MFA for every booking platform, your channel manager and your email. Give each person their own account instead of one shared login.
2. Staff don't know what a fake message looks like
These campaigns play on the stress of a "bad review" and on urgency. Booking.com says its partner service staff will only ask for your property ID, never your password or card details (Booking.com). Bitdefender notes that Booking.com does not ask partners to run commands or install "verification tools" (Bitdefender).
What to do: keep a one-page set of rules at reception (see the checklist below) and give every new seasonal employee a 15-minute briefing.
3. One Wi-Fi network for everyone
If guests, cameras, the card terminal and the reception computer all share one network, an infected guest laptop can reach your devices. New Zealand's government guidance for small businesses puts it simply: a guest network should only give access to the internet and should not be able to connect to other devices on the business network (Own Your Online, NCSC NZ).
What to do: a separate guest network, a separate staff network, a new router admin password, and WPS turned off.
4. The reception computer does everything
The same computer reads email, opens attachments, logs into the extranet and stores guest lists. If it is infected, everything is. For this campaign, Microsoft recommends phishing-resistant MFA, cloud-delivered antivirus protection and link checking at the moment of the click (Microsoft).
What to do: keep Windows and the browser updated, keep antivirus on, and use a standard user account, not an administrator account, for daily work.
5. Payments and deposits handled by email
A message asking a guest to "re-confirm" their card or to send a deposit to a new IBAN is a classic fraud. The attacks Krebs on Security describes ended exactly there: a payment outside the platform.
What to do: say in your booking confirmation that you never change bank details by email. Confirm any change of bank details by phone, on a number you already know.
Reception checklist
| Rule | Yes / No |
|---|---|
| MFA on Booking.com, other platforms, the channel manager and email | |
| Personal accounts, no shared password | |
| We never press Windows + R or paste commands a website asks for | |
| "Guest complaint": open the extranet from a bookmark, not from the email | |
| Separate guest Wi-Fi | |
| Windows and antivirus up to date at reception | |
| No change of bank details without a phone check | |
| Who we call if something looks wrong (name, phone) |
If something happens
Change passwords at once from a different, clean device and tell the booking platform. If guests' personal data was exposed, the GDPR requires you to notify the supervisory authority (in Greece, the Hellenic Data Protection Authority) within 72 hours of becoming aware of it, unless the breach is unlikely to put people at risk (GDPR, Article 33).
General information, not legal advice.
Common mistakes
- "We're too small to be a target." These campaigns send messages in bulk to any property that works with Booking.com.
- MFA on the owner's account only. A seasonal employee with a shared password is the easiest way in.
- One network "to keep it simple". Separating networks is a router setting, not a project.
- Trusting the sender name. "Booking.com" in the From line proves nothing.
Start with what is visible from outside
Some of these gaps can be seen from the internet: whether your property's email is protected against spoofing, whether your website and booking engine use HTTPS correctly, and whether they run outdated software. Velontech's VelonRadar checks these public signals every day, and VelonGrade turns them into an A–F grade with the fixes that raise it. It does not enter your network and cannot see your Wi-Fi or reception computer; the checklist above covers those. We are in private beta: ask for a free check before the season opens.
Want us to check this for you?
A free check using public information only. We reply within one working day.