People search Cotiviti data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 1 Cotiviti-linked incident, with headline counts up to 65K+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.
Why Cotiviti breach history matters
Cotiviti operates in Technology (India). Across indexed rows, recurring themes include unverified actor or scraping claims. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2020 — Visionary Medical subcontractor insider-style mis-upload; ~63–65k members’ PHI
Cataloged incident. Between mid-October and mid-December 2020, a Visionary Medical Systems subcontractor working on Humana medical-record workflows for analytics vendor Cotiviti copied PHI into a personal Google Drive for impermissible “training,” exposing roughly 63,000–65,000 plan members per HIPAA Journal, TechTarget, and DataBreaches.net summaries of the ensuing class-action settlement (August 2022). The episode is best classified as insider / vendor misuse of authorized access rather than external ransomware. Exposed categories include Humana member PHI categories described in healthcare breach summaries—identifiers plus clinical/claims-adjacent context per notices. BreachHistory cites approximately 65K+ affected records in this row. See the cotiviti2020 and canonical BreachHistory entry.
Patterns and analysis
- Unverified actor or scraping claims — appears across multiple Cotiviti catalog entries; prioritize controls that address this class of failure.
- Record-count hygiene — BreachHistory indexes actor-cited figures separately from company-confirmed totals; read each row's technicalWriteup before treating counts as fact.
- 2026 monitoring — New disclosures roll into this timeline as they are verified or labeled unverified per catalog policy.
What to do if you may be affected
- Step 1: Enable phishing-resistant MFA on every account tied to this brand.
- Step 2: Use unique passwords and a password manager—breach rows often involve credential reuse.
- Step 3: Monitor official company breach notices and regulator filings, not dark-web downloads.
- Step 4: Review OAuth app permissions and revoke unused third-party integrations.
- Step 5: Bookmark the Cotiviti company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/cotiviti · Latest: cotiviti2020.
Sources: BreachHistory catalog (1 row for Cotiviti), company and regulator disclosures cited in individual breach records.