DisclosureLens
Leak SiteState AGConfirmed5 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlockbit_3high sensitivity
Merged incident · 5 filings

YMCA of Central Florida — May 2024 breach

Clustered 5 filings across 5 jurisdictions · filing window Jun 1, 2024 Nov 14, 2024. View entity profile → Other incidents for this victim →

1 cross-filing discrepancyMerge100%

Determination

Confirmed

Members

5 filings

States

4

Affected · reported

11,954

First → last filing

Jun 1, 2024 Nov 14, 2024

Merge confidence

100%

incident inc_f00c61ef15744f42 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion May 16, 2024, discovered May 20, 2024 — the first regulatory filing landed 39 days later (flagged late). 11,954 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 2 more. Notifications rolled out on a 165-day schedule across 4 filings beginning Jun 1, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
39days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
26days before filing

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

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delayno SEC 8-K in this cluster.

Regulatory clocksMaine ME AG >90d · 172dLeak gap Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 16, 2024breach begins
May 20, 2024discovered
notification delay · 39 days
Jun 28, 2024first filing
Nov 14, 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. JUN 1Leak sitelockbit_3 postfirst filing · attacker claim · unverifiedday 0
  2. JUN 28IN AGIN AG noticestates nationwide total 11,954+26d
  3. NOV 8NH AGNH AG notice5 NH residents+159d
  4. NOV 8ME AGME AG noticestates nationwide total 11,954+159d
  5. NOV 14MA AGMA AG noticemost recent · 15 MA residents+165d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 16, 2024
IN AG
Discovered
May 20, 2024· 4d undetected
NH AG + ME AG
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PII
NH AG + ME AG + MA AG
Attack vector
Unauthorized Access
NH 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)

11,954

Sum of filed state slices

42· 0.4% of stated

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

US11,954
IN17
MA15
NH5
ME5

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 filing4 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 Aug 22, 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

165 days

Cadence

~1 / 41.3d

vs. multi-state median

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