Skip to main content

Ransomware victim disclosure

All victims

Marina Bay Sands

listed as marinabaysands.com -  Singapore Hotel (Internal Server) · Claimed by Babuk2 · listed 1 year ago

16m
Age
since listed · data leaked

Status timeline

  1. ListedMar 12, 2025
  2. Data leakeddate unknown

At a glance

Group
Babuk2
Status
Data leaked
Country
Singapore
Listed on leak site
Mar 12, 2025

About the victim

AI dossier — public-source company profile

Marina Bay Sands is one of Singapore's most prominent luxury integrated resorts, featuring a 2,561-room hotel, casino, convention facilities, shopping mall, and restaurants. Operated by Las Vegas Sands Corporation, it is a major tourism and business destination in Singapore's Marina Bay district.

Industry
Luxury Hospitality & Integrated Resort
Address
10 Bayfront Avenue, Singapore 018956
Employees
7000-10000
Founded
2010

Attack summary

Severity: high — Confirmed breach of a major hospitality operator with access to sensitive guest data, financial records, and operational systems. Despite limited post detail, the target's scale and guest data exposure history in hospitality breaches warrants high severity. Published disclosure without ransom indicates potential data publication threat.

Babuk2 group claims to have compromised an internal server at Marina Bay Sands. The leak post provides minimal detail on the scope of data exfiltration or encryption, stating only the target and location without specifying operational impact or data categories.

high

Data the group says was taken

AI dossier — extracted from the leak post
  • internal server data
  • unspecified systems

What the group claims

marinabaysands.com -  Singapore Hotel (Internal Server)

Sources

Source

Indexed 1 year 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 babuk2

Babuk2 appears to be a recently emerged ransomware operation first observed in January 2025, representing either a new variant or successor to the original Babuk ransomware group, with apparent financial motivations based on their targeting patterns across multiple sectors and geographic regions. Given the limited timeframe since their emergence and the naming convention, this group likely operates independently or represents a rebrand/evolution of previous Babuk operations, though definitive attribution remains unclear due to the recency of their activities. Based on their targeting patterns across diverse sectors including public sector entities, technology companies, healthcare organizations, and manufacturing firms, the group appears to employ broad-spectrum attack methodologies typical of modern ransomware operations, though specific technical details regarding their initial access vectors, encryption methods, and extortion tactics have not yet been extensively documented by major security researchers. With 180 documented victims across multiple countries including significant activity in the United States, Brazil, India, Indonesia, and China within just the first month of 2025, Babuk2 has demonstrated a notably aggressive operational tempo, though specific high-profile incidents or ransom demands have not yet been publicly detailed by major cybersecurity firms or law enforcement agencies. The group appears to remain actively operational as of early 2025, though their recent emergence means long-term operational patterns and potential law enforcement responses are still developing. The group has been linked to 180 public disclosures across our corpus. First observed on a leak site on January 27, 2025; most recent post April 23, 2025. The operation is currently inactive.

Timeline of this disclosure

  • March 12, 2025marinabaysands.com -  Singapore Hotel (Internal Server) listed by babuk2on the group's public leak site

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, marinabaysands.com -  Singapore Hotel (Internal Server) is reported in Singapore, a country with 45 ransomware disclosures in our corpus.

If your organisation is affected

A listing by babuk2 means marinabaysands.com -  Singapore Hotel (Internal Server) 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 babuk2'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.