LiveBreach Intelligence: data breaches, leaks & ransomware, tracked as they surfaceOngoing protection: GalaxyWarden →
Recent BreachesData breach tracker
AnalysisInside the ARTEX toolkit, and the US outage weekTimeline

Recent Breaches › Holiday Inn Vilnius Listed by SafePay Ransomware Group

Holiday Inn Vilnius Listed by SafePay Ransomware Group: Ransomware Claim — What’s Alleged & What To Do

Holiday Inn Vilnius was listed by the SafePay ransomware group on September 28, 2026, with the group claiming to hold data belonging to an undisclosed number of people. Individuals who may have stayed at or transacted with the hotel are advised to monitor their accounts and consider changing passwords or enabling additional security measures.

Holiday Inn Vilnius Listed by SafePay Ransomware Group

Reported September 28, 2026.

Claim, unrated
Severity
September 28, 2026
Disclosed
Severity & verification
Claim, unratedUnverified claim
We grade an incident's severity only once the organisation, a regulator or a breach index has confirmed it. This one has not been confirmed yet.
Published on a ransomware group’s leak site — an unverified extortion claim until the named organization or credible reporting corroborates it.
Check your exposure
See every leak and listing tied to your email. We can’t confirm any single incident against the sources we search, so we won’t pretend to. 15-second check, no card, no account. Details go to your inbox.

By running your scan you agree to the Terms and Conditions and the Privacy Policy, and to GalaxyWarden emailing you the results of this scan.

A ransomware group known as SafePay has listed Holiday Inn Vilnius on its leak site, an accusation that has not been publicly confirmed by the hotel or by independent authorities as of writing. For guests, staff, and business contacts who may have shared personal or payment details with the property, the practical question is not whether a dramatic headline is true, but what to do if personal information were ever involved in an incident of this kind.

Public detail is limited. The listing itself is an unverified claim by the group. Counts of people affected, the method of any intrusion, and the exact contents of any files are undisclosed in the material available for this report. What follows separates what SafePay asserts from what is known about the brand, the sector, and sensible next steps if your data might be at risk.

What is being claimed

According to the listing, SafePay has named Holiday Inn Vilnius on its leak site. The report associated with that listing is dated September 28, 2026. Beyond the naming of the property, the publicly summarised claim does not set out a claimed timeline of intrusion, a volume of records, a ransom demand, or a technical description of how access was supposedly obtained.

The number of people affected is unknown. Data types supposedly involved are not disclosed in the available summary. Holiday Inn Vilnius has not, on the public record reflected here, stated that a breach occurred, that data was taken, or that the listing is accurate. Listings of this type are pressure tactics: groups publish a name and threaten release in order to force payment. That does not, by itself, establish that files left the organisation or that any particular guest or employee is exposed.

Readers should therefore treat the episode as an allegation on a criminal leak site until the company, a regulator, or another authoritative source says otherwise.

The group behind it: SafePay

SafePay is known in public reporting as a ransomware and extortion operation. Groups in this category typically claim to encrypt systems, exfiltrate copies of data, or both, then use dedicated leak sites to name victims and threaten publication if payment is refused. The model relies on reputational harm and regulatory fear as much as on technical disruption.

Well-documented patterns among such actors include double-extortion messaging, timed countdowns on leak portals, and marketing-style descriptions of stolen material that are difficult for outsiders to verify. SafePay’s listing of Holiday Inn Vilnius should be read in that light: the group claims the hotel is a victim; it does not supply independently audited proof in the facts provided here. No additional claims by SafePay about this specific property—beyond the fact of the listing and the sparse summary attached to it—are treated as established in this article.

Attribution on leak sites can also be noisy. Names are sometimes recycled, inflated, or attached to partial access. Without confirmation from the organisation or from forensic disclosure, the listing remains a claim.

Who is Holiday Inn Vilnius?

Holiday Inn Vilnius operates under the international Holiday Inn brand of IHG Hotels & Resorts. Public description of the property notes that it provides 134 guest rooms. Like other full-service city hotels, it sits at the intersection of travel, hospitality, and local business services: short-stay guests, corporate travellers, events, and on-site staff.

A hotel of this type is consequential in a data-protection sense because it routinely handles identity and contact information, reservation histories, and payment-related details in the ordinary course of booking and stay management. Brand affiliation with a large international group can also mean shared platforms, loyalty programmes, or centralised systems—though whether any such systems are implicated here is unconfirmed and is not asserted.

A leak-site listing does not prove operational failure at this property. It only shows that a criminal group chose to publish the name. That distinction matters for both the organisation’s reputation and for how individuals should weigh their own risk.

The information in question

The facts available for this report state that data types named as exposed are not disclosed. It is therefore not possible to say which fields, files, or systems—if any—are involved. Asserting a concrete inventory would repeat the attackers’ marketing without evidence.

