2023 · Hospitality

MGM Resorts, 2023: a ten-minute phone call to the help desk

Case file · 4 min read · Published 14 September 2026

CASE FILE

MGM Resorts cyberattack

Attackers found an MGM employee on LinkedIn, called the IT help desk pretending to be them, and got a password reset. Slot machines and room keys stopped working for ten days.

Follow the timeline ↓
A person using a laptop beside a desktop monitor
Logan Jeffrey / Unsplash · Personal research · context photograph, not an affected user
People affected
Personal data of customers who transacted with MGM before March 2019
When it happened
September 2023
Made public
11 September 2023
How they got in
Social engineering of the IT help desk to obtain a credential reset, then abuse of the identity provider
Attributed to
Scattered Spider (UNC3944) working with the ALPHV/BlackCat ransomware operation
What it cost
MGM reported roughly $100 million in impact for the quarter, plus about $10 million in one-off costs

What was exposed: Names · Contact details · Dates of birth · Driver's licence numbers · A smaller set of Social Security and passport numbers

FOLLOW THE RECORD

How the story unfolded

Open a step to read the detail. Missing dates stay unknown.

  1. 01Late August 2023

    Caesars Entertainment is compromised via a social engineering attack on an outsourced IT support vendor.

    Review the case-file sources

  2. 02~8 September 2023

    The help desk call to MGM takes place; the attackers obtain a credential reset.

    Review the case-file sources

  3. 0310 – 11 September 2023

    MGM detects the intrusion, shuts down major systems, and files an 8-K disclosure.

    Review the case-file sources

  4. 0414 September 2023

    ALPHV publishes a statement about the attack, disputing parts of the public account.

    Review the case-file sources

  5. 0520 September 2023

    MGM reports that its systems are largely restored.

    Review the case-file sources

  6. 06October 2023

    MGM notifies customers that personal data, including driver's licence numbers and a smaller set of Social Security and passport numbers, was taken for customers who transacted before March 2019.

    Review the case-file sources

  7. 072024 onwards

    Arrests connected to Scattered Spider are announced in the US and UK; class actions consolidate.

    Review the case-file sources

The story behind the breach

On the Las Vegas Strip in September 2023, guests queued at reception because digital room keys had stopped working, slot machines sat dark, and staff wrote restaurant orders on paper. The intrusion that caused it did not involve a vulnerability. It involved a phone call to the IT help desk by somebody who had read an employee's LinkedIn profile.

How did it happen?

Social engineering of the IT help desk to obtain a credential reset, then abuse of the identity provider

What was the motive?

The published account does not establish the motive. We cannot tell what the attackers intended from the exposed data alone.

Claims and demands are reported as such; they do not establish every attacker's intention.

What was the outcome?

MGM reported roughly $100 million in impact for the quarter, plus about $10 million in one-off costs

Reported scale: Personal data of customers who transacted with MGM before March 2019.

Read the full account and timeline · 4 min

On the Las Vegas Strip in September 2023, guests queued at reception because digital room keys had stopped working, slot machines sat dark, and staff wrote restaurant orders on paper. The intrusion that caused it did not involve a vulnerability. It involved a phone call to the IT help desk by somebody who had read an employee's LinkedIn profile.

What happened

The attackers identified an MGM employee from public professional information, the kind of profile everyone in a corporate role maintains, and assembled enough personal and organisational detail to impersonate them convincingly. They then called MGM's internal IT support and asked for help getting back into their account.

The help desk did what help desks exist to do. It verified the caller against the information it was trained to ask for, all of which the caller had, and reset the credentials. That included the multi-factor authentication enrolment, which is the step that matters: a password reset alone is manageable, but a reset that also re-enrols the second factor hands over the whole identity.

With a valid employee identity the attackers went after the identity provider, the single system that issues access to everything else. Having a foothold there converts one employee's account into an ability to issue access at will, and it is why identity infrastructure has become the primary objective in intrusions of this kind rather than an obstacle on the way to one.

ALPHV, the ransomware operation working with them, then deployed ransomware against part of the estate. MGM responded by shutting systems down.

The help desk is not a weak link by accident. It is measured on speed and on user satisfaction, staffed by people rewarded for unblocking colleagues, and its entire function is to restore access to people who have lost it. Every incentive in the role points towards saying yes. Meanwhile the information used to verify a caller, employee number, manager's name, date of birth, office location, is exactly the information that leaks, gets scraped from professional networks, or can be obtained from a previous breach. The verification step is asking for secrets that are not secret.

