Incident · 8-K Item 1.05
Lee Enterprises reports a network attack that encrypted applications and delayed print distribution
Compiled from public records. Updated 2026-11-11. By the cisonews.net Desk.
Lee Enterprises told the SEC in a Form 8-K signed February 14, 2025 that a cybersecurity attack on February 3, 2025 caused a systems outage, with threat actors encrypting critical applications and taking certain files. The filing does not say whether personal information was involved, and it gives no count of affected people; a state record does.
Entries like this one, in Wednesday’s docket
Wednesdays
Unsubscribe any time.
Personal information was involved: Oregon's Department of Justice records a Lee Enterprises breach notice to 39,779 people, sent June 3, 2025, for a breach on February 3, 2025 that it lists as discovered on May 28, 2025.
What happened at Lee Enterprises, and when?
The company reports that the outage began on February 3, 2025. It says an incident response team including outside cybersecurity experts was activated on discovery.
Preliminary findings are that the network was accessed without authorization. The company says it has notified law enforcement.
Was personal information taken in the Lee Enterprises attack?
The filings do not confirm that any personal data was taken. The original filing says the analysis was still under way and that nothing conclusive had been found. The March 6, 2025 amendment says the question was still open and that Lee expected a definitive answer within several weeks. No categories of personal information are listed in either document.
Which Lee newspapers and services were disrupted?
The outage reached distribution, billing, collections and vendor payments. As of February 12, 2025, weekly and ancillary products had not been restored, and the filing says they account for five percent of operating revenue.
Lee said the financial impact was not yet known but was likely to be material. It also described manual processing of transactions as a stopgap.
What did the March 2025 amendment add?
The amendment reports that the threat was contained and all products were being produced and distributed, with limits remaining. Billing, collections and vendor payments were still delayed.
The amendment also describes a financing step taken to cover remediation and operations. The company's sole lender agreed to waive March 2025 interest and certain lease payments, which are added to principal. On insurance, Lee expects costs above a small retainer to be reimbursed.
What did the Lee Enterprises cyberattack cost?
Lee Enterprises' annual report for the fiscal year ended September 28, 2025, filed on November 26, 2025, counts the cost in cash.
The company says it lost $10.5 million of cash flows to the incident during that fiscal year. It also records $10.1 million of non-cash interest expense tied to a waiver of three monthly interest payments owed to BH Finance LLC, granted because of the February incident.
The table of what thirteen cyber incidents cost sets Lee's lost cash flows beside other companies' response costs, lost profit and lost sales, and labels what each figure measures.
| Date | What happened | Source |
|---|---|---|
| February 3, 2025 | Outage begins; critical applications encrypted and files taken | 8-K |
| February 12, 2025 | Weekly and ancillary products, five percent of operating revenue, still not restored | 8-K |
| March 6, 2025 | 8-K/A: threat contained, all products produced and distributed; lender waives March interest | 8-K/A |
| Fiscal year to September 28, 2025 | $10.5 million of lost cash flows; $10.1 million of non-cash interest from the waiver | 10-K |
What is still unknown?
The filings do not state how the attackers gained access, who they were, or how many people or records were involved. They do not say whether any individuals will be notified, and they contain no call-center or enrollment details. The final cost is also unstated.
How this disclosure's timing compares
Lee Enterprises disclosed 15 days after the discovery date its filing gives. Across the 46 other filings under 8-K Item 1.05 on cisonews.net that date discovery to the day, the median gap is 6 days.
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.
Guides for this kind of filing
Sources
- 2026-11-11 · AOregon Department of Justice, consumer data breach list, published November 11, 2026
- 2025-02-18 · ALee Enterprises, Inc., Form 8-K (SEC EDGAR), published February 18, 2025
- 2025-03-06 · ALee Enterprises, Inc., Form 8-K/A (SEC EDGAR), published March 6, 2025
- 2025-11-26 · ALee Enterprises, Form 10-K for the period ended 2025-09-28 (SEC EDGAR), published November 26, 2025
- 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.