DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
HHS OCRState AGConfirmed5 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 5 filings

Bako Diagnostics — December 2021 breach

Clustered 5 filings across 5 jurisdictions · filing window Jan 1, 2022 → Feb 25, 2022. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

5 filings

States

5

Affected · reported

25,745

First → last filing

Jan 1, 2022 → Feb 25, 2022

Merge confidence

100%

incident inc_e944fa7d3e2b4116 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe unauthorized access. Intrusion Dec 21, 2021–Dec 28, 2021, discovered Dec 21, 2021 — the first regulatory filing landed 11 days later. 25,745 individuals reported across the linked filings. Data reported: Government ID, PHI, Identity (basic), and 2 more. Notifications rolled out on a 55-day schedule across 5 filings beginning Jan 1, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
11days

Discovered → first regulatory filing

Discovery variance
7days

Range of discovered_at dates across filings

Filing span
55days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksCalifornia✓ CA 60-day OK · 59dHIPAA✓ HHS notifiedMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 21, 2021breach begins
Dec 21, 2021discovered · members disagree
notification delay · 11 days
Jan 1, 2022first filing
Feb 25, 2022most 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. FEB 25CA AGCA AG noticeno count stated+55d
  3. FEB 25HHS OCRHHS OCR noticestates nationwide total 25,745+55d
  4. FEB 25MT AGMT AG notice29 MT residents+55d
  5. FEB 25MA AGMA AG noticemost recent · 1 MA residents+55d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 21, 2021 – Dec 28, 2021
CA AG
Discovered
Dec 21, 2021IL AGDec 28, 2021CA AG + MT AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
CA AG + HHS OCR + MT AG +1
Attack vector
Unauthorized Access
CA 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)

25,745

Sum of filed state slices

30· 0.1% of stated

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

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

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

55 days

Cadence

~1 / 13.8d

vs. multi-state median

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