DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteSEC 8-KState AGConfirmed14 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcl0phigh sensitivity
Merged incident · 14 filings

JACKSON NATIONAL LIFE INSURANCE COMPANY — May 2023 breach

Clustered 14 filings across 9 jurisdictions · filing window Jan 1, 2023 → Aug 17, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

14 filings

States

8

Affected · reported

852,644

First → last filing

Jan 1, 2023 → Aug 17, 2023

Merge confidence

100%

incident inc_9d3f442155504b1f · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 13 regulatory filings and 1 unverified claim. The filings describe hacking. Intrusion May 29, 2023–May 30, 2023, discovered May 29, 2023. 852,644 individuals reported across the linked filings. Data reported: Government ID, Financial account, PII, and 1 more. Notifications rolled out on a 228-day schedule across 13 filings beginning Jan 1, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
22days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 179d

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
228days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay

Regulatory clocksOregon✗ OR AG >45dLeak gap⏱ Leak >30dMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 29, 2023breach begins
May 29, 2023discovered · members disagree
Jan 1, 2023first filing
Aug 17, 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. JAN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. MAR 31MA AGMA AG notice2 MA residents+89d
  3. JUN 26MA AGMA AG notice563 MA residents+176d
  4. JUN 26SEC 8-KSEC 8-K notice700,000 affected+176d
  5. JUN 26MA AGMA AG notice14,622 MA residents+176d
  6. JUN 29Leak sitecl0p postattacker claim · unverified+179d
  7. JUL 19MA AGMA AG notice1 MA residents+199d
  8. JUL 24WA AGWA AG notice22,709 WA residents+204d
  9. JUL 24IN AGIN AG noticestates nationwide total 852,644+204d
  10. JUL 25CA AGCA AG noticeno count stated+205d
  11. JUL 27OR AGOR AG noticestates nationwide total 845,644+207d
  12. JUL 27SC AGSC AG notice62,929 SC residents+207d
  13. AUG 15MA AGMA AG notice1 MA residents+226d
  14. AUG 17OR AGOR AG noticemost recent · states nationwide total 7,000+228d
  15. 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, 2023IL AGMay 31, 2023SC AGJun 1, 2023WA AGJun 20, 2023OR AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
MA AG + WA AG + CA AG +2
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)

852,644

Sum of filed state slices

100,763· 11.8% of stated

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

US852,644
SC62,929
WA22,709
MA14,622
IN503

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 report

No press coverage linked yet.

State AG / regulator filing12 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 25, 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

228 days

Cadence

~1 / 17.5d

vs. multi-state median

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