// Adds dimensions UUID, Author and Topic into GA4
Saturday, June 13, 2026
30 C
Singapore

Marina Bay Sands data leak affects over 660,000 members

SINGAPORE: Marina Bay Sands (MBS) is dealing with a significant data breach that has exposed the personal information of approximately 665,000 of its members. In an email to members this week, the luxury integrated resort said the breach occurred on Oct 19th and 20th when unauthorized access was made to the non-casino rewards program “Sands Rewards Lifestyle.”

The breach is believed to have compromised sensitive member information, including their names, email addresses, mobile phone numbers, country of residence, and membership number and level.

MBS told members that its internal investigation has so far yielded no evidence of data misuse by the unauthorized third parties responsible for the breach.

MBS added that it has taken immediate action in response to the breach and has been collaborating with cybersecurity companies to enhance its system and data security measures to prevent future breaches of this nature. It said the casino’s primary membership rewards program, Sands Rewards, remains unaffected by the breach.

In light of this incident, MBS has issued an apology to the affected members and has advised all its members to remain vigilant and monitor their accounts for any unusual or suspicious activities. They have also urged members to change their login passwords regularly as an additional precautionary measure.

- Advertisement -

Hot this week

Ex-PAP MP: Underlying racial issues are real; damage doesn’t disappear when posts are taken down

"This is deeply troubling, and I am glad the Government moved quickly. What struck me was not just the targeting of Singapore's Indian community, but the deeper damage it was trying to cause. The w...

‘Are Malaysians ready to protest?’: Petition removal fuels anger online

After surpassing 400,000 signatures, the “Remove Rohingya from Malaysia” petition was taken down from Change.org, sparking outrage among supporters. Many users on X expressed frustration, claiming ...

Popular Categories

document.addEventListener("DOMContentLoaded", () => { const trigger = document.getElementById("ads-trigger"); if ('IntersectionObserver' in window && trigger) { const observer = new IntersectionObserver((entries, observer) => { entries.forEach(entry => { if (entry.isIntersecting) { lazyLoader(); // You should define lazyLoader() elsewhere or inline here observer.unobserve(entry.target); // Run once } }); }, { rootMargin: '800px', threshold: 0.1 }); observer.observe(trigger); } else { // Fallback setTimeout(lazyLoader, 3000); } });
// //
Enable Notifications OK No thanks