Case Library / Vishing (Voice Phishing) / Carnival's 2026 data breach: one vishing call, 6 million people
Vishing (Voice Phishing) Documented incident

Carnival's 2026 data breach: one vishing call, 6 million people

A caller posing as Carnival's IT security team got an employee's login in April 2026. The attacker copied data on nearly 6 million people. What was taken.

Share:

Social Engineering Examples·8 sources

On 10 April 2026, someone phoned a Carnival Corporation employee pretending to be from Carnival's own IT security team and got the employee's login details. With them, the attacker reached "a limited portion" of Carnival's IT systems and copied personal data. Carnival later notified 5,995,277 people. The ShinyHunters extortion group claimed the attack, but Carnival hasn't confirmed that. Status: Documented incident, company disclosure.

Key takeaways

  • One phone call did it. Carnival described no malware, phishing email or software exploit.
  • The caller posed as internal security, the team people trust most with their accounts.
  • Carnival caught the unusual account activity four days later, through monitoring rather than a report from the employee.
  • Stolen data included names, addresses, dates of birth and passport or driving licence numbers.

Timeline

Date Event
10 April 2026 Vishing call; the employee gives up their credentials
14 April 2026 Carnival's security team spots unusual activity on the account and blocks it
22 April 2026 Investigation confirms personal data was copied
27 May 2026 Public disclosure, state notices and letters to affected people begin
26 June 2026 Carnival's quarterly SEC filing covers the incident and the lawsuits

Carnival brought in outside security experts, told law enforcement, and said it saw no further unauthorised activity after 14 April.

Tip: "I'm from IT security" is a strong opener because it sounds like the people protecting you. Verify it the same way you'd verify anyone else.

What was taken

According to Carnival's notice to the Iowa Attorney General, the unencrypted data included:

  • Full names and postal addresses
  • Email addresses and phone numbers
  • Dates of birth
  • Government ID numbers: passport and/or driving licence

Carnival is the parent of Carnival Cruise Line, Holland America Line, Princess, Costa, Cunard, Seabourn, AIDA and P&O. Have I Been Pwned linked leaked data to Holland America Line's Mariner Society loyalty programme. Carnival hasn't confirmed that detail. It offered affected US customers two years of free credit monitoring.

Who was behind it

Carnival hasn't named anyone. ShinyHunters, an extortion group, claimed the breach on its leak site and said it took more than 8.7 million records. That's higher than Carnival's count and unconfirmed.

Reporters compared the method to the 2025 UK retail breaches at Marks & Spencer, Co-op and Harrods, where callers fooled help desks. No primary source links the two. The overlap is in the playbook: attackers going after the IT support layer by phone. See the MGM case for an earlier example.

Six proposed class actions were filed in federal court in southern Florida and later combined. In its June filing, Carnival said it doesn't expect them to have a material effect on its finances. It hasn't given a cost for the incident.

What would have stopped it

  • Call back on a known number before giving credentials or approving anything, however senior or internal the caller sounds.
  • Phishing-resistant MFA, such as hardware keys, so a stolen password alone isn't enough.
  • A simple rule: IT security never asks for your password. Ever.
  • Monitoring that catches odd logins quickly. Carnival's caught this one in four days; faster is better.
  • Limit what one account can reach, so "a limited portion" really is limited.

See also vishing and how to prevent vishing.

Common questions

How was Carnival hacked in 2026?

An attacker phoned an employee pretending to be from Carnival's IT security team and got their login details, then used them to copy customer data.

How many people were affected?

Carnival notified about 5,995,277 people. ShinyHunters claimed 8.7 million records, which Carnival hasn't confirmed.

What data was stolen?

Names, addresses, emails, phone numbers, dates of birth and passport or driving licence numbers.

Was ShinyHunters behind the Carnival breach?

The group claimed it, but Carnival hasn't confirmed who was responsible.

Sources
Cite this case

Social Engineering Examples. “Carnival's 2026 data breach: one vishing call, 6 million people”. Accessed 3 November 2026. https://socialengineeringexamples.com/carnival-corporation-employee-vishing-breach-2026

Attack Chain & Defense
1Reconnaissance
What happened

The attacker likely identified a specific Carnival employee and gathered enough organizational detail, such as the employee's name, role, and the existence and naming conventions of Carnival's internal IT security team, to make an impersonation call sound credible, typically drawn from sources like LinkedIn, corporate directories, or other public-facing OSINT, consistent with the broader 2025-2026 vishing wave documented at Marks & Spencer, Co-op, Harrods, and MGM Resorts.

