UnknownHigh
Rivers Casino Philadelphia
bd_56d5cd84f996d0d8 · schema v1 · pii pii-v1
Full breach record for Rivers Casino Philadelphia →Rivers Casino Philadelphia reported a data breach to the Oregon Attorney General. The breach was reported on 2025-02-28. The breach occurred during 10/14/2024 - 10/22/2024. The breach was discovered on 2/16/2025. 1,942,182 individuals were affected. Notice was sent on 2/28/2025.
Leak gap clock✗ Leak >180d12 days discovery → filing
⚠ AG web formThe discovery date came from the AG web-form field, which is systematically later than the detection date stated in the letter. Treat the clock as indicative.
This filing is one of 5 about the same incident.View merged incident
A leak claim by akira about this victim predates this filing by 547 days.View originating leak claim
Linked disclosures
Why this link?Regulatory filings (4) · sorted by filing gap
- bd_06e9f96430f78b22Vermont State AGfiled 2025-02-28Verified
- bd_759840def0340d72Washington State AGfiled 2025-02-28Verified
- bd_97acc729917addf9California State AGfiled 2025-02-28Verified
- bd_dbc44bdcec3996d8Montana State AGfiled 2025-02-28Verified
Source provenance
- Source URL
- https://justice.oregon.gov/consumer/DataBreach/
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
- Filed at
- Feb 28, 2025
- Raw hash
- 615c12bbec0905e81da8bfae9ab21ca880ae11ac3d9abaa1227ea5a256a92624
Reporting entity
- Name
- Rivers Casino Philadelphianorm: rivers casino philadelphia
Victim entity
- Name
- Rivers Casino Philadelphianorm: rivers casino philadelphia
Incident
- Discovered
- Feb 16, 2025
- Materiality determined
- —
- Notification sent
- Feb 28, 2025
- Affected individuals
- 1,942,182
- Data types
- —
- Attack vector
- Unknown
- Threat actor
- External
Compliance
- Time to disclose
- 12 days(12 days from discovery to filing)
- Compliance flags
- Leak >180dOR AG ≤45d
- Discovery-date grounding
- AG web formThe discovery date came from the AG web-form field, which is systematically later than the detection date stated in the letter. Treat the clock as indicative.
Extraction provenance
- Status
- No extraction artifact recorded for this disclosure.