DisclosureLens
Leak SiteState AGConfirmed4 records · 3 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedqilinhigh sensitivity
Merged incident · 4 records

Yushin America, Inc — February 2025 breach

Clustered 4 records across 3 jurisdictions: 3 filings and 1 leak-site claim · filing window Feb 25, 2025 → Feb 26, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

4 records

States

3

Affected · reported

331

First → last filing

Feb 25, 2025 → Feb 26, 2025

Merge confidence

100%

incident inc_a5f059eff1134438 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings and 1 unverified claim. Intrusion Feb 10, 2025. 331 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 1 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Leak precedence
Noneclaim trailed by 15d

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
1days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 10, 2025breach begins
Feb 25, 2025first filing
Feb 26, 2025most recent filing

No discovery date is recorded on any filing in this cluster, so the notification delay is not computable. Dashed segments fill in as filings merge.

Member cascade — every filing and leak-site claim in this incident

  1. FEB 25NH AGNH AG noticefirst filing · 2 NH residentsday 0
  2. FEB 25IN AGIN AG noticestates nationwide total 331day 0
  3. FEB 26MA AGMA AG notice27 MA residents+1d
  4. MAR 12Leak siteqilin postmost recent · attacker claim · unverified+15d
  5. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 10, 2025
IN AG
Discovered
—
Data types
Financial account · Identity (basic) · Government ID · PII
NH AG + MA 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)

331

Sum of filed state slices

32· 9.7% of stated

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

US331
MA27
IN3
NH2

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 filing3 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 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

1 days

Cadence

~1 / 0.5d

vs. multi-state median

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