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

THYSSENKRUPP MATERIALS, LLC — December 2020 breach

Clustered 9 filings across 7 jurisdictions · filing window Jan 19, 2021 → Jan 27, 2021 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

9 filings

States

7

Affected · reported

10,462

First → last dated filing

Jan 19, 2021 → Jan 27, 2021

Merge confidence

100%

incident inc_846884e439d74aaf · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. Intrusion Dec 28, 2020, discovered Dec 28, 2020. 10,462 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 4 more. Notifications rolled out on a 8-day schedule across 8 dated filings beginning Jan 19, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
0days

Range of discovered_at dates across filings

Filing span
8days

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 clocksMaine✓ ME AG ≤30d · 25dWashington✓ WA AG ≤30dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 28, 2020breach begins
Dec 28, 2020discovered
Jan 19, 2021first dated filing
Jan 27, 2021most recent dated filing

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 about this breach

  1. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. JAN 19IN AGIN AG noticefirst filing · states nationwide total 10,462day 0
  3. JAN 22ME AGME AG noticestates nationwide total 9,207+3d
  4. JAN 26WA AGWA AG notice1,250 WA residents+7d
  5. JAN 26CA AGCA AG noticeno count stated+7d
  6. JAN 26MA AGMA AG notice474 MA residents+7d
  7. JAN 26ME AGME AG noticestates nationwide total 10,462+7d
  8. JAN 26ME AGME AG noticestates nationwide total 10,462+7d
  9. JAN 27NH AGNH AG noticemost recent · 2 NH residents+8d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 28, 2020
IN AG
Discovered
Dec 28, 2020
IL AG + ME AG + WA AG +1
Data types
Employment · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
ME AG + WA AG + CA AG +2
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)

10,462

Sum of filed state slices

2,254· 21.5% of stated

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

US10,462
WA1,250
IN527
MA474
NH2
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 claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing9 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 Jun 12, 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

8 days

Cadence

~1 / 1.1d

vs. multi-state median

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