Metrowest Community Federal Credit Union
bd_116f45d168299bc0 · schema v1 · pii pii-v1
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
MetroWest Community Federal Credit Union offers a range of person al banking services including checking and savings accounts, mobi le banking, and various lending products such as vehicle, home, a nd personal loans. We are ready to upload corporate and client documents. Lots of cl ients documents (DLs, birth and death certs and numerous forms wi th personal information), financial and accounting information, c ourt cases information, employee personal files, etc.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Oct 25, 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?Regulatory filings (5) · sorted by filing gap
- Vermont State AGbd_5f8f7d025bc854f92025-12-29 · +65dVerified by operator
- Massachusetts State AGbd_605a72d6d99a2aa92025-12-29 · +65dVerified by operator
- Vermont State AGbd_27bfc3acf10562e32026-03-06 · +132dVerified
- Indiana State AGbd_0c962b2c99ddb8242026-03-10 · +136dVerified by operator
Show 1 more filing ↓Show fewer ↑up to 136d gap
- Maine State AGbd_3778ce4cf42cd6762026-03-10 · +136dVerified
Filing propagation · 6 filings · 4 states
View merged incident ↗Pattern: first filing Oct 25, last Mar 10 (ME) — a 136-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