DisclosureLens
State AGConfirmed9 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedshinyhunters
Merged incident · 9 filings

Carnival Corporation Ltd. — March 2021 breach

Clustered 9 filings across 7 jurisdictions · filing window May 21, 2021 → Oct 18, 2021 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

9 filings

States

7

Affected · reported

20,992

First → last dated filing

May 21, 2021 → Oct 18, 2021

Merge confidence

100%

incident inc_5ff18231a98c4c12 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. Intrusion Mar 12, 2021–Mar 19, 2021, discovered Mar 19, 2021. 20,992 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 2 more. Notifications rolled out on a 150-day schedule across 8 dated filings beginning May 21, 2021. 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
150days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksOregon✗ OR AG >45dMaine⏱ ME AG >30d · 211dFull clock table in Litigation Timeline

Incident timeline

Mar 12, 2021breach begins
Mar 19, 2021discovered
May 21, 2021first dated filing
Oct 18, 2021most 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 about this breach

  1. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. MAY 21IN AGIN AG noticefirst filing · states nationwide total 20,992day 0
  3. MAY 21MT AGMT AG notice44 MT residentsday 0
  4. MAY 25NH AGNH AG notice69 NH residents+4d
  5. OCT 6MT AGMT AG notice63 MT residents+138d
  6. OCT 16ME AGME AG noticestates nationwide total 20,992+148d
  7. OCT 18NH AGNH AG notice79 NH residents+150d
  8. OCT 18OR AGOR AG noticestates nationwide total 20,992+150d
  9. OCT 18CA AGCA AG noticemost recent · no count stated+150d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 12, 2021
IN AG
Discovered
Mar 19, 2021· 7d undetected
IL AG + MT AG + NH AG +2
Data types
Identity (basic) · Government ID · Health (basic) · PII · Financial account
MT AG + NH AG + ME AG +1
Attack vector
Unauthorized Access
MT 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)

20,992

Sum of filed state slices

479· 2.3% of stated

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

US20,992
IN243
ME94
NH79
MT63

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 claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing9 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
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

150 days

Cadence

~1 / 21.4d

vs. multi-state median

25.0× slower

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.