DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed17 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 17 filings

NEW YORK LIFE INSURANCE COMPANY — May 2023 breach

Clustered 17 filings across 7 jurisdictions · filing window Aug 10, 2023 → Oct 23, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

17 filings

States

7

Affected · reported

not comparable

First → last filing

Aug 10, 2023 → Oct 23, 2023

Merge confidence

100%

incident inc_39ef161ed7594417 · merged by deterministic · confidence 100%

Part of the Progress Software Corporation supply-chain incident (2023) — at least 97 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 17 regulatory filings. The filings describe hacking. Intrusion May 29, 2023–May 31, 2023, discovered May 31, 2023 — the first regulatory filing landed 71 days later (flagged late). Data reported: Government ID, Identity (basic), Financial account, and 1 more. Notifications rolled out on a 74-day schedule across 17 filings beginning Aug 10, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
71days

Discovered → first regulatory filing

Discovery variance
56days

Range of discovered_at dates across filings

Filing span
74days

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 clocksMaine✗ ME AG >90d · 145dOregon✗ OR AG >45dWashington⏱ WA AG >30dMassachusetts✓ 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 · 71 days
Aug 10, 2023first filing
Oct 23, 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. AUG 10ME AGME AG noticefirst filing · states nationwide total 1,367day 0
  2. AUG 10CA AGCA AG noticeno count statedday 0
  3. AUG 10MA AGMA AG notice73 MA residentsday 0
  4. AUG 11MA AGMA AG notice270 MA residents+1d
  5. AUG 11IN AGIN AG noticestates nationwide total 25,685+1d
  6. AUG 11ME AGME AG noticestates nationwide total 25,685+1d
  7. AUG 11CA AGCA AG notice1,000,000 CA residents+1d
  8. AUG 21IN AGIN AG noticestates nationwide total 35,062+11d
  9. AUG 23NH AGNH AG notice8 NH residents+13d
  10. AUG 24WA AGWA AG notice1,622 WA residents+14d
  11. AUG 24ME AGME AG noticestates nationwide total 35,062+14d
  12. AUG 24OR AGOR AG noticestates nationwide total 35,062+14d
  13. AUG 24MA AGMA AG notice1,067 MA residents+14d
  14. OCT 23MA AGMA AG notice1,793 MA residents+74d
  15. OCT 23IN AGIN AG noticestates nationwide total 30,167+74d
  16. OCT 23OR AGOR AG noticestates nationwide total 30,167+74d
  17. OCT 23ME AGME AG noticemost recent · states nationwide total 30,167+74d
  18. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 29, 2023
ME AG
Discovered
May 31, 2023CA AG + ME AG + OR AGJun 6, 2023ME AGJun 12, 2023ME AGJul 6, 2023WA AGJul 26, 2023NH AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
ME AG + MA AG + CA AG +2
Attack vector
Unauthorized Access
ME AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Affected residents by state

per-state reported counts

US35,062
CA1,000,000
MA1,793
WA1,622
IN664
ME95
NH8

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 filing17 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 Jun 12, 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

74 days

Cadence

~1 / 4.6d

vs. multi-state median

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