Mevion Medical Systems reported a data breach to the Montana Attorney General. The breach was reported on 2021-06-17. The breach occurred from 3/28/2021 to 3/29/2021. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filed Jun 17, 2021. View entity profile → Other incidents for this victim →
incident inc_8ac38610fed84470 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 28, 2021
When the intrusion reportedly occurred, per the linked filings
Apr 8, 2021
Reported by MAINE AG filing
Mevion Medical Systems reported a data breach to the Montana Attorney General. The breach was reported on 2021-06-17. The breach occurred from 3/28/2021 to 3/29/2021. 1 Montana residents were affected.
Affected (this filing): 1
Mevion Medical Systems, a healthcare technology company, reported an external system breach (hacking) that occurred on March 28, 2021, and was discovered on April 8, 2021. The breach compromised the names and Social Security numbers of 730 individuals, including 8 Maine residents. The company provided written notification to the affected individuals on June 17, 2021, and offered 24 months of identity monitoring services through Experian.
Affected (this filing): 8
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.