DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteSEC 8-KState AGConfirmed8 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlockbit_3high sensitivity
Merged incident · 8 filings

HAYNES INTERNATIONAL, INC. — June 2023 breach

Clustered 8 filings across 5 jurisdictions · filing window Jun 11, 2023 → Oct 20, 2023. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

8 filings

States

4

Affected · reported

2,119

First → last filing

Jun 11, 2023 → Oct 20, 2023

Merge confidence

100%

incident inc_6935e83764bf48a6 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 3 unverified claims. The filing describes a ransomware attack. Intrusion Jun 6, 2023–Jun 10, 2023, discovered Jun 10, 2023 — the first regulatory filing landed 3 days later. 2,119 individuals reported across the linked filings. Data reported: Government ID, Financial account, and Identity (basic). Notifications rolled out on a 131-day schedule across 5 filings beginning Jun 11, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
3days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
2days before filing

Days between the first leak-site claim and the first regulatory filing. 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
131days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay

Regulatory clocksLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jun 6, 2023breach begins
Jun 10, 2023discovered
notification delay · 3 days
Jun 13, 2023first filing
Oct 20, 2023most 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 11Leak sitelockbit_3 postfirst filing · attacker claim · unverifiedday 0
  2. JUN 13SEC 8-KSEC 8-K noticeno count stated+2d
  3. JUN 21SEC 8-KSEC 8-K noticeno count stated+10d
  4. JUL 26Leak sitedispossessor postattacker claim · unverified+45d
  5. AUG 5Leak sitelockbit_3 postattacker claim · unverified+55d
  6. OCT 20MA AGMA AG notice5 MA residents+131d
  7. OCT 20MT AGMT AG notice1 MT residents+131d
  8. OCT 20IN AGIN AG noticemost recent · states nationwide total 2,119+131d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 10, 2023
SEC 8-K
Discovered
Jun 10, 2023
SEC 8-K + MT AG
Data types
Financial account · Identity (basic) · Government ID
MA AG + MT AG
Attack vector
Ransomware
MT 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)

2,119

Sum of filed state slices

1,466· 69.2% of stated

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

US2,119
IN1,460
MA5
MT1

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

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

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

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

131 days

Cadence

~1 / 18.7d

vs. multi-state median

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