GR Energy Services reported a data breach to the Montana Attorney General. The breach was reported on 2021-03-03. The breach occurred from 12/1/2020 to 12/18/2020. 7 Montana residents were affected.
Affected (this filing): 7
Clustered 2 filings across 2 jurisdictions · filed Mar 3, 2021. View entity profile → Other incidents for this victim →
incident inc_382319f8d4564f35 · 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
Dec 1, 2020
When the intrusion reportedly occurred, per the linked filings
Dec 18, 2020
Reported by MAINE AG filing
GR Energy Services reported a data breach to the Montana Attorney General. The breach was reported on 2021-03-03. The breach occurred from 12/1/2020 to 12/18/2020. 7 Montana residents were affected.
Affected (this filing): 7
GR Energy Services experienced a data breach that began with a phishing email and escalated into a ransomware attack. The incident occurred between December 1, 2020, and December 7, 2020, and was discovered on December 18, 2020. The breach affected 2 Maine residents, whose names and driver's license or non-driver identification card numbers were compromised. Affected individuals were notified on March 3, 2021, and offered 12 months of credit and cyberscan monitoring.
Affected (this filing): 2
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.