Murex Petroleum Corporation reported a data breach to the Montana Attorney General. The breach was reported on 2026-01-27. The breach occurred on 05/27/2025. 294 Montana residents were affected.
Affected (this filing): 294
Clustered 2 filings across 2 jurisdictions · filing window Jan 27, 2026 → Jan 30, 2026. View entity profile → Other incidents for this victim →
incident inc_9e6d0e5e3d674411 · 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
May 27, 2025
When the intrusion reportedly occurred, per the linked filings
May 27, 2025
Reported by NEW HAMPSHIRE AG filing
Murex Petroleum Corporation reported a data breach to the Montana Attorney General. The breach was reported on 2026-01-27. The breach occurred on 05/27/2025. 294 Montana residents were affected.
Affected (this filing): 294
Murex Petroleum Corporation notified the New Hampshire Attorney General of a ransomware incident discovered on May 27, 2025. The breach potentially affected one New Hampshire resident, exposing name and tax identification number. Murex contained the threat, engaged forensic investigators, and notified credit bureaus. Notifications were sent on January 27, 2026, offering credit monitoring services.
Affected (this filing): 1
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.