NUCOR CORPORATION
bd_5d4a1347ab3beb1c · schema v1 · pii pii-v1
Full breach record for NUCOR CORPORATION →4 incidents on fileNucor Corporation filed an 8-K/A amendment (Item 1.05) on June 20, 2025 supplementing its May 14, 2025 disclosure of a cybersecurity incident. Investigation determined a threat actor illegally accessed Nucor's IT systems and exfiltrated limited data, causing temporary halt of production at some facilities. Affected operations and IT access have been restored; Nucor believes the threat actor no longer has access. Company states the incident has not had and is not reasonably likely to have a material impact on its business or financials.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Jun 20, 2025
Filed
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Linked disclosures
Why this link?Regulatory filings (5) · sorted by filing gap
- Indiana State AGbd_e8dd270c8f1b4b652025-06-24 · +4dVerified
- Vermont State AGbd_f0b0185bf1d1823b2025-06-24 · +4dCandidate
- Massachusetts State AGbd_602a58f53ef5e6fe2025-06-27 · +7dVerified
- New Hampshire State AGbd_9461555a0a074d8a2025-06-27 · +7dVerified
Show 1 more filing ↓Show fewer ↑up to 10d gap
- New Hampshire State AGbd_70306daf12f7c0d82025-06-30 · +10dVerified
Filing propagation · 6 filings · 4 states
View merged incident ↗Pattern: first filing Jun 20, last Jun 30 (NH) — a 10-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.