DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed6 records · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedransomhubcritical sensitivity
Merged incident · 6 records

YOROZU — October 2024 breach

Clustered 6 records across 5 jurisdictions: 5 filings and 1 leak-site claim · filed Jun 2, 2026 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

6 records

States

5

Affected · reported

20,627

First → last dated filing

Jun 2, 2026

Merge confidence

100%

incident inc_5c48ed05ca9a4244 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 1 unverified claim. The filings describe a ransomware attack. Intrusion Oct 9, 2024–Oct 13, 2024, discovered Dec 19, 2025 — the first regulatory filing landed 165 days later. 20,627 individuals reported across the linked filings. Data reported: Government ID, Biometric, Financial account, and 4 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
165days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
589days before filing

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. 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
0days

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 >180dFull clock table in Litigation Timeline

Sensitive data

biometricidentity_government

Incident timeline

Oct 9, 2024breach begins
Dec 19, 2025discovered
notification delay · 165 days
Jun 2, 2026first dated filing
—watching for filings

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. OCT 14Leak siteransomhub postfirst record · attacker claim · unverifiedday 0
  2. JUN 2VT AGVT AG notice1 VT residents+596d
  3. JUN 2NH AGNH AG notice2 NH residents+596d
  4. JUN 2IN AGIN AG noticestates nationwide total 20,627+596d
  5. JUN 2NE AGNE AG noticefiling day not on record · no count stated—
  6. JUN 2MA AGMA AG noticemost recent · 8 MA residents+596d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 9, 2024 – Oct 13, 2024
NH AG
Discovered
Dec 19, 2025· 436d undetected
NH AG + NE AG
Data types
Biometric · Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PII
VT AG + NH AG + NE AG +1
Attack vector
Ransomware
NH 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)

20,627

Sum of filed state slices

33· 0.2% of stated

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

US20,627
IN22
MA8
NH2
VT1

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 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Sep 29, 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

0 days

Cadence

~1 / 0d

vs. multi-state median

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