Skip to main content
Darkfield

Ransomware victim disclosure

← All victims

Hotelogix

Claimed by ShadowByt3$ · listed 2 months ago

2m
Age
since listed · data leaked

Status timeline

  1. ListedMay 14, 2026
  2. Data leakeddate unknown

At a glance

Group
ShadowByt3$
Status
Data leaked
Country
Singapore
Sector
Hospitality and Tourism
Listed on leak site
May 14, 2026

About the victim

AI dossier — public-source company profile

Hotelogix is a cloud-based hotel management software provider founded in 2008 and trusted by hotels globally, including clients in the Asia-Pacific region. The company offers a property management system (PMS) covering reservations, front desk operations, housekeeping, point of sale, and analytics. It serves independent hotels and hotel chains, with client data hosted on cloud infrastructure including Amazon S3 and Azure Blob Storage.

Industry
Hotel Management Software (SaaS / Hospitality Technology)
Employees
51-200
Founded
2008

Attack summary

Severity: critical — The breach involves confirmed exfiltration of regulated PII at scale — guest names, home addresses, phone numbers, and financial/payment processing details belonging to hotel guests of at least one named third-party client (Treebo Hotels). This constitutes a multi-party data breach affecting end consumers, with payment-adjacent data and personally identifiable information, meeting the threshold for critical severity.

ShadowByt3$ claims to have exfiltrated approximately 6 GB of data from misconfigured Amazon S3 buckets and Azure Blob Storage belonging to Hotelogix, including internal corporate documents and client-specific data such as guest PII, payment processing details, and stay records belonging to at least one named client (Treebo Hotels). The group has set a ransom demand of $500,000 in BTC or Monero with a deadline of April 14th, threatening public release of all data if unpaid.

critical

Data the group says was taken

AI dossier — extracted from the leak post
  • Internal operational manuals
  • Product upgrade / software documentation PDFs
  • Branding assets (logos, templates, marketing materials)
  • Client guest names, phone numbers, and home addresses
  • Guest stay details (arrival/departure dates, room numbers, room types)
  • Payment processing details (last four digits of cards, transaction IDs, billing amounts, GST/SGST breakdowns)
  • Customer folios / invoices (Treebo Hotels)

What the group claims

We are ShadowByt3$. We have claimed responsibility for hacking Hotelogix. They have been breached through there amazon s3 buckets and azure blobs. They were misconfigured which allowed us to scrape everything inside. This has been are latest campaign. If you don't pay $500,000 in btc or monero all data gets leaked. We are not joking and not playing we will. As you can tell in the sample in the data leak site or url below. We are giving you until April 14th at 12:20 it expires. It gets released. DarkWebinformer if you see this contact us asap through are telegram. Any researchers you can contact them and verify data. Also let them know what we have and have 6gb of data. Tell them if they don't pay by that date they get released and is not being put up for sale. Make the right decision and just getting law enforcement involved is just going to make it worse and as you can see they are helpless and don't do shit about you and don't care about companies. Look at how many companies get reported to the feds, you really think there going to help you. If you do your wrong. You can try to stop us but it doesn't stop the leaks from already being leaked and passed around other researchers or criminals. The following below was stolen: 1. Internal Corporate Data This data pertains to Hotelogix's own business operations and software development: - Operational Manuals: Internal guides for staff on how to use and manage their cloud-based systems. - Product Upgrade PDFs: Documentation detailing recent or upcoming software updates, which can reveal specific system architectures. - Branding Assets: Official logos, templates, and marketing materials (often used by hackers to create more convincing phishing emails). 2. Client-Specific Data (Treebo Hotels) The most critical part of the breach involves data belonging to Hotelogix’s clients. For Treebo Hotels, the stolen files include: - Customer Folios (Invoices): As seen in your image, these contain guest names, phone numbers, and home addresses. - Guest Stay Details: Specific dates of arrival and departure, room numbers, and room types (e.g., "Promotional Room Rent Oak"). - Payment Processing Details: While full credit card numbers are often encrypted, "processing details" can include: Last four digits of cards. Transaction IDs and dates. Billing amounts and tax breakdowns (GST/SGST).

Sources

Source

Indexed 2 months ago

This page surfaces a public ransomware disclosure indexed by Darkfield. Original posts come from the operator's own leak site; we cross-check against ransomware.live, RansomLook and RansomWatch where applicable. Share this URL freely.

Is this your supplier? Your competitor? You?

Pro plans monitor your domain, corporate emails, and crypto wallets across every new ransomware leak-site post, breach dump and Telegram callout — alerts within 5 minutes.

Disclosure context

About ShadowByt3$

ShadowByt3$ is an emerging ransomware group that was first observed in February 2026, appearing to be financially motivated based on its ransomware operations. The group's country of origin and any potential affiliations with other cybercriminal organizations remain unknown due to limited intelligence available on this newly identified threat actor. Given the minimal public documentation available, the group's attack methodology, tools, and operational tactics have not been sufficiently analyzed or reported by major cybersecurity firms or government agencies. No notable campaigns, high-profile victims, or significant ransoms have been publicly documented by CISA, FBI, Mandiant, or other reputable security researchers, with only one known victim reported to date and no specific sector targeting patterns identified. The current operational status of ShadowByt3$ remains unclear due to the limited intelligence available on this recently emerged and relatively unknown ransomware operation. The group has been linked to 13 public disclosures across our corpus. First observed on a leak site on February 25, 2026; most recent post June 16, 2026. The operation is currently active.

Timeline of this disclosure

  • May 14, 2026Hotelogix listed by ShadowByt3$on the group's public leak site

Other recent disclosures by ShadowByt3$

ShadowByt3$ has been linked to 13 public victims on Darkfield. A sample of the most recent:

See the full ShadowByt3$ dossier →

Sector and geography

This disclosure adds to ransomware activity in the Hospitality and Tourism sector, which has 452 disclosures indexed across all operators we track. Geographically, Hotelogix is reported in Singapore, a country with 45 ransomware disclosures in our corpus.

If your organisation is affected

A listing by ShadowByt3$ means Hotelogix appeared on a ransomware extortion site and data attributed to it has been published. If this is your organisation, or a supplier you depend on, the priority is to confirm the intrusion and contain it before the window to act closes.

  • Engage your incident-response team and preserve forensic evidence before remediating — do not wipe affected systems first.
  • Force a password reset and revoke active sessions for exposed accounts; rotate any credentials, API keys or certificates that may have been in the stolen data.
  • Assess regulatory notification duties (GDPR, NIS2, sector regulators) — many carry a 72-hour reporting clock from awareness.
  • Report the incident to your national CERT, SingCERT (Singapore), as required for your jurisdiction.
  • Monitor for the data appearing on ShadowByt3$'s leak site and across paste and breach channels, and brief downstream partners who may be exposed through you.

How we know this. Darkfield monitors public ransomware leak sites continuously, archiving every new disclosure and the data later released against the victim. Each entry on this page is sourced from the operator's own publication and cross-checked against complementary OSINT feeds (RansomLook, ransomware.live, RansomWatch). We do not collect or host stolen data — only the metadata, timestamps and screenshots needed to make the public disclosure searchable and accountable. Records here are corrected when the original post is edited, retracted, or merged with another disclosure.