DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed10 records · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedkarakurthigh sensitivity
Merged incident · 10 records

National Board of Osteopathic Medical Examiners — February 2023 breach

Clustered 10 records across 8 jurisdictions: 9 filings and 1 leak-site claim · filing window Jan 4, 2024 → Feb 5, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 records

States

8

Affected · reported

4,310

First → last dated filing

Jan 4, 2024 → Feb 5, 2024

Merge confidence

100%

incident inc_98c94c7b826347c6 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Feb 4, 2023–Feb 13, 2023, discovered Feb 14, 2023. 4,310 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 2 more. Notifications rolled out on a 32-day schedule across 8 dated filings beginning Jan 4, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
324days

Range of discovered_at dates across filings

Filing span
32days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap✗ Leak >180dVermont✗ VT AG >45 bdayFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 4, 2023breach begins
Feb 14, 2023discovered · members disagree
Jan 4, 2024first dated filing
Feb 5, 2024most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing and leak-site claim in this incident

  1. MAR 20Leak sitekarakurt postfirst record · attacker claim · unverifiedday 0
  2. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  3. JAN 4DE AGDE AG noticeno count stated+290d
  4. JAN 31IN AGIN AG noticestates nationwide total 4,310+317d
  5. JAN 31MT AGMT AG notice8 MT residents+317d
  6. JAN 31ME AGME AG noticestates nationwide total 4,310+317d
  7. JAN 31VT AGVT AG noticeno count stated+317d
  8. JAN 31DE AGDE AG noticeno count stated+317d
  9. FEB 1MA AGMA AG notice12 MA residents+318d
  10. FEB 5NH AGNH AG noticemost recent · 2 NH residents+322d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 4, 2023 – Feb 13, 2023
DE AG
Discovered
Feb 14, 2023IL AG + DE AG + MT AG +2Jan 4, 2024ME AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PII
DE AG + MT AG + VT AG +3
Attack vector
Unauthorized Access
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)

4,310

Sum of filed state slices

78· 1.8% of stated

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

US4,310
IN32
ME24
MA12
MT8
NH2

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 filing9 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 16, 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

32 days

Cadence

~1 / 4.6d

vs. multi-state median

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