Rivers Casino Philadelphia
bd_759840def0340d72 · schema v1 · pii pii-v1
Full breach record for Rivers Casino Philadelphia →2 incidents on fileRivers Casino Philadelphia reported a ransomware incident affecting 2,480 Washington residents. Unauthorized access occurred between Oct 14-22, 2024. Data exposed included names, SSNs, driver's licenses, and passport numbers. Notifications mailed Feb 28, 2025. Credit monitoring offered.
J jump to incidentP pin to compareR raw source
Incident timeline
Oct 14, 2024
Begins
Oct 20, 2024
Discovered
Feb 28, 2025
Filed
vs. sector median
+11 wks slower
Linked disclosures
Why this link?Regulatory filings (8) · sorted by filing gap
- Vermont State AGbd_06e9f96430f78b222025-02-28Verified
- Oregon State AGbd_56d5cd84f996d0d82025-02-28Candidate
- Nebraska State AGbd_619a13f6a4b58b6c2025-02-28Verified
- California State AGbd_97acc729917addf92025-02-28Verified
Show 4 more filings ↓Show fewer ↑up to 60d gap
- Montana State AGbd_dbc44bdcec3996d82025-02-28Verified
- Vermont State AGbd_29756f652db032672024-12-30 · +60dVerified by operator
- Massachusetts State AGbd_687b71bad74b1a362024-12-30 · +60dVerified
- Indiana State AGbd_82234c4f45a536cb2024-12-30 · +60dVerified by operator
Filing propagation · 9 filings · 8 states
View merged incident ↗Pattern: first filing Dec 30 (VT), last Feb 28 (WA) — a 60-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
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.