DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed3 filings · 3 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlow sensitivity
Merged incident · 3 filings

Tokyo Electron U.S. Holdings

Clustered 3 filings across 3 jurisdictions · filing window Mar 20, 2025 → Apr 3, 2025. View entity profile → Other incidents for this victim →

✓ affected count, data types, discovery date agreeMerge100%

Determination

Confirmed

Members

3 filings

States

3

Affected · reported

793

First → last filing

Mar 20, 2025 → Apr 3, 2025

Merge confidence

100%

incident inc_c5085482ef054e38 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings. The filings describe unauthorized access. Discovered Feb 19, 2025 — the first regulatory filing landed 29 days later. 793 individuals reported across the linked filings. Data reported: Credentials and Identity (basic). Notifications rolled out on a 14-day schedule across 3 filings beginning Mar 20, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
29days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
14days

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 clocksVermont⏱ VT AG >14 bdayMaryland✓ MD AG ≤30dOregon✓ OR AG ≤45dFull clock table in Litigation Timeline

Incident timeline

? — ?breach window unknown
Feb 19, 2025discovered
notification delay · 29 days
Mar 20, 2025first filing
Apr 3, 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. MAR 20MD AGMD AG noticefirst filing · 3 MD residentsday 0
  2. MAR 21VT AGVT AG noticeno count stated+1d
  3. APR 3OR AGOR AG noticemost recent · states nationwide total 793+14d
  4. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
—
Discovered
Feb 19, 2025
MD AG + VT AG + OR AG
Data types
Credentials · Identity (basic)
MD AG + VT AG
Attack vector
Unauthorized Access
MD 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)

793

Sum of filed state slices

3· 0.4% of stated

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

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

14 days

Cadence

~1 / 7d

vs. multi-state median

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