DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
SEC 8-KState AGConfirmed6 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 6 filings

COREBRIDGE FINANCIAL, INC. — May 2023 breach

Clustered 6 filings across 6 jurisdictions · filing window Jun 26, 2023 → Jul 27, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

6 filings

States

5

Affected · reported

6,500,000

First → last filing

Jun 26, 2023 → Jul 27, 2023

Merge confidence

100%

incident inc_5728c00ed26946f7 · merged by human · confidence 100%

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

Litigation Timing

Notification delay
26days

Discovered → first regulatory filing

Discovery variance
16days

Range of discovered_at dates across filings

Filing span
31days

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.

Regulatory clocksMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 29, 2023breach begins
May 31, 2023discovered · members disagree
notification delay · 26 days
Jun 26, 2023first filing
Jul 27, 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. JUN 26SEC 8-KSEC 8-K noticefirst filing · no count statedday 0
  2. JUL 27CA AGCA AG noticeno count stated+31d
  3. JUL 27OR AGOR AG noticeno count stated+31d
  4. JUL 27IN AGIN AG noticestates nationwide total 6,500,000+31d
  5. JUL 27MT AGMT AG notice15,080 MT residents+31d
  6. JUL 27MA AGMA AG noticemost recent · 90,697 MA residents+31d
  7. 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
CA AG
Discovered
May 31, 2023CA AG + MT AGJun 16, 2023SEC 8-Kfilings disagree on discovery
Data types
Identity (basic) · Government ID · PII
SEC 8-K + MT AG + CA AG +1
Attack vector
Third-Party / Supply Chain
SEC 8-K

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)

6,500,000

Sum of filed state slices

294,198· 4.5% of stated

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

US6,500,000
IN188,421
MA90,697
MT15,080

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

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

SEC 8-K / victim statement1 member

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Merge provenance

Method
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 24, 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

31 days

Cadence

~1 / 6.2d

vs. multi-state median

6.2× 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.