Skip to content
cisonews.net

Incident · 8-K Item 1.05

Data I/O reports ransomware traced to a third-party firewall vulnerability

Compiled from public records. Updated 2026-11-10. By the cisonews.net Desk.

Data I/O Corporation disclosed in an Item 1.05 Form 8-K filed with the SEC on August 21, 2025 that it experienced a ransomware incident on certain internal IT systems on August 16, 2025. The filings do not state what personal information was involved or how many people were affected, and a second filing dated September 10, 2025 said the incident was contained and remediated.

Entries like this one, in Wednesday’s docket

Wednesdays

Unsubscribe any time.

What happened at Data I/O, and when?

The company reported that the ransomware incident took place on August 16, 2025, affecting certain of its internal IT systems. After discovery, it activated response protocols and took containment steps. It also brought in outside cybersecurity experts for recovery work and an investigation.

How did the ransomware get into Data I/O?

The September filing gave an origin that the first filing did not. The company said the attack was not targeted, and began with a vulnerability in a commercially available third-party firewall service. The filing does not name the firewall provider, and neither filing names a ransomware group.

Did the attack stop Data I/O's production?

The first filing said the disruption reached communications, shipping, receiving and manufacturing production, and that the timeline for full restoration was unknown. By September 10, 2025 the company said the affected systems were back. It also said no revenue appeared lost.

On cost, the company estimated about $388,000 in expenses for remediation, restoration and investigation, falling in the quarter ending September 30, 2025. It said this will likely have a material effect on its results of operations and financial condition. The first filing had already said expected costs were reasonably likely to be material.

What did the Data I/O ransomware attack cost?

Data I/O's annual report for 2025, filed on April 16, 2026, describes the ransomware incident and its cost.

It says the August 2025 attack shut down most of its global operating systems, disrupted the business, including timely processing of some shipments, and brought remediation costs of about $388,000 in the third quarter of 2025.

Data I/O's remediation bill is the smallest of the thirteen figures in the guide to filings after the 8-K, which compares what later filings say incidents cost.

The effect on sales lasted into 2026. Data I/O's 10-Q for the quarter ended June 30, 2026 says bookings rose late in the quarter as customers stopped delaying purchases over trade and tariff worries, and as sales processes disrupted by the ransomware incident resumed. That sits beside the September 2025 filing's view that no revenue appeared lost: the later report points to sales work that was delayed, not orders that were cancelled.

DateWhat happenedSource
August 16, 2025Ransomware hits internal IT systems8-K
August 21, 2025Item 1.05 8-K filed8-K
September 10, 2025Second 8-K: contained, systems restored, about $388,000 of costs, origin in a third-party firewall8-K
April 16, 202610-K for 2025 repeats the cost and the shutdown of most global systems10-K
August 14, 202610-Q: disrupted sales processes had resumed10-Q

What is still unknown?

The first filing said the company would notify affected individuals and regulators as appropriate. The September filing then said it did not believe further action was needed. Neither document says whether any data was taken, what categories of information were involved, or whether any notification letters were sent.

How this disclosure's timing compares

Data I/O disclosed 5 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.

Other technology incidents on cisonews.net

  • DreamHost, Breach notice, first disclosed November 2, 2026
  • Photon Health, Breach notice, first disclosed October 28, 2026; affected: approximately 1706 Rhode Island residents
  • Indico Data Solutions, Breach notice, first disclosed October 27, 2026; affected: 79 Rhode Island residents
  • Stitch Connect Inc, Breach notice, first disclosed September 21, 2026; affected: 113,727 people in total (Indiana AG record)
  • IDScan.net, Breach notice, first disclosed September 18, 2026; 27,624 affected in total (Indiana Attorney General)

All technology incidents

Sources

  1. 2025-08-21 · AData I/O Corporation, Form 8-K (SEC EDGAR), published August 21, 2025
  2. 2025-09-10 · AData I/O Corporation, Form 8-K (SEC EDGAR), published September 10, 2025
  3. 2026-04-16 · AData I/O, Form 10-K for the period ended 2025-12-31 (SEC EDGAR), published April 16, 2026
  4. 2026-08-14 · AData I/O, Form 10-Q for the period ended 2026-06-30 (SEC EDGAR), published August 14, 2026
  5. 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.