DisclosureLens
Leak SiteState AGConfirmed7 filings · 3 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlockbit_3high sensitivity
Merged incident · 7 filings

Dayton Superior Corporation — July 2022 breach

Clustered 7 filings across 4 jurisdictions · filing window Jul 24, 2022 Apr 27, 2023. View entity profile → Other incidents for this victim →

1 cross-filing discrepancyMerge100%

Determination

Confirmed

Members

7 filings

States

3

Affected · reported

662

First → last filing

Jul 24, 2022 Apr 27, 2023

Merge confidence

100%

incident inc_5a93811b8a05480b · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 2 unverified claims. The filings describe a ransomware attack. Intrusion Jul 24, 2022, discovered Jul 24, 2022 — the first regulatory filing landed 26 days later (flagged late). 662 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 2 more. Notifications rolled out on a 277-day schedule across 5 filings beginning Jul 24, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
26days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
26days 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
277days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delayno SEC 8-K in this cluster.

Regulatory clocksLeak gap Leak >180dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jul 24, 2022breach begins
Jul 24, 2022discovered
notification delay · 26 days
Aug 19, 2022first filing
Apr 27, 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. JUL 24Leak sitelockbit_3 postfirst filing · attacker claim · unverifiedday 0
  2. AUG 19IN AGIN AG noticestates nationwide total 650+26d
  3. AUG 29NH AGNH AG notice2 NH residents+36d
  4. AUG 31NH AGNH AG notice2 NH residents+38d
  5. MAR 23Leak siteblack_basta postattacker claim · unverified+243d
  6. APR 24IN AGIN AG noticestates nationwide total 662+274d
  7. APR 27MA AGMA AG noticemost recent · 1 MA residents+277d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 24, 2022
IN AG
Discovered
Jul 24, 2022
NH AG
Data types
Financial · Financial account · Health (basic) · Identity (basic) · Government ID
NH AG + MA AG
Attack vector
Ransomware
NH 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)

662

Sum of filed state slices

17· 2.6% of stated

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

US662
IN14
NH2
MA1

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

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing5 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

277 days

Cadence

~1 / 46.2d

vs. multi-state median

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