DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed10 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 10 filings

Sarku Japan — January 2022 breach

Clustered 10 filings across 7 jurisdictions · filing window Mar 16, 2022 → Aug 12, 2022. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

10 filings

States

7

Affected · reported

29,239

First → last filing

Mar 16, 2022 → Aug 12, 2022

Merge confidence

100%

incident inc_e4f587985cd945a6 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. The filings describe unauthorized access. Intrusion Jan 13, 2022–Feb 6, 2022, discovered Feb 6, 2022 — the first regulatory filing landed 38 days later. 29,239 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Notifications rolled out on a 149-day schedule across 10 filings beginning Mar 16, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
38days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
149days

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 >30dMaine⏱ ME AG >30d · 38dMassachusetts✓ MA credit monitoring dueOregon✓ OR AG ≤45dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 13, 2022breach begins
Feb 6, 2022discovered
notification delay · 38 days
Mar 16, 2022first filing
Aug 12, 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. MAR 16WA AGWA AG noticefirst filing · 741 WA residentsday 0
  2. MAR 16CA AGCA AG noticeno count statedday 0
  3. MAR 16MA AGMA AG notice1,225 MA residentsday 0
  4. MAR 16ME AGME AG noticestates nationwide total 28,298day 0
  5. MAR 16OR AGOR AG noticestates nationwide total 28,298day 0
  6. MAR 16IN AGIN AG noticestates nationwide total 28,298day 0
  7. MAR 21NH AGNH AG notice97 NH residents+5d
  8. AUG 8CA AGCA AG noticeno count stated+145d
  9. AUG 8ME AGME AG noticestates nationwide total 29,239+145d
  10. AUG 12NH AGNH AG noticemost recent · 104 NH residents+149d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 14, 2022 – Feb 6, 2022
WA AG
Discovered
Feb 6, 2022· 23d undetected
WA AG + CA AG + ME AG +2
Data types
Identity (basic) · Government ID
WA AG + CA AG + ME AG +2
Attack vector
Unauthorized Access
WA 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)

29,239

Sum of filed state slices

2,568· 8.8% of stated

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

US29,239
MA1,225
WA741
IN365
ME133
NH104

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 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 Oct 22, 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

149 days

Cadence

~1 / 16.6d

vs. multi-state median

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