Shields Facilities Management reported a data breach to the Montana Attorney General. The breach was reported on 2025-12-09. The breach occurred from 01/28/2025 to 01/30/2025. 2 Montana residents were affected.
Affected (this filing): 2
Clustered 2 filings across 2 jurisdictions · filed Dec 9, 2025. View entity profile → Other incidents for this victim →
incident inc_4c104bb6790a4923 · 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.
MT NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 28, 2025
When the intrusion reportedly occurred, per the linked filings
Jan 28, 2025
Reported by NEW HAMPSHIRE AG filing
Shields Facilities Management reported a data breach to the Montana Attorney General. The breach was reported on 2025-12-09. The breach occurred from 01/28/2025 to 01/30/2025. 2 Montana residents were affected.
Affected (this filing): 2
Shields Facilities Management, LLC notified the New Hampshire Attorney General on December 9, 2025, of a ransomware incident occurring between January 28 and 30, 2025. The attack encrypted systems and potentially exposed personal information, including names, SSNs, and tax IDs, affecting 24 New Hampshire residents. Shields engaged forensic specialists, conducted a file review, and provided 12 months of credit monitoring to affected individuals.
Affected (this filing): 24
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.