UnknownHigh
Medusind, Inc.
bd_bef150eaeee5f6b3 · schema v1 · pii pii-v1
Full breach record for Medusind, Inc. →Medusind, Inc. reported a data breach to the Oregon Attorney General. The breach was reported on 2025-02-11. The breach occurred during 12/29/2023 - 1/7/2024. The breach was discovered on 12/29/2023. 691,192 individuals were affected. Notice was sent on 1/7/2025.
Oregon clock✗ OR AG >45d14 months discovery → filing
⚠ occurrence dateThe stored discovery date equals the breach OCCURRENCE date. Detection is normally later, so this OVERSTATES the delay — a 'late' verdict here may not be real.
This filing is one of 9 about the same incident.View merged incident
Linked disclosures
Why this link?Regulatory filings (8) · sorted by filing gap
- bd_e16e595df9c8d7edCalifornia State AGfiled 2025-02-11Verified
- bd_e8a96821895972c9Washington State AGfiled 2025-02-11Verified
- bd_166adc1614e76acdDelaware State AGfiled 2025-01-07(35d gap)Verified
- bd_44842e5c901da36aCalifornia State AGfiled 2025-01-07(35d gap)Verified
Show 4 more filings ↓Show fewer ↑up to 35d gap
- bd_4c0617bdd3903364Indiana State AGfiled 2025-01-07(35d gap)Verified
- bd_853cd6d42e42a889Oregon State AGfiled 2025-01-07(35d gap)Candidate
- bd_c91dd71a3986d50cHHS OCRfiled 2025-01-07(35d gap)Verified
- bd_e7e2fd3d471ae780Maine State AGfiled 2025-01-07(35d gap)Verified
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 11, 2025
- Raw hash
- 4fa5ec1ebc9ed0b74685a54239bff787bc13d239e67fd277f9c22c229009b8bb
Reporting entity
- Name
- Medusind, Inc.norm: medusind
Victim entity
- Name
- Medusind, Inc.norm: medusind
Incident
- Discovered
- Dec 29, 2023
- Materiality determined
- —
- Notification sent
- Jan 7, 2025
- Affected individuals
- 691,192
- Data types
- —
- Attack vector
- Unknown
- Threat actor
- External
Compliance
- Time to disclose
- 14 months(410 days from discovery to filing)
- Compliance flags
- OR AG >45d
- Discovery-date grounding
- occurrence dateThe stored discovery date equals the breach OCCURRENCE date. Detection is normally later, so this OVERSTATES the delay — a 'late' verdict here may not be real.
Extraction provenance
- Status
- No extraction artifact recorded for this disclosure.