DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SitePressSEC 8-KState AGConfirmed13 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedrhysidahigh sensitivity
Merged incident · 13 filings

MarineMax, Inc. — March 2024 breach

Clustered 13 filings across 10 jurisdictions · filing window Mar 10, 2024 → Jul 16, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

13 filings

States

9

Affected · reported

123,494

First → last filing

Mar 10, 2024 → Jul 16, 2024

Merge confidence

100%

incident inc_369379d40eb94b60 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings, 1 press report and 2 unverified claims. The filings describe unauthorized access. Intrusion Mar 1, 2024–Mar 10, 2024, discovered Mar 10, 2024 — the first regulatory filing landed 2 days later (flagged late). 123,494 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 3 more. Notifications rolled out on a 128-day schedule across 10 filings beginning Mar 10, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
2days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
2days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Materiality delta
0days

Discovery to SEC materiality determination

SEC filing delay
2days

Materiality determination to SEC 8-K filing

Filing span
128days

Time between earliest and latest filing

Regulatory clocksSEC✗ SEC 4-day late · 22dMaine✗ ME AG >90d · 128dLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 1, 2024breach begins
Mar 10, 2024discovered
notification delay · 2 days
Mar 12, 2024first filing
Jul 16, 2024most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. MAR 10Leak siterhysida postfirst filing · attacker claim · unverifiedday 0
  2. MAR 12SEC 8-KSEC 8-K noticeno count stated+2d
  3. MAR 20Leak siterhysida postattacker claim · unverified+11d
  4. APR 1SEC 8-KSEC 8-K noticeno count stated+22d
  5. JUL 16ME AGME AG noticestates nationwide total 123,494+128d
  6. JUL 16CA AGCA AG noticeno count stated+128d
  7. JUL 16IN AGIN AG noticestates nationwide total 123,494+128d
  8. JUL 16MT AGMT AG notice72 MT residents+128d
  9. JUL 16MA AGMA AG notice3,139 MA residents+128d
  10. JUL 16SC AGSC AG notice2,147 SC residents+128d
  11. JUL 16NH AGNH AG notice448 NH residents+128d
  12. JUL 16VT AGVT AG noticemost recent · no count stated+128d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 10, 2024
ME AG
Discovered
Mar 10, 2024
SEC 8-K + ME AG + SC AG +1
Data types
Employment · Financial account · Identity (basic) · Government ID · PCI · PII
SEC 8-K + SC AG + NH AG +5
Attack vector
Unauthorized Access
SEC 8-K

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

123,494

Sum of filed state slices

6,287· 5.1% of stated

95% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US123,494
MA3,139
SC2,147
NH448
IN328
ME153
MT72

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim2 members

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report1 member

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing8 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement2 members

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Merge provenance

Method
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 22, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

128 days

Cadence

~1 / 10.7d

vs. multi-state median

16.0× slower

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.