DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SitePressState AGConfirmed7 records · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedbianlianhigh sensitivity
Merged incident · 7 records

Mizuno USA, Inc. — August 2024 breach

Clustered 7 records across 5 jurisdictions: 5 filings, 1 press report and 1 leak-site claim · filed Jan 30, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

7 records

States

5

Affected · reported

1,329

First → last dated filing

Jan 30, 2025

Merge confidence

100%

incident inc_23206016ca60468a · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings, 1 press report and 1 unverified claim. The filings describe unauthorized access. Intrusion Aug 21, 2024–Oct 29, 2024, discovered Nov 6, 2024 — the first regulatory filing landed 85 days later. 1,329 individuals reported across the linked filings. Data reported: Government ID, Financial account, and Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
85days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
82days 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 >30dMaine⏱ ME AG >30d · 85dMaryland⏱ MD AG >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 21, 2024breach begins
Nov 6, 2024discovered
notification delay · 85 days
Jan 30, 2025first 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. NOV 6Leak sitebianlian postfirst record · attacker claim · unverifiedday 0
  2. JAN 30IN AGIN AG noticestates nationwide total 1,329+85d
  3. JAN 30MA AGMA AG notice14 MA residents+85d
  4. JAN 30ME AGME AG notice1 ME residents+85d
  5. JAN 30MD AGMD AG noticemost recent · 5 MD residents+85d
  6. JAN 30NE AGNE AG noticefiling day not on record · 6 NE residents—
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 21, 2024
IN AG
Discovered
Nov 6, 2024· 77d undetected
ME AG + MD AG + NE AG
Data types
Financial account · Identity (basic) · Government ID
MA AG + ME AG + MD AG +1
Attack vector
Unauthorized Access
ME 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)

1,329

Sum of filed state slices

34· 2.6% of stated

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

US1,329
MA14
IN8
NE6
MD5
ME1

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 report1 member

Unlocks: incident narrative, operational impact. Still no compliance clock.

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
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 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

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.