DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SitePressState AGConfirmed17 records · 15 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedshinyhuntershigh sensitivity
Merged incident · 17 records

Carnival Corporation Ltd. — April 2026 breach

Clustered 17 records across 15 jurisdictions: 15 filings, 1 press report and 1 leak-site claim · filing window May 27, 2026 → May 28, 2026 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

17 records

States

15

Affected · reported

5,995,277

First → last dated filing

May 27, 2026 → May 28, 2026

Merge confidence

100%

incident inc_dfbb2f9be48b4f54 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 15 regulatory filings, 1 press report and 1 unverified claim. The filings describe a phishing attack. Intrusion Apr 10, 2026–Apr 14, 2026, discovered Apr 14, 2026. 5,995,277 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and PII. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
0days

Range of discovered_at dates across filings

Filing span
1days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap⏱ Leak >30dMaine⏱ ME AG >30d · 43dWashington⏱ WA AG >30dMassachusetts⏱ MA AG >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 10, 2026breach begins
Apr 14, 2026discovered
May 27, 2026first dated filing
May 28, 2026most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing and leak-site claim in this incident

  1. APR 18Leak siteshinyhunters postfirst record · attacker claim · unverifiedday 0
  2. MAY 1IL AGIL AG noticefiling day not on record · no count stated—
  3. MAY 27IN AGIN AG noticestates nationwide total 5,995,277+39d
  4. MAY 27NH AGNH AG notice11,477 NH residents+39d
  5. MAY 27NE AGNE AG noticefiling day not on record · no count stated—
  6. MAY 27ME AGME AG noticestates nationwide total 5,995,277+39d
  7. MAY 27DE AGDE AG noticeno count stated+39d
  8. MAY 27MT AGMT AG notice5,690 MT residents+39d
  9. MAY 27IA AGIA AG noticeno count stated+39d
  10. MAY 27WA AGWA AG notice54,960 WA residents+39d
  11. MAY 27OR AGOR AG noticestates nationwide total 5,995,277+39d
  12. MAY 27CA AGCA AG noticeno count stated+39d
  13. MAY 28MA AGMA AG notice46,241 MA residents+40d
  14. MAY 28TX AGTX AG noticestates nationwide total 5,995,277+40d
  15. MAY 28VT AGVT AG notice3,915 VT residents+40d
  16. MAY 28SC AGSC AG noticemost recent · 134,156 SC residents+40d
  17. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 10, 2026
IN AG
Discovered
Apr 14, 2026· 4d undetected
IL AG + NH AG + NE AG +10
Data types
Identity (basic) · Government ID · PII
IL AG + NH AG + IA AG +10
Attack vector
Phishing
NH AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

5,995,277

Sum of filed state slices

1,151,329· 19.2% of stated

81% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US5,995,277
TX800,060
SC134,156
IN85,084
WA54,960
MA46,241
NH11,477
ME9,746
MT5,690
VT3,915

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report1 member

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing15 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 9, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

1 days

Cadence

~1 / 0.1d

vs. multi-state median

6.0× faster

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.