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

STEEL PARTNERS HOLDINGS L.P. — April 2020 breach

Clustered 8 filings across 7 jurisdictions · filing window Jun 29, 2020 → Aug 2, 2020. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

8 filings

States

7

Affected · reported

26,356

First → last filing

Jun 29, 2020 → Aug 2, 2020

Merge confidence

100%

incident inc_0a1a7978a8324ba9 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. Intrusion Apr 18, 2020–Apr 29, 2020, discovered May 29, 2020 — the first regulatory filing landed 31 days later. 26,356 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 3 more. Notifications rolled out on a 34-day schedule across 8 filings beginning Jun 29, 2020. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
31days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
34days

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 clocksSouth Carolina✓ SC CRA notice dueMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 18, 2020breach begins
May 29, 2020discovered
notification delay · 31 days
Jun 29, 2020first filing
Aug 2, 2020most 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. JUN 29IN AGIN AG noticefirst filing · states nationwide total 26,356day 0
  2. JUN 29DE AGDE AG noticeno count statedday 0
  3. JUN 29MT AGMT AG notice159 MT residentsday 0
  4. JUN 29SC AGSC AG notice3,628 SC residentsday 0
  5. JUL 16MA AGMA AG notice1,531 MA residents+17d
  6. JUL 16CA AGCA AG noticeno count stated+17d
  7. JUL 30NH AGNH AG notice26 NH residents+31d
  8. AUG 2CA AGCA AG noticemost recent · no count stated+34d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 18, 2020
IN AG
Discovered
May 29, 2020· 41d undetected
DE AG + MT AG + SC AG +1
Data types
Employment · Health (basic) · Identity (basic) · Government ID · PHI · PII
DE AG + MT AG + SC AG +3
Attack vector
Phishing
DE 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)

26,356

Sum of filed state slices

6,212· 23.6% of stated

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

US26,356
SC3,628
MA1,531
IN868
MT159
NH26

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

34 days

Cadence

~1 / 4.9d

vs. multi-state median

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