HackingEnergy & UtilitiesUtilitiesCustomer Data InvolvedPIIIdentity (basic)LowContained

MUREX PETROLEUM CORPORATION

bd_29206e5dd2ea978a · schema v1 · pii pii-v1

Severity

Low

Discovered

May 27, 2025

Filed

Jan 27, 2026

To disclose

35 weeks

Affected

294state residents only

Linked

9 filings

Confidence

66%

Full breach record for MUREX PETROLEUM CORPORATION →

Murex Petroleum Corporation notified Montana and other state residents of unauthorized network access detected on May 27, 2025. The incident potentially involved personal information. The company secured its network, engaged external cybersecurity professionals (Kroll), and is offering complimentary credit monitoring services to affected individuals.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 35 weeks / 245 days

May 27, 2025

Begins

May 27, 2025

Discovered

Jan 27, 2026

Filed

This filing is one of 9 about the same incident.View merged incident

Linked disclosures

Why this link?

Ransomware claims (2)

Leak Siteakirabd_765558bad22f7e8c2025-06-30 · +211dVerified by operator
Leak Siteakirabd_605df93111f849762025-05-27 · +245dVerified by operator

Regulatory filings (6) · sorted by filing gap

Nebraska State AGbd_15b289258e7374f42026-01-27Candidate
Vermont State AGbd_194759e4e9d2beb12026-01-27Verified
Massachusetts State AGbd_2d474235197917922026-01-27Verified
Indiana State AGbd_440672c7f491e9952026-01-27Verified

Show 2 more filings ↓up to 3d gap

Maine State AGbd_c1efa654a1ceba3d2026-01-27Verified
New Hampshire State AGbd_11739785f1f07b5d2026-01-30 · +3dVerified

Name: MUREX PETROLEUM CORPORATION
norm: murex petroleum
Domain: murexpetroleum.com

Name: MUREX PETROLEUM CORPORATION
norm: murex petroleum
Domain: murexpetroleum.com
Industry: Energy & Utilitiesllm

Discovered: May 27, 2025
Breach occurred: May 27, 2025
Undetected for: 0 daysoccurrence → discovery
Materiality determined: —
Notification sent: Jan 27, 2026
Affected individuals: 294state-resident count only
Data types: PIIIdentity (basic)
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid Accounts
Threat actor: External
Initial access: valid_credentials

During the incident: Secured our network
Commenced a prompt and thorough investigation
Working very closely with external cybersecurity professionals
Conducted a thorough review of the potentially impacted data
Providing complimentary credit monitoring services
Secured the services of Kroll to provide identity monitoring
Changes made: Evaluate and modify practices and internal controls to enhance the security and privacy of your personal information
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 35 weeks(245 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 7 filings · 7 states

View merged incident ↗

Nebraska State AGJan 27 · first

Vermont State AGJan 27 · first

Massachusetts State AGJan 27 · first

Indiana State AGJan 27 · first

Maine State AGJan 27 · first

Montana State AGJan 27 · first · this page

New Hampshire State AG+3d

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

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

SEC 8-K / victim statement

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

Source URL: https://dojmt.gov/wp-content/uploads/2026/07/Consumer-notification-letter-1.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jan 27, 2026
Raw hash: 2487ed0ed947c124d6a7b85e96d3cc4b308331e59bc0d6ca1dd4fc45ee84359a

Linked disclosures

Ransomware claims (2)

Regulatory filings (6) · sorted by filing gap

Reporting entityMUREX PETROLEUM CORPORATION

Victim entityMUREX PETROLEUM CORPORATION

Incidentdiscovered May 27, 2025

Stated responseSecured our network

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov