DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
SEC 8-KState AGConfirmed8 filings · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 8 filings

MKS Instruments, Inc — February 2023 breach

Clustered 8 filings across 7 jurisdictions · filing window Feb 6, 2023 → Feb 16, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

6

Affected · reported

1,276

First → last filing

Feb 6, 2023 → Feb 16, 2023

Merge confidence

100%

incident inc_968e8f960dcc4e5b · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. The filings describe a ransomware attack. Intrusion Feb 3, 2023, discovered Feb 3, 2023 — the first regulatory filing landed 3 days later. 1,276 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 4 more. Notifications rolled out on a 10-day schedule across 8 filings beginning Feb 6, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
3days

Discovered → first regulatory filing

Discovery variance
10days

Range of discovered_at dates across filings

Filing span
10days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster.

Regulatory clocksCalifornia✓ CA 60-day OK · 2dMassachusetts✓ MA credit monitoring dueMaine✓ ME AG ≤30d · 3dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Feb 3, 2023breach begins
Feb 3, 2023discovered · members disagree
notification delay · 3 days
Feb 6, 2023first filing
Feb 16, 2023most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. FEB 6SEC 8-KSEC 8-K noticefirst filing · no count statedday 0
  2. FEB 13SEC 8-KSEC 8-K noticeno count stated+7d
  3. FEB 15CA AGCA AG noticeno count stated+9d
  4. FEB 15NH AGNH AG notice203 NH residents+9d
  5. FEB 15MA AGMA AG notice1,045 MA residents+9d
  6. FEB 16ME AGME AG notice8 ME residents+10d
  7. FEB 16MT AGMT AG notice13 MT residents+10d
  8. FEB 16IN AGIN AG noticemost recent · 7 IN residents+10d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 3, 2023
NH AG
Discovered
Feb 3, 2023SEC 8-KFeb 13, 2023CA AG + NH AG + ME AG +1filings disagree on discovery
Data types
Credentials · Employment · Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID
CA AG + NH AG + ME AG +2
Attack vector
Ransomware
SEC 8-K

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Affected residents by state

per-state reported counts

MA1,045
NH203
MT13
ME8
IN7

State AGs report only their own residents; teal bars show each state's reported slice.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing6 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement2 members

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

10 days

Cadence

~1 / 1.4d

vs. multi-state median

1.7× slower

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.