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

Ravkoo — September 2021 breach

Clustered 11 filings across 11 jurisdictions · filing window Jan 3, 2022 → Jan 5, 2022 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

11 filings

States

11

Affected · reported

105,000

First → last dated filing

Jan 3, 2022 → Jan 5, 2022

Merge confidence

100%

incident inc_a1fc7f59321c4a30 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe unauthorized access. Intrusion Sep 27, 2021–Dec 7, 2021, discovered Sep 27, 2021. 105,000 individuals reported across the linked filings. Data reported: PHI, Health (basic), Identity (basic), and 1 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
0days

Range of discovered_at dates across filings

Filing span
2days

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 clocksWashington✗ WA AG >90dOregon✗ OR AG >45dMaine⏱ ME AG >30d · 100dHIPAA✓ HHS notifiedSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Incident timeline

Sep 27, 2021breach begins
Sep 27, 2021discovered
Jan 3, 2022first dated filing
Jan 5, 2022most 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 about this breach

  1. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. JAN 3HHS OCRHHS OCR noticefirst filing · states nationwide total 105,000day 0
  3. JAN 3WA AGWA AG notice5,729 WA residentsday 0
  4. JAN 3IN AGIN AG noticestates nationwide total 105,000day 0
  5. JAN 3NH AGNH AG notice600 NH residentsday 0
  6. JAN 3MT AGMT AG notice611 MT residentsday 0
  7. JAN 3MA AGMA AG notice1,517 MA residentsday 0
  8. JAN 3CA AGCA AG noticeno count statedday 0
  9. JAN 4SC AGSC AG notice2,589 SC residents+1d
  10. JAN 5OR AGOR AG noticestates nationwide total 105,000+2d
  11. JAN 5ME AGME AG noticemost recent · states nationwide total 105,000+2d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 27, 2021
WA AG
Discovered
Sep 27, 2021
IL AG + WA AG + NH AG +5
Data types
Health (basic) · Identity (basic) · PHI · PII
HHS OCR + WA AG + NH AG +4
Attack vector
Unauthorized Access
HHS OCR

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)

105,000

Sum of filed state slices

12,851· 12.2% of stated

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

US105,000
WA5,729
SC2,589
MA1,517
IN1,437
MT611
NH600
ME368

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 claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

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

2 days

Cadence

~1 / 0.2d

vs. multi-state median

3.0× faster

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.