MarineMax, Inc.
bd_23b6b8daee8338b2 · schema v1 · pii pii-v1
Full breach record for MarineMax, Inc. →Press / market disclosure — not a breach-notification filing
A media or market posting that confirms an incident but carries no breach-notification fields, so compliance clocks aren't assessable. The summary below is extracted from the coverage — verify against the source.
Billion-dollar boat seller MarineMax reports cyberattack to SEC. MarineMax: MarineMax, one of the largest boat sellers in the world, reported to the Securities and Exchange Commission (SEC) a cyberattack that disrupted its operations, starting on Sunday. The company implemented its incident response and business continuity protocols, resulting in disruptions, but continued to operate and engaged cybersecurity experts to investigate. MarineMax did not confirm whether data was stolen, but stated that sensitive data was not stored in the computer environment affected by the incident, and the material impact on the company's operations remains to be determined. Linked ransomware group: rhysida.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Mar 10, 2024
Press report
—
Corroborated · see linked filings
This record's own dates cannot anchor compliance clocks; see the linked filings.
Attack → press
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (10) · sorted by filing gap
- SEC 8-Kbd_8a1ed142962d25ff2024-03-12 · +2dVerified
- SEC 8-Kbd_f40953669866c89c2024-04-01 · +22dVerified
- Indiana State AGbd_0f878f76066c5f222024-07-16 · +128dVerified by operator
- Massachusetts State AGbd_1172f515803033fd2024-07-16 · +128dVerified by operator
Show 6 more filings ↓Show fewer ↑up to 128d gap
- South Carolina State AGbd_1e2d33b188b249382024-07-16 · +128dVerified
- New Hampshire State AGbd_29639741801d07d32024-07-16 · +128dVerified by operator
- Vermont State AGbd_8fa0e6de8ec422e12024-07-16 · +128dVerified by operator
- Maine State AGbd_a019d7e057c3ca542024-07-16 · +128dVerified
- California State AGbd_f6e3aae64c5b56982024-07-16 · +128dVerified by operator
- Montana State AGbd_fb1d2c8bf0d356b12024-07-16 · +128dVerified by operator
Showing first 10 of 11 linked disclosures.
Filing propagation · 10 filings · 8 states
View merged incident ↗Pattern: first filing Mar 12, last Jul 16 (MT) — a 126-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Cascade drawn from the first 10 linked disclosures of 11 — the full spread may be wider.
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
- incident type + narrative only (may be machine-translated)
- discovery date
- materiality
- affected count
- data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
rhysida
According to ransomware.live, Rhysida is a ransomware-as-a-service (RAAS) group that emerged in May 2023. The group utilizes a namesake ransomware through phishing attacks and Cobalt Strike to breach the targets' networks and deploy their payloads. The group threatens to publicly distribute exfiltrated data if the ransom is not paid, and it's worth mentioning that Rhysida is still in the early stages of development. The ransomware leaves PDF notes in the affected folders, instructing victims to contact the group through its portal, and payment is made via Bitcoin. After encryption, the ransomware appends the extension '.ryshida' to encrypted files. Source: https://github.com/crocodyli/ThreatActors-TTPs