DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SitePressHHS OCRState AGConfirmed10 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedabysshigh sensitivity
Merged incident · 10 filings

Bienville Orthopaedic Specialists LLC — February 2023 breach

Clustered 10 filings across 8 jurisdictions · filing window Mar 5, 2023 → Sep 5, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

7

Affected · reported

242,986

First → last filing

Mar 5, 2023 → Sep 5, 2023

Merge confidence

100%

incident inc_029a16c6d0dd4d1b · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings, 1 press report and 2 unverified claims. The filings describe unauthorized access. Intrusion Feb 3, 2023–Mar 5, 2023, discovered Mar 5, 2023 — the first regulatory filing landed 180 days later (flagged late). 242,986 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 2 more. Notifications rolled out on a 184-day schedule across 7 filings beginning Mar 5, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
180days

Discovered → first regulatory filing

Discovery variance
148days

Range of discovered_at dates across filings

Leak precedence
180days 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
184days

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 >180dVermont✗ VT AG >45 bdayFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 3, 2023breach begins
Mar 5, 2023discovered · members disagree
notification delay · 180 days
Sep 1, 2023first filing
Sep 5, 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. MAR 5Leak siteabyss postfirst filing · attacker claim · unverifiedday 0
  2. MAR 27Leak siteabyss postattacker claim · unverified+22d
  3. SEP 1MT AGMT AG notice11 MT residents+180d
  4. SEP 1NH AGNH AG notice9 NH residents+180d
  5. SEP 1VT AGVT AG noticeno count stated+180d
  6. SEP 1MA AGMA AG notice18 MA residents+180d
  7. SEP 1IN AGIN AG noticestates nationwide total 242,986+180d
  8. SEP 5ME AGME AG noticestates nationwide total 242,986+184d
  9. SEP 5HHS OCRHHS OCR noticemost recent · states nationwide total 242,986+184d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 3, 2023 – Mar 5, 2023
MT AG
Discovered
Mar 5, 2023MT AG + NH AG + VT AGJul 31, 2023ME AG + HHS OCRfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
MT AG + NH AG + VT AG +3
Attack vector
Unauthorized Access
MT 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)

242,986

Sum of filed state slices

113· 0.0% of stated

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

US242,986
IN64
MA18
MT11
ME11
NH9

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

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report1 member

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing7 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

184 days

Cadence

~1 / 20.4d

vs. multi-state median

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