DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteHHS OCRState AGConfirmed12 records · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforceddispossessorcritical sensitivity
Merged incident · 12 records

PAN-AMERICAN LIFE INSURANCE GROUP, INC. — May 2023 breach

Clustered 12 records across 9 jurisdictions: 10 filings and 2 leak-site claims · filing window Dec 4, 2023 → Dec 7, 2023 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

12 records

States

9

Affected · reported

105,387

First → last dated filing

Dec 4, 2023 → Dec 7, 2023

Merge confidence

100%

incident inc_942664d739bb4e65 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings and 2 unverified claims. The filings describe hacking. Intrusion May 28, 2023–May 31, 2023, discovered May 30, 2023. 105,387 individuals reported across the linked filings. Data reported: Government ID, Biometric, Identity (basic), and 4 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
128days

Range of discovered_at dates across filings

Filing span
3days

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 clocksWashington✗ WA AG >90dOregon✗ OR AG >45dLeak gap⏱ Leak >90dMaine⏱ ME AG >30d · 186dFull clock table in Litigation Timeline

Sensitive data

biometricidentity_government

Incident timeline

May 28, 2023breach begins
May 30, 2023discovered · members disagree
Dec 4, 2023first dated filing
Dec 7, 2023most 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. OCT 16Leak sitedispossessor postfirst record · attacker claim · unverifiedday 0
  2. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  3. JUN 16Leak sitecl0p postattacker claim · unverified+243d
  4. DEC 4MT AGMT AG notice1,981 MT residents+414d
  5. DEC 4CA AGCA AG noticeno count stated+414d
  6. DEC 4HHS OCRHHS OCR noticestates nationwide total 94,807+414d
  7. DEC 4WA AGWA AG notice616 WA residents+414d
  8. DEC 4HHS OCRHHS OCR noticestates nationwide total 105,387+414d
  9. DEC 4MA AGMA AG notice179 MA residents+414d
  10. DEC 4OR AGOR AG noticestates nationwide total 105,387+414d
  11. DEC 4ME AGME AG noticestates nationwide total 105,387+414d
  12. DEC 7NH AGNH AG noticemost recent · 48 NH residents+417d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 28, 2023
CA AG
Discovered
May 30, 2023IL AGJun 1, 2023WA AG + OR AG + ME AGOct 5, 2023NH AGfilings disagree on discovery
Data types
Biometric · Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI
MT AG + CA AG + HHS OCR +4
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)

105,387

Sum of filed state slices

3,194· 3.0% of stated

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

US105,387
MT1,981
WA616
ME370
MA179
NH48

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 claim2 members

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

Press / market report

No press coverage linked yet.

State AG / regulator filing10 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 22, 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

3 days

Cadence

~1 / 0.4d

vs. multi-state median

2.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.