Incident · 8-K Item 1.05
Nucor halts some production after unauthorized access to IT systems
Compiled from public records. Updated 2026-11-15. By the cisonews.net Desk.
Nucor Corporation told the SEC in an 8-K Item 1.05 filing dated May 14, 2025 that an unauthorized third party had accessed certain information technology systems, leading it to halt some production operations as a precaution. A June 20, 2025 amendment added that the threat actor took limited data, and the filing does not say what kind of data it was or how many people are affected. The notices that followed went to 2,461 people by the total Nucor gave Indiana, and Nucor's next annual report, filed on February 25, 2026, says no cybersecurity incident it has experienced has materially affected the company.
Entries like this one, in Wednesday’s docket
Wednesdays
Unsubscribe any time.
| Date | Event | Record |
|---|---|---|
| May 3, 2025 | Date of breach in Indiana's record | Indiana AG 2025 report |
| May 13, 2025 | Earliest event reported | 8-K Item 1.05 |
| May 14, 2025 | 8-K filed: systems taken offline, some production paused | 8-K Item 1.05 |
| June 20, 2025 | 8-K/A: data was taken; production and access restored | 8-K/A |
| June 24, 2025 | Notices sent to 2,461 people, 32 in Indiana | Indiana AG 2025 report |
| June 27, 2025 | Report to Massachusetts (breach 2025-1115), 1 resident | Massachusetts OCABR 2025 report |
| February 25, 2026 | Form 10-K for 2025: no material effect from past incidents | Form 10-K |
The two dates for the start differ: Indiana's record carries May 3, 2025 as the date of the breach, ten days before the May 13 date in the 8-K. Neither filing explains the gap, so this entry keeps both dates as each record states them.
What happened at Nucor, and when?
The filing lists May 13, 2025 as the date of the earliest event reported. The original report said the company had identified unauthorized third party access to certain systems it uses.
Nucor said it took potentially affected systems offline, activated its incident response plan and notified federal law enforcement. It also said outside cybersecurity experts were assisting the investigation.
The filing does not give the date the access began or the date it was detected.
Which Nucor production was halted?
The company said it paused certain production at various locations out of caution, and that it was already restarting the affected operations when it filed.
The amendment said the incident also temporarily limited access to some IT applications that support operations at some facilities. Neither filing names the locations that stopped or states how long any of them were down.
What did Nucor's June 2025 amendment add?
The investigation found that the actor had taken data from the systems. Nucor said it was reviewing that data and would notify affected parties and regulators where the law requires.
On recovery, the company said production and application access had been restored. It also said it believes the actor no longer has access, and that it restored affected data from backup systems.
How many people did Nucor notify?
Indiana's attorney general lists Nucor Corporation in its 2025 breach report, with notice sent on June 24, 2025 for a breach that occurred on May 3, 2025: 32 Indiana residents and 2,461 people affected in total. The total is the figure the organization reported to Indiana.
What did Massachusetts record?
Massachusetts' Office of Consumer Affairs and Business Regulation lists a report from Nucor Corporation dated June 27, 2025 (breach 2025-1115): 1 Massachusetts residents affected. The categories it marks as breached are Social Security numbers, medical records, driver's license numbers and credit or debit card numbers. That count covers Massachusetts residents only.
What did Nucor's 2025 annual report say about the incident?
The Form 10-K for 2025 does not describe the May 2025 incident by date. Its cybersecurity section says that, as of the report, no risks from cybersecurity threats, including those from incidents the company has experienced, have materially affected it or are reasonably likely to. That is the same conclusion the June 2025 amendment reached, now stated eight months later, with no cost figure attached.
The same section sets out who handles an incident. A management Risk Committee oversees the response, and its members include the Cybersecurity Director, the President of Nucor Business Technology and the General Counsel. The Audit Committee of the board oversees cybersecurity risk. Nucor says its program is based on the NIST Cybersecurity Framework. For how other companies close an incident in later periodic reports, see after the 8-K: how later 10-Q and 10-K filings close a cyber incident, and for other production stoppages, operational shutdowns in 8-K filings.
Did Nucor pay a ransom or name the attacker?
Neither 8-K nor the annual report says. The filings do not use the word ransomware, do not name a threat group and do not mention a payment. They say only that an unauthorized third party accessed systems and took limited data, so this entry records no ransom and no attacker.
Was the Nucor incident material, and what is unknown?
Nucor concluded that the incident has not had, and is not reasonably likely to have, a material impact on its operations, financial condition or results of operations.
The documents leave several points open. They do not describe the type of data taken, whether it relates to employees, customers or business records, or how many individuals are involved. They also do not say how the actor gained access or give a cost figure. The amendment said notifications would follow where required, and the state records above show them: notices sent on June 24, 2025, to 2,461 people in total by Indiana's count.
The rule behind an Item 1.05 filing
Form 8-K Item 1.05 is where a public company reports a cybersecurity incident it has determined to be material. Under the rule the SEC adopted on July 26, 2023, the filing is generally due four business days after the company determines that the incident is material. Source: U.S. Securities and Exchange Commission, press release 2023-139. The guide What is SEC Form 8-K Item 1.05, and what counts as a disclosed cyber incident? reads the rule in full, and the glossary defines Form 8-K Item 1.05.
Other industrials & manufacturing incidents on cisonews.net
- Plant Construction Company, L.P., Breach notice, first disclosed November 13, 2026
- Southwire Company, LLC, Other public record, first disclosed November 12, 2026
- USA Waste-Management Resources, LLC, Breach notice, first disclosed November 6, 2026
- Cotton Incorporated, Breach notice, first disclosed November 2, 2026
- NCH Corporation, Breach notice, first disclosed October 30, 2026; 5,031 affected in total (Indiana Attorney General)
Sources
- 2025-05-14 · ANucor Corporation, Form 8-K (SEC EDGAR), published May 14, 2025
- 2025-06-20 · ANucor Corporation, Form 8-K/A (SEC EDGAR), published June 20, 2025
- 2026-11-09 · AIndiana Attorney General, 2025 data breach year-to-date report, published November 9, 2026
- 2026-11-09 · AMassachusetts Office of Consumer Affairs and Business Regulation, 2025 Data Breach Notification Report, published November 9, 2026
- 2026-02-25 · ANucor Corporation, Form 10-K for fiscal 2025 (SEC EDGAR), published February 25, 2026
- 2023-07-26 · AU.S. Securities and Exchange Commission, press release 2023-139, published July 26, 2023
Tier A: the organization itself (including notices it filed with a state attorney general), a regulator or SEC EDGAR. Tier B: established press. Each fact on this page carries its supporting passage in the page source.
Entries like this one, in Wednesday’s docket
Wednesdays
Unsubscribe any time.