Resort Data Processing — December 2024 breach

Clustered 10 filings across 6 jurisdictions · filing window Mar 20, 2025 → May 15, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

Affected · reported

6,556

First → last filing

Mar 20, 2025 → May 15, 2025

Merge confidence

100%

incident inc_742bef014d184088 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. The filings describe hacking. Intrusion Dec 24, 2024–Apr 17, 2025, discovered Jan 28, 2025 — the first regulatory filing landed 51 days later. 6,556 individuals reported across the linked filings. Data reported: PII, Identity (basic), PCI, and 2 more. Notifications rolled out on a 56-day schedule across 10 filings beginning Mar 20, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

51days

Discovered → first regulatory filing

Discovery variance

106days

Range of discovered_at dates across filings

Filing span

56days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksMaine✓ ME AG ≤30d · 21dOregon✓ OR AG ≤45dFull clock table in Litigation Timeline

No cross-filing comparison data available for this incident.

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.