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

Renkim Corporation — March 2025 breach

Clustered 11 filings across 11 jurisdictions · filing window Jun 1, 2025 → Aug 8, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

11

Affected · reported

105,518

First → last filing

Jun 1, 2025 → Aug 8, 2025

Merge confidence

100%

incident inc_67231f7cfa6440fa · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe unauthorized access. Intrusion Mar 2, 2025–Mar 3, 2025, discovered Mar 3, 2025 — the first regulatory filing landed 90 days later (flagged late). 105,518 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 1 more. Notifications rolled out on a 68-day schedule across 11 filings beginning Jun 1, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
90days

Discovered → first regulatory filing

Discovery variance
67days

Range of discovered_at dates across filings

Filing span
68days

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 clocksMaine✗ ME AG >90d · 91dVermont✗ VT AG >45 bdaySouth Carolina✓ SC CRA notice dueHIPAA✓ HHS report on timeTexas✓ TX AG ≤30dOregon✓ OR AG ≤45dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 2, 2025breach begins
Mar 3, 2025discovered · members disagree
notification delay · 90 days
Jun 1, 2025first filing
Aug 8, 2025most 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. JUN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. JUN 2SC AGSC AG notice1,076 SC residents+1d
  3. JUN 2NE AGNE AG noticeno count stated+1d
  4. JUN 2NH AGNH AG notice3 NH residents+1d
  5. JUN 2IN AGIN AG noticestates nationwide total 46,864+1d
  6. JUN 2ME AGME AG noticestates nationwide total 46,864+1d
  7. JUN 2HHS OCRHHS OCR noticestates nationwide total 105,518+1d
  8. JUN 3TX AGTX AG noticestates nationwide total 46,864+2d
  9. JUN 23VT AGVT AG noticeno count stated+22d
  10. JUN 23OR AGOR AG noticestates nationwide total 80,178+22d
  11. AUG 8CA AGCA AG noticemost recent · no count stated+68d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 2, 2025
SC AG
Discovered
Mar 3, 2025SC AG + NE AG + NH AG +3May 9, 2025IL AG + HHS OCR + TX AG +1filings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PII
IL AG + NH AG + TX AG +6
Attack vector
Unauthorized Access
SC 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)

105,518

Sum of filed state slices

1,607· 1.5% of stated

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

US105,518
SC1,076
TX466
IN55
ME7
NH3

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

68 days

Cadence

~1 / 6.8d

vs. multi-state median

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