MalwareManufacturingManufacturingRansomwareData EncryptedData ExfiltratedCustomer Data InvolvedIdentity (basic)Government IDHealth (basic)Financial accountMediumContained

Dayton Superior Corporation

bd_be49042a2dabe77f · schema v1 · pii pii-v1

Severity

Medium

Discovered

Jul 24, 2022

Filed

Aug 31, 2022

To disclose

5 weeks

Affected

2state residents only

Linked

4 records

Confidence

66%

Full breach record for Dayton Superior Corporation →2 incidents on file

Dayton Superior Corporation (DSC), a manufacturing firm, notified the NH Attorney General of a ransomware incident discovered on July 24, 2022. The attack encrypted databases and files, leading to the compromise of HR data for 2 NH residents (employees/beneficiaries). Data included names, SSNs, driver's licenses, and health/financial data. DSC isolated systems, engaged forensic experts, notified the FBI and DHS, and offered 2 years of credit monitoring.

J jump to incidentP pin to compareR raw source

Leak gap clock⏱ Leak >30d5 weeks discovery → filing

⚠ occurrence dateThe stored discovery date equals the breach OCCURRENCE date. Detection is normally later, so this OVERSTATES the delay — a 'late' verdict here may not be real.

Incident timeline

discovery → filing · 5 weeks / 38 days

Jul 24, 2022

Begins

Jul 24, 2022

Discovered

Aug 31, 2022

Filed

This filing is one of 4 records about the same incident.View merged incident

A leak claim by lockbit_3 about this victim was first seen 38 days before this filing.View originating leak claim

Linked disclosures

Why this link?

Ransomware claims (1)

Leak Sitelockbit_3bd_696e652627d241522022-07-24 · +38dVerified by operator

Regulatory filings (2) · sorted by filing gap

New Hampshire State AGbd_01e854a6eac5f7682022-08-29 · +2dVerified by operator
Indiana State AGbd_57a485bd8171cdc52022-08-19 · +12dVerified by operator

Name: Thompson Hine LLP
norm: thompson hine

Name: Dayton Superior Corporation
norm: dayton superior
Domain: daytonsuperior.com
Industry: Manufacturingllm

Discovered: Jul 24, 2022
Breach occurred: Jul 24, 2022
Undetected for: 0 daysoccurrence → discovery
Materiality determined: —
Notification sent: Aug 19, 2022
Affected individuals: 2state-resident count only
Data types: Identity (basic)Government IDHealth (basic)Financial account
Data elements: Social Security numberDate of birth
Attack vector: Ransomware
MITRE ATT&CK: T1486 Data Encrypted for ImpactT1041 Exfiltration Over C2 ChannelT1119 Automated Collection
Threat actor: ExternalFinancial
Regulator citations: Notified the Federal Bureau of InvestigationNotified the U.S. Department of Homeland SecurityNotified the New Hampshire Office of the Attorney General

During the incident: Moved quickly to isolate the security incident and restore its networks and systems to a normal state of operation
Engaged leading security experts to further investigate the matter and help assess the scope of the cyberattack
Began notifying all individuals whose personal data may have been affected
Established a dedicated call support line and website
Proactively engaged both the Federal Bureau of Investigation and the U.S. Department of Homeland Security
Changes made: Retained independent third-party IT security consultants to analyze the incident
Ensuring the strength of its information security programs and tools and its data security hygiene to prevent future security incidents
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 5 weeks(38 days from discovery to filing)
Compliance flags: Leak >30d
Discovery-date grounding: occurrence dateThe stored discovery date equals the breach OCCURRENCE date. Detection is normally later, so this OVERSTATES the delay — a 'late' verdict here may not be real.

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 3 filings · 2 states

View merged incident ↗

Indiana State AGAug 19 · first

New Hampshire State AG+10d

New Hampshire State AG+12d · this page

Pattern: first filing Aug 19 (IN), last Aug 31 (NH) — a 12-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

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

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

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

Source URL: https://mm.nh.gov/files/uploads/doj/remote-docs/dayton-superior-20220831.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Aug 31, 2022
Raw hash: ede98669c30ae9c7c0857d31235dd4687c84c09c42a173ff9de92570a3dc6f71

Linked disclosures

Ransomware claims (1)

Regulatory filings (2) · sorted by filing gap

Reporting entityThompson Hine LLP

Victim entityDayton Superior Corporation

Incidentdiscovered Jul 24, 2022

Stated responseMoved quickly to isolate the security incident and restore its networks and systems to a normal state of operation

ComplianceLeak >30d

Extraction provenanceno artifact recorded

Source provenancemm.nh.gov