DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed9 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 9 filings

The Global Atlantic Financial Group LLC — May 2023 breach

Clustered 9 filings across 8 jurisdictions · filing window Jul 28, 2023 → Sep 14, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

8

Affected · reported

972,485

First → last filing

Jul 28, 2023 → Sep 14, 2023

Merge confidence

100%

incident inc_cef8c12fc5bd4618 · merged by deterministic · confidence 100%

Part of the Pension Benefit Information, LLC supply-chain incident (2023) — at least 28 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe a third-party compromise. Intrusion May 29, 2023–May 30, 2023, discovered May 29, 2023 — the first regulatory filing landed 60 days later; 1 later filing was flagged late. 972,485 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and PII. Notifications rolled out on a 48-day schedule across 9 filings beginning Jul 28, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
60days

Discovered → first regulatory filing

Discovery variance
9days

Range of discovered_at dates across filings

Filing span
48days

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 >45dWashington⏱ WA AG >30dMassachusetts✓ MA credit monitoring dueCalifornia✓ CA 60-day OK · 51dSouth Carolina✓ SC CRA notice dueHawaii✓ HI CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 29, 2023breach begins
May 29, 2023discovered · members disagree
notification delay · 60 days
Jul 28, 2023first filing
Sep 14, 2023most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. JUL 28WA AGWA AG noticefirst filing · 62,433 WA residentsday 0
  2. JUL 28DE AGDE AG noticeno count statedday 0
  3. JUL 28IN AGIN AG noticestates nationwide total 972,485day 0
  4. AUG 8MA AGMA AG notice18,434 MA residents+11d
  5. AUG 8OR AGOR AG noticestates nationwide total 972,485+11d
  6. AUG 14CA AGCA AG noticeno count stated+17d
  7. AUG 21SC AGSC AG notice14,913 SC residents+24d
  8. AUG 24HI AGHI AG notice4,949 HI residents+27d
  9. SEP 14HI AGHI AG noticemost recent · no count stated+48d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 29, 2023 – May 30, 2023
WA AG
Discovered
May 29, 2023HI AGMay 31, 2023DE AGJun 7, 2023WA AG + OR AG + CA AG +1filings disagree on discovery
Data types
Identity (basic) · Government ID · PII
WA AG + DE AG + CA AG +3
Attack vector
Third-Party / Supply Chain
WA 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)

972,485

Sum of filed state slices

133,605· 13.7% of stated

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

US972,485
WA62,433
IN32,876
MA18,434
SC14,913
HI4,949

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
Reviewed
operator-reviewed Oct 29, 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

48 days

Cadence

~1 / 6d

vs. multi-state median

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