ASMFC: Atlantic States Marine Fisheries Commission
bd_cdcd3bad1829f42f · schema v1 · pii pii-v1
Full breach record for ASMFC: Atlantic States Marine Fisheries Commission →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group 8base 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
The Commission is committed to ensuring the sustainability of Atlantic Coast fishery resources. Healthy and vibrant resources mean more jobs and more opportunities for those who live along the coast.asmfc.org
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Apr 15, 2024
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 (6) · sorted by filing gap
- Massachusetts State AGbd_7a8bc6310304f49e2024-06-11 · +57dVerified by operator
- Montana State AGbd_1488322330afd4be2024-06-28 · +74dVerified by operator
- Vermont State AGbd_726cfd676d23a28b2024-06-28 · +74dVerified
- Massachusetts State AGbd_5a7397fc9e658c222024-07-01 · +77dVerified by operator
Show 2 more filings ↓Show fewer ↑up to 79d gap
- Maine State AGbd_b4fb1ab69fdd8c232024-07-01 · +77dVerified by operator
- New Hampshire State AGbd_bbdb037c54a80cf62024-07-03 · +79dVerified
Filing propagation · 7 filings · 5 states
View merged incident ↗Pattern: first filing Apr 15, last Jul 3 (NH) — a 79-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.
8base
According to ransomware.live, The 8base Ransomware group made its first appearance in early March 2022, remaining somewhat quiet after the attacks. This group operates like other ransomware actors, engaging in double extortion. However, in mid-May and June 2023, the ransomware operation saw a spike in activity against organizations from various sectors, listing 131 organizations in just 3 months. The 8base data leak site was created and made available in March 2023, claiming honesty and simplicity in its discourse. VMware published a report on 8base, drawing some similarities with the ransomware group `RansomHouse`, pointing out resemblances such as the website used by 8base and the ransom notes presented in its attacks. Interestingly, the 8base Ransomware group does not have its own ransomware developed by the group. Instead, the actors took advantage of other leaked ransomware builders to customize the ransom note and present it to the victim organization as 8base's operation. Source : https://github.com/crocodyli/ThreatActors-TTPs