DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteHHS OCRState AGConfirmed11 records · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedblacksuithigh sensitivity
Merged incident · 11 records

Reventics — December 2022 breach

Clustered 11 records across 8 jurisdictions: 10 filings and 1 leak-site claim · filing window Feb 10, 2023 → Jul 12, 2023 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

11 records

States

8

Affected · reported

4,212,823

First → last dated filing

Feb 10, 2023 → Jul 12, 2023

Merge confidence

100%

incident inc_91ca19acd9174f4a · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings and 1 unverified claim. Intrusion Dec 15, 2022–Dec 19, 2022, discovered Dec 15, 2022. 4,212,823 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 3 more. Notifications rolled out on a 152-day schedule across 8 dated filings beginning Feb 10, 2023. 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
152days

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 clocksCalifornia✗ CA 60-day late · 76dWashington✗ WA AG >90dLeak gap⏱ Leak >90dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 15, 2022breach begins
Dec 15, 2022discovered
Feb 10, 2023first dated filing
Jul 12, 2023most 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. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  3. FEB 10HHS OCRHHS OCR noticefirst filing · states nationwide total 4,212,823day 0
  4. FEB 10MT AGMT AG notice2,856 MT residentsday 0
  5. FEB 13Leak siteblacksuit postattacker claim · unverified+3d
  6. FEB 24CA AGCA AG noticeno count stated+14d
  7. JUN 5CA AGCA AG noticeno count stated+115d
  8. JUN 5MA AGMA AG notice2,965 MA residents+115d
  9. JUN 5WA AGWA AG notice4,764 WA residents+115d
  10. JUN 20OR AGOR AG noticestates nationwide total 3,900,000+130d
  11. JUL 12SC AGSC AG noticemost recent · 77,883 SC residents+152d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 15, 2022
CA AG
Discovered
Dec 15, 2022
IL AG + MT AG + CA AG +2
Data types
Credentials · Health (basic) · Identity (basic) · Government ID · PHI · PII
HHS OCR + MT AG + CA AG +3
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)

4,212,823

Sum of filed state slices

88,468· 2.1% of stated

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

US4,212,823
SC77,883
WA4,764
MA2,965
MT2,856

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 filing10 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 25, 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

152 days

Cadence

~1 / 21.7d

vs. multi-state median

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