DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed8 filings · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedinc_ransomhigh sensitivity
Merged incident · 8 filings

National Boat Owners Association — May 2025 breach

Clustered 8 filings across 7 jurisdictions · filing window Jun 6, 2025 → Jan 23, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

8 filings

States

6

Affected · reported

3,580

First → last filing

Jun 6, 2025 → Jan 23, 2026

Merge confidence

100%

incident inc_0b2307d2086a4e4c · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings and 2 unverified claims. The filings describe malware. Intrusion May 7, 2025–Jun 7, 2025, discovered Jun 6, 2025 — the first regulatory filing landed 229 days later (flagged late). 3,580 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 231-day schedule across 6 filings beginning Jun 6, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
229days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
229days 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.

Filing span
231days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksVermont✗ VT AG >45 bdayLeak gap✗ Leak >180dMassachusetts✗ MA AG >90dMaine✗ ME AG >90d · 229dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 7, 2025breach begins
Jun 6, 2025discovered
notification delay · 229 days
Jan 21, 2026first filing
Jan 23, 2026most 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. JUN 6Leak siteinc_ransom postfirst filing · attacker claim · unverifiedday 0
  2. JUL 20Leak siteinc_ransom postattacker claim · unverified+44d
  3. JAN 21VT AGVT AG noticeno count stated+229d
  4. JAN 21NE AGNE AG noticeno count stated+229d
  5. JAN 21MA AGMA AG notice154 MA residents+229d
  6. JAN 21ME AGME AG noticestates nationwide total 3,580+229d
  7. JAN 21IN AGIN AG noticestates nationwide total 3,580+229d
  8. JAN 23NH AGNH AG noticemost recent · states nationwide total 3,580+231d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 15, 2025 – Jun 1, 2025
VT AG
Discovered
Jun 6, 2025· 22d undetected
VT AG + NE AG + MA AG +2
Data types
Financial · Financial account · Identity (basic) · Government ID · PII
VT AG + NE AG + MA AG +2
Attack vector
Third-Party / Supply Chain· INC Ransomware
VT AG

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)

3,580

Sum of filed state slices

235· 6.6% of stated

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

US3,580
MA154
NH40
IN26
ME15

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 report

No press coverage linked yet.

State AG / regulator filing6 members

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

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 23, 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

231 days

Cadence

~1 / 33d

vs. multi-state median

28.9× 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.