DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed6 records · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedplaycritical sensitivity
Merged incident · 6 records

Vacation Myrtle Beach — June 2025 breach

Clustered 6 records across 5 jurisdictions: 5 filings and 1 leak-site claim · filing window May 15, 2026 → May 20, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

6 records

States

5

Affected · reported

10,750

First → last filing

May 15, 2026 → May 20, 2026

Merge confidence

100%

incident inc_ea92b20e266e41a1 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Jun 16, 2025, discovered Jun 16, 2025 — the first regulatory filing landed 333 days later. 10,750 individuals reported across the linked filings. Data reported: Government ID, Minor, PII, and 5 more. Notifications rolled out on a 5-day schedule across 5 filings beginning May 15, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
333days

Discovered → first regulatory filing

Discovery variance
261days

Range of discovered_at dates across filings

Leak precedence
330days before filing

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. 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
5days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap✗ Leak >180dFull clock table in Litigation Timeline

Sensitive data

identity_governmentminor

Incident timeline

Jun 16, 2025breach begins
Jun 16, 2025discovered · members disagree
notification delay · 333 days
May 15, 2026first filing
May 20, 2026most recent filing

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

Member cascade — every filing and leak-site claim in this incident

  1. JUN 15Leak siteplay postfirst record · attacker claim · unverifiedday 0
  2. MAY 15ME AGME AG noticestates nationwide total 10,750+334d
  3. MAY 15IN AGIN AG notice22 IN residents+334d
  4. MAY 15VT AGVT AG notice6 VT residents+334d
  5. MAY 15NH AGNH AG notice7 NH residents+334d
  6. MAY 20SC AGSC AG noticemost recent · 7,738 SC residents+339d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 16, 2025
ME AG
Discovered
Jun 16, 2025NH AG + SC AGMar 4, 2026ME AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · Minor · PCI · PHI · PII
ME AG + NH AG + SC AG +1
Attack vector
Unauthorized Access
ME 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)

10,750

Sum of filed state slices

7,777· 72.3% of stated

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

US10,750
SC7,738
IN22
NH7
VT6
ME4

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 claim1 member

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

Press / market report

No press coverage linked yet.

State AG / regulator filing5 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 9, 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

5 days

Cadence

~1 / 1.3d

vs. multi-state median

1.2× faster

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.