DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed15 filings · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcl0phigh sensitivity
Merged incident · 15 filings

ERNST & YOUNG LLP — May 2023 breach

Clustered 15 filings across 12 jurisdictions · filing window Jan 1, 2023 → Apr 30, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

15 filings

States

11

Affected · reported

168,714

First → last filing

Jan 1, 2023 → Apr 30, 2024

Merge confidence

100%

incident inc_c21a0252c2e84970 · merged by human · 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: 14 regulatory filings and 1 unverified claim. The filings describe hacking. Intrusion May 27, 2023–May 31, 2023, discovered May 31, 2023. 168,714 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 485-day schedule across 14 filings beginning Jan 1, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 173d

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
485days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dOregon✗ OR AG >45dWashington⏱ WA AG >30dMaine⏱ ME AG >30d · 70dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 27, 2023breach begins
May 31, 2023discovered
Jan 1, 2023first filing
Apr 30, 2024most 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. JUN 23Leak sitecl0p postattacker claim · unverified+173d
  3. AUG 9DE AGDE AG notice2,408 DE residents+220d
  4. AUG 9MA AGMA AG notice7,320 MA residents+220d
  5. AUG 9WA AGWA AG notice3,571 WA residents+220d
  6. AUG 9CA AGCA AG noticeno count stated+220d
  7. AUG 9ME AGME AG noticestates nationwide total 30,210+220d
  8. AUG 9IN AGIN AG noticestates nationwide total 30,210+220d
  9. AUG 9MT AGMT AG notice238 MT residents+220d
  10. AUG 9NH AGNH AG notice72 NH residents+220d
  11. AUG 22OR AGOR AG noticestates nationwide total 168,714+233d
  12. AUG 24IN AGIN AG noticestates nationwide total 186+235d
  13. AUG 28SC AGSC AG notice3,037 SC residents+239d
  14. AUG 29MA AGMA AG notice2 MA residents+240d
  15. APR 30NH AGNH AG noticemost recent · 629 NH residents+485d
  16. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 27, 2023 – May 31, 2023
WA AG
Discovered
May 31, 2023· 4d undetected
IL AG + WA AG + CA AG +5
Data types
Financial account · Identity (basic) · Government ID · PCI · PII
DE AG + WA AG + CA AG +5
Attack vector
Third-Party / Supply Chain
DE 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)

168,714

Sum of filed state slices

18,565· 11.0% of stated

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

US168,714
MA7,320
WA3,571
SC3,037
DE2,408
IN1,262
NH629
MT238
ME100

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 filing14 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
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

485 days

Cadence

~1 / 34.6d

vs. multi-state median

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