MUREX PETROLEUM CORPORATION
bd_765558bad22f7e8c · schema v1 · pii pii-v1
Full breach record for MUREX PETROLEUM CORPORATION →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Akira on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
Murex Petroleum Corporation is engaged in the acquisition, develo pment and operation of oil and gas properties in North America. We are ready to upload 25 GB of documents. Lots of confidential d ocuments, employee information (SSN, DOB, address, passport/SSN/D L scans), detailed financial information (reports, invoices, so o n), NDAs, etc.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jun 30, 2025
Claim posted
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Siteakirabd_605df93111f849762025-05-27 · +34dVerified by operator
Regulatory filings (7) · sorted by filing gap
- Nebraska State AGbd_15b289258e7374f42026-01-27 · +211dCandidate
- Vermont State AGbd_194759e4e9d2beb12026-01-27 · +211dVerified
- Montana State AGbd_29206e5dd2ea978a2026-01-27 · +211dVerified
- Massachusetts State AGbd_2d474235197917922026-01-27 · +211dVerified
Show 3 more filings ↓Show fewer ↑up to 214d gap
- Indiana State AGbd_440672c7f491e9952026-01-27 · +211dVerified
- Maine State AGbd_c1efa654a1ceba3d2026-01-27 · +211dVerified
- New Hampshire State AGbd_11739785f1f07b5d2026-01-30 · +214dVerified
Filing propagation · 8 filings · 7 states
View merged incident ↗Pattern: first filing Jun 30, last Jan 30 (NH) — a 214-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
akira
According to ransomware.live, The Akira ransomware group is said to have emerged in March 2023, and there's much speculation about its ties to the former CONTI ransomware group. It's worth noting that with the end of CONTI's operation, several affiliates migrated to independent campaigns such as Royal, BlackBasta, and others. According to some reports, Akira affiliates also work with other ransomware operations, such as Snatch and BlackByte, as an open directory of tools used by an Akira operator was identified, which also had connections to the Snatch ransomware. The first version of the Akira ransomware was written in C++ and appended files with the '.akira' extension, creating a ransom note named 'akira_readme.txt,' partially based on the Conti V2 source code. However, on June 29, 2023, a decryptor for this version was reportedly released by Avast. Subsequently, a version was released that fixed the decryption flaw on July 2, 2023. Since then, the new version is said to be written in Rust, this time called 'megazord.exe,' and it changes the extension to '.powerranges' for encrypted files. Most of Akira's initial access vectors use brute-force attempts on Cisco VPN devices (which use single-factor authentication only). Additionally, exploitation of CVEs: CVE-2019-6693 and CVE-2022-40684 for initial access has been identified. Source: https://github.com/crocodyli/ThreatActors-TTPs