Conception Reproductive Associates Colorado
bd_34a5c71200e3f836 · schema v1 · pii pii-v1
Full breach record for Conception Reproductive Associates Colorado →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group INC Ransom on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
For over 20 years, Conceptions Reproductive Associates of Colorado has been a pillar of success and hope for patients across Colorado and around the world with clinical outcomes that meet or exceed US benchmarks. We have a huge amount of data from this company in our hands. Medical records, patient images, customer personal data, medical records, email correspondence, photos, and more. In the event that we do not come to an agreement, all data will be published.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Apr 22, 2024
Claim posted
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (1) · sorted by filing gap
- HHS OCRbd_42417872762a5d7a2024-11-25 · +216dVerified
Filing propagation · 2 filings
View merged incident ↗Pattern: first filing Apr 22, last Nov 25 (CO) — a 216-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.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.