DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed7 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedransomhubhigh sensitivity
Merged incident · 7 filings

Baim Institute for Clinical Research — June 2024 breach

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

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

7 filings

States

4

Affected · reported

70

First → last filing

Jun 28, 2024 → Aug 1, 2024

Merge confidence

100%

incident inc_44653cbbbcb34947 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings and 3 unverified claims. The filings describe unauthorized access. Intrusion Jun 30, 2024, discovered Jun 30, 2024 — the first regulatory filing landed 31 days later. 70 individuals reported across the linked filings. Data reported: Government ID, PII, and Identity (basic). Notifications rolled out on a 34-day schedule across 4 filings beginning Jun 28, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
31days

Discovered → first regulatory filing

Discovery variance
12days

Range of discovered_at dates across filings

Leak precedence
33days 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
34days

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 >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jun 30, 2024breach begins
Jun 30, 2024discovered · members disagree
notification delay · 31 days
Jul 31, 2024first filing
Aug 1, 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 28Leak siteransomhub postfirst filing · attacker claim · unverifiedday 0
  2. JUN 28Leak siteransomhub postattacker claim · unverifiedday 0
  3. JUL 9Leak siteransomhub postattacker claim · unverified+12d
  4. JUL 31IN AGIN AG noticestates nationwide total 70+33d
  5. JUL 31NH AGNH AG noticeno count stated+33d
  6. JUL 31ME AGME AG noticestates nationwide total 70+33d
  7. AUG 1MA AGMA AG noticemost recent · 47 MA residents+34d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 30, 2024
IN AG
Discovered
Jun 30, 2024NH AGJul 12, 2024ME AGfilings disagree on discovery
Data types
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)

70

Sum of filed state slices

50· 71.4% of stated

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

US70
MA47
ME2
IN1

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

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

34 days

Cadence

~1 / 5.7d

vs. multi-state median

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