If files from a hotel of this kind were ever taken, organisations in the sector typically hold some combination of guest names, addresses, email addresses, phone numbers, dates of stay, reservation identifiers, loyalty or membership references, and payment or billing metadata. Staff records, supplier contacts, and internal operational documents can also exist in hotel environments. None of that list is confirmed as part of this listing; it is a sector baseline for conditional risk thinking only.

Because the listing does not itemise content, individuals cannot know from public sources alone whether their own record is implicated. The responsible stance is to assume uncertainty and to take proportionate precautions rather than to treat any particular data element as proven stolen.

The real-world impact

For people who have stayed at, worked with, or been employed by the property, the realistic risks—if personal data were involved—are familiar rather than cinematic. Fraudsters reuse emails and phone numbers for phishing that impersonates hotels, booking sites, or payment processors. Reservation and travel details can make social-engineering messages more convincing. Payment-related data, where present, can support card fraud or account takeover attempts on related services. Identity details can be mixed with other breached datasets over time.

For the organisation, an unverified leak-site listing still creates operational and reputational pressure: guest enquiries, partner concern, and the need to investigate internally whether anything occurred. Those pressures exist whether or not the claim is accurate. They do not, however, establish negligence or confirm loss of control of systems. A listing establishes that criminals made an accusation in public; it does not establish the scope of any incident, the quality of defences, or the outcome of any response.

Scale remains unknown. With people affected listed as unknown and data types undisclosed, impact assessments for any single individual stay conditional.

What to do now

Until there is official confirmation and a clear description of what, if anything, was involved, treat advice as precautionary. Practical steps include:

  • If you have booked or stayed at the property, watch for unexpected messages that urge urgent payment, re-confirmation of card details, or clicks on unfamiliar links—especially messages that reference a stay date or reservation style detail.
  • Prefer official apps or known websites when checking bookings; do not use links from unsolicited email or chat.
  • If you reused a password on hotel, loyalty, or travel accounts, change it and enable multi-factor authentication where available.
  • Monitor bank and card statements for unfamiliar charges; report anything suspicious to your provider promptly.
  • Be cautious about sharing further personal data in response to cold contacts claiming to “help with a hotel breach.”
  • Remember that your information is not confirmed as exposed; these steps reduce risk if criminals later misuse hospitality-related data from any source.

You can also run a free exposure scan of your email to check whether your address has already appeared in known breach datasets elsewhere. That kind of check does not prove involvement in this specific listing, but it can show whether your email is already circulating in broader breach corpuses and whether tighter account hygiene is overdue. Stay alert to official statements from the hotel or IHG if they choose to address the claim; until then, SafePay’s listing remains an unconfirmed accusation on a criminal leak site, not a verified account of what happened inside Holiday Inn Vilnius.

AICompiled with AI assistance from public sources and published under our editorial standards.

Editorial & sourcing policy
Recent Breaches is a breach-monitoring service and news aggregator. We do not exfiltrate, host, purchase, or redistribute stolen data, and we do not hold the data claimed in leak-site listings. Incidents are compiled from publicly accessible sources and threat-intelligence platforms and are reported as claims attributed to their source. We promptly correct or remove material shown to be inaccurate — write to support@galaxywarden.com or press@recentbreaches.com.

How this breach connects

SourceLeak-site claim data adapted from RansomLook.io, used under CC BY 4.0.

CompanyHoliday Inn Vilnius security record
84/100
DoxxScan™ · Low doxx risk
B- 76Above-average record

1 reported incident on record.

See Holiday Inn Vilnius’s full breach history →

More recent breaches

by.zivor.co.il Listed by SafePay Ransomware GroupNovember 7, 2026titres-services.net Listed by SafePay Ransomware GroupNovember 4, 2026ruscopackaging.com Listed by SafePay Ransomware GroupNovember 4, 2026prospecthillcamberwell.com.au Listed by SafePay Ransomware GroupNovember 4, 2026

Latest breaches

Read GalaxyWarden’s full analysis of the Holiday Inn Vilnius Listed by SafePay Ransomware Group →

Source: threat-actor leak-site listing

Publicly posted by safepay — unverified claim, pending independent verification. Leak-site claim data adapted from RansomLook.io, used under CC BY 4.0.

Breach listings — particularly those originating from ransomware or leak sites — are third-party claims that may be unverified, incomplete, or inaccurate. A listing does not by itself confirm that a breach occurred or that any specific data was exposed. Severity is an automated assessment, not a definitive rating. Verification status is shown where available.

Attributions to threat groups and methods reflect public reporting and, in some cases, unverified claims made by the groups themselves; they may be incomplete or later revised. Recent Breaches and GalaxyWarden are independent and are not affiliated with, and do not endorse, any company or group named on this page. This information is aggregated from public sources for awareness only and is not legal, security, or investment advice.

ShareXLinkedInFacebookRedditWhatsAppTelegram