Ten days of paper

The operational effect was the part the public saw. Room keys stopped working. Check-in ran on manual processes. Slot machines were taken offline, reservations could not be made online, and payouts were handled by hand. Guests filmed the queues.

Almost all of that was self-inflicted, in the sense that MGM chose it. Faced with attackers holding valid identity credentials and moving through the network, the options are to shut things down and lose revenue, or to stay up and risk losing everything. MGM shut down. Recovery took roughly ten days and the company put the financial effect at around $100 million for the quarter.

Caesars Entertainment had been hit by the same crew days earlier and made the other choice, reportedly paying about $15 million. It stayed open. Both companies ended up notifying customers and facing class actions.

The timeline

  1. Late August 2023: Caesars Entertainment is compromised via a social engineering attack on an outsourced IT support vendor.
  2. ~8 September 2023: The help desk call to MGM takes place; the attackers obtain a credential reset.
  3. 10 – 11 September 2023: MGM detects the intrusion, shuts down major systems, and files an 8-K disclosure.
  4. 14 September 2023: ALPHV publishes a statement about the attack, disputing parts of the public account.
  5. 20 September 2023: MGM reports that its systems are largely restored.
  6. October 2023: MGM notifies customers that personal data, including driver's licence numbers and a smaller set of Social Security and passport numbers, was taken for customers who transacted before March 2019.
  7. 2024 onwards: Arrests connected to Scattered Spider are announced in the US and UK; class actions consolidate.

What it changed

Help desk verification was rebuilt across entire industries. The fixes that followed are unglamorous and effective: requiring a video call with an identity document, requiring a manager to approve resets out of band, imposing a mandatory delay on MFA re-enrolment, and refusing to perform resets for privileged accounts over the phone at all.

Identity providers became the crown jewels. Once single sign-on mediates access to every application, its administrative interface is the most valuable surface in the organisation. Separate, phishing-resistant, hardware-backed authentication for those administrative roles became a standard recommendation rather than a mature-programme nicety.

Everyone learned what their own containment decision costs. Most incident response plans in 2023 had no answer to "at what point do we take the revenue-generating systems offline, and who decides". MGM made that decision in public, expensively, and a great many tabletop exercises since have been built around it.

Youth stopped being a proxy for harmlessness. A group whose members included teenagers took a $14 billion company off the internet for ten days. The skills that mattered were research and confidence on the telephone, neither of which requires resources or experience.

If you stayed at an MGM property

Your next steps

Tick off the actions you have taken. Progress lasts while this page is open.

0 actions completed

Were you part of this breach?

Only a result for this incident is shown. On submission, your email is sent through MyRecon to XposedOrNot for a breach lookup. MyRecon does not save this check to your history. Some incidents have no searchable email records.

Questions people ask

How did attackers get into MGM without hacking anything?

They identified an employee through public professional profiles, gathered enough detail to sound like that person, and called the internal IT help desk asking for account recovery. The help desk performed the reset. From there the attackers had a working corporate identity and went after the identity provider that sits behind every other system. The technical skill in this attack was almost entirely conversational.

Why did slot machines stop working?

They did not fail individually. MGM shut down large parts of its own network deliberately to stop the attackers moving further, and modern casino and hotel operations depend on that network for nearly everything, reservations, digital room keys, points of sale, gaming floor systems. The visible chaos was the containment decision, not the attack itself, and that trade-off is one every victim has to make quickly and with poor information.

Did MGM pay a ransom?

MGM has said publicly that it did not pay. Caesars Entertainment, targeted by the same crew shortly before, was widely reported to have paid approximately $15 million. The contrast is instructive: Caesars avoided the operational collapse, MGM avoided funding the group, and both ended up in regulatory filings and class actions regardless.

Who is Scattered Spider?

A loosely organised, largely English-speaking group, many members reportedly young, some teenagers, tracked under names including UNC3944 and Octo Tempest. Their signature is social engineering rather than exploitation: help desk impersonation, SIM swapping, and phishing that targets the account recovery process rather than the password. Several arrests have been made in the US and UK since 2024.

Sources

Read next

Case files are written from the public record: regulatory findings, court filings, company disclosures and contemporaneous reporting, cited above. Figures are the ones the organisation or its regulator finally settled on, which is often not the number first reported, where that differs, the page says so. Disputed accounts are marked as disputed rather than resolved in either direction.

← All case files Breach archive →