The control that would have stopped it

Employee-facing OSINT exposure, such as LinkedIn roles and organizational structure, is very hard to eliminate at enterprise scale; the realistic control assumes attackers already have this information and hardens the process it later gets used against (identity verification during any credential-related contact), rather than trying to hide it.

2Pretext and channel preparation
What happened

The attacker likely prepared an internal-IT-security pretext and a calling approach designed to sound legitimate to the target, a pattern consistent with documented service-desk and vishing tradecraft in the broader wave this case is compared against; Carnival's own notices do not detail the specific technical delivery method used for the call.

The control that would have stopped it

Employee training that specifically covers the scenario of an unsolicited call claiming to be internal IT or security, paired with a clear organizational policy that internal IT/security will never request credentials or an MFA reset over a live phone call alone.

3Vishing call and credential theft (April 10, 2026)
What happened

Per Carnival's notice to the Iowa Attorney General, an unauthorized actor placed a voice-phishing call to a Carnival employee, impersonated a member of Carnival's internal IT security team, and successfully obtained the employee's account credentials.

The control that would have stopped it

Callback or out-of-band verification, requiring any credential-related request to be confirmed through a separate, pre-established channel such as a known internal extension or ticketing system, regardless of the caller's apparent authority.

4Unauthorized account access
What happened

Using the stolen credentials, the actor logged into and accessed a limited portion of Carnival's IT environment, per Carnival's disclosure, going undetected until Carnival's IT security team identified the unusual account activity four days later on April 14, 2026.

The control that would have stopped it

Use phishing-resistant MFA and tightly controlled account-recovery procedures to reduce the risk of unauthorized account access.

5Data exfiltration
What happened

Before Carnival blocked the account, the actor illegally copied unencrypted personal information, including full names, addresses, email addresses, phone numbers, dates of birth, and government identification numbers, on nearly 6 million people; Carnival's investigation confirmed the exfiltration on April 22, 2026.

The control that would have stopped it

Anomaly-based monitoring and data-loss-prevention controls tuned to flag unusual data access or bulk transfers from a single account shortly after a credential change, plus encryption of sensitive fields at rest so a copied file is less immediately usable; Carnival's own April 14 detection shows this class of control working, just not fast enough to prevent the exfiltration that had already begun.

6Extortion, monetization, and disclosure
What happened

The ShinyHunters extortion group publicly claimed responsibility on a leak site, asserting theft of over 8.7 million records including internal corporate data (a claim Carnival has not confirmed), consistent with the group's documented pattern of using stolen data for extortion leverage; Carnival disclosed the breach publicly on May 27, 2026, and later disclosed related class-action litigation in its June 26, 2026 Form 10-Q.

The control that would have stopped it

Rapid third-party incident-response engagement, law-enforcement notification, and prompt, legally compliant breach disclosure, all of which Carnival did, limit an attacker's extortion leverage and downstream harm even after data has already left the network.

Quick Facts
Victim
Carnival Corporation & plc, the world's largest cruise operator, parent of Carnival Cruise Line, Holland America Line, Princess Cruises, Costa, Cunard, Seabourn, AIDA,
and P&O; roughly 5,995,277 individuals notified.
Company
Carnival Corporation & plc
Location
Carnival Corporation is headquartered in Miami, Florida, USA; affected individuals notified were primarily U.S. residents
(notice also filed with the Iowa Attorney General as one of several U.S. state regulators).
Date
2026-04-10 (vishing call and credential theft) to 2026-05-27 (public disclosure); SEC Form 10-Q filed 2026-06-26
Impact
Carnival did not disclose a specific dollar loss tied to the incident itself.
BasisunquantifiedNo loss tied to the incident disclosed; litigation was pending at the last filing
Six purported class-action lawsuits were filed in April 2026 in the U.S. District Court for the Southern District of Florida and were later consolidated; in its Form 10-Q for the quarter ended May 31, 2026 (filed June 26, 2026), Carnival stated it believes the outcome of this litigation will not have a material impact on its consolidated financial statements. Carnival offered affected U.S. individuals two years of complimentary identity/credit monitoring (via TransUnion per the notice), a remediation cost that was not itemized in dollars.
Status
Documented incident
Case Type
Real-World Incident
Sector
Hospitality, Gaming & Travel
Threat Actor
Organized Crime
Explore more

Related Cases

Browse by what this case has in common with others in the library.