Incident · 8-K Item 8.01
MKS Instruments reports a ransomware event and suspends operations at some facilities
Compiled from public records. Updated 2026-11-10. By the cisonews.net Desk.
MKS Instruments, Inc. told the SEC in a Form 8-K dated February 6, 2023 that it identified a ransomware event on February 3, 2023, which affected certain business systems including production-related systems. The filings do not say that any personal information was involved and give no count of affected people.
Entries like this one, in Wednesday’s docket
Wednesdays
Unsubscribe any time.
What happened at MKS Instruments, and when?
The company says it identified the ransomware event on February 3, 2023 and activated its incident response and business continuity protocols. It also reports that it brought in outside help and informed authorities. The first filing describes the investigation as early-stage.
Which MKS divisions were hit?
The first filing says the incident reached production systems and that the company chose to pause work at some sites as part of containment.
A second 8-K, covering February 13, 2023, reports that the company had moved into recovery. It says work continues on affected sites.
The second filing says the attack had a material first-quarter impact on order processing, shipping and service in the Vacuum Solutions and Photonics Solutions divisions. It says the Materials Solutions division was not affected.
Did MKS expect insurance to cover the costs?
Both filings say the full costs, and how far insurance would offset them, had not been determined.
What did the MKS ransomware attack cost?
MKS Instruments' annual report for 2023, filed on February 27, 2024, sizes the ransomware event.
Because it could not fulfil orders, the company estimates the event cut first-quarter 2023 revenue by about $160 million. It puts its net costs for 2023 at about $15 million.
Lost revenue is a different measure from response costs, and the cost table in the guide to filings after the 8-K labels each of its thirteen figures by what it counts, from MKS's revenue to other companies' remediation bills.
Much of the lost revenue came back later as delayed orders shipped: the November 2023 10-Q estimates those orders added about $90 million to semiconductor revenue in the second quarter and about $20 million in the third.
| Measure | Amount | Period |
|---|---|---|
| Revenue lost to unfilled orders (estimate) | about $160 million | Q1 2023 |
| Delayed orders recovered (estimate) | about $90 million | Q2 2023 |
| Delayed orders recovered (estimate) | about $20 million | Q3 2023 |
| Net costs | about $15 million | 2023 |
How many people did MKS notify in Massachusetts?
Massachusetts' Office of Consumer Affairs and Business Regulation lists a report from MKS Instruments, Inc. dated February 15, 2023 (breach 29037): 1,045 Massachusetts residents affected. The categories it marks as breached are Social Security numbers and account numbers. That count covers Massachusetts residents only.
What is still unknown?
Neither filing states whether any data was taken or accessed, what kinds of information the affected systems held, or how many individuals or customers might be affected. Neither describes a notification letter, a call center or a credit monitoring offer, though Massachusetts' record above counts 1,045 residents in a report received on February 15, 2023. The filings also do not say when the suspended facilities resumed normal operation, and the second filing refers to a press release of February 13, 2023 which this entry does not draw on. The company states that its assessment is ongoing and that it may not update its statements.
How this disclosure's timing compares
MKS Instruments disclosed 3 days after the discovery date its filing gives. Across the 22 other filings under 8-K Item 8.01 on cisonews.net that date discovery to the day, the median gap is 4 days.
The rule behind an Item 8.01 filing
Item 8.01 (Other Events) is the item the SEC's Division of Corporation Finance encouraged companies to use for a cybersecurity incident they have not yet determined to be material, or have determined is not material. Its May 21, 2024 statement says a company that later determines the incident is material should file under Item 1.05 within four business days of that decision. Source: U.S. Securities and Exchange Commission, statement by the Director of the Division of Corporation Finance. The guide Item 8.01 versus Item 1.05: when a cyber incident moves between them 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
- 2023-02-06 · AMKS Instruments, Inc., Form 8-K (SEC EDGAR), published February 6, 2023
- 2023-02-13 · AMKS Instruments, Inc., Form 8-K (SEC EDGAR), published February 13, 2023
- 2024-02-27 · AMKS Instruments, Form 10-K for the period ended 2023-12-31 (SEC EDGAR), published February 27, 2024
- 2023-11-08 · AMKS Instruments, Form 10-Q for the period ended 2023-09-30 (SEC EDGAR), published November 8, 2023
- 2026-11-09 · AMassachusetts Office of Consumer Affairs and Business Regulation, 2023 Data Breach Notification Report, published November 9, 2026
- 2024-05-21 · AU.S. Securities and Exchange Commission, statement by the Director of the Division of Corporation Finance, published May 21, 2024
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.