Murray's Cheese
bd_59533785a51a33d9 · schema v1 · pii pii-v1
Full breach record for Murray's Cheese →2 incidents on fileThreat-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
Murray's Cheese, founded in 1940 in Greenwich Village, is the old est cheese shop in New York City. The company specializes in reta il grocery with a focus on premium cheese products. Murray's has earned recognition for its quality offerings and has expanded to multiple locations. The business operates both B2B and B2C models , providing specialty cheese and related products to consumers an d businesses alike. We will upload corporate data soon. Very detailed employee (more than 300 employees) information (passports, DOB, DLs, and so on), financials, clients files, contracts and agreements, projects, i nternal confidential files and so on.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Feb 21, 2026
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?Regulatory filings (4) · sorted by filing gap
- Massachusetts State AGbd_9e4ee48de5f2640a2026-04-21 · +59dVerified by operator
- Maine State AGbd_b7c6cefd9727bb322026-04-21 · +59dVerified by operator
- Indiana State AGbd_bca098857be8dd772026-04-21 · +59dVerified
- New Hampshire State AGbd_2883a9d7b008bc4e2026-05-27 · +95dVerified
Filing propagation · 5 filings · 4 states
View merged incident ↗Pattern: first filing Feb 21, last May 27 (NH) — a 95-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