Home › Intelligence › Brief
BREACH BRIEF🔴 Critical Breach

Critical Data Breach Exposes 48,145 Records on DC Health Link Platform

LiveThreat™ Intelligence · 📅 October 08, 2026· 📰 haveibeenpwned.com
🔴
Severity
Critical
BR
Type
Breach
🎯
Confidence
HIGH
🏢
Affected
3 sector(s)
✅
Actions
5 recommended
📰
Source
haveibeenpwned.com

Critical Data Breach Exposes 48,145 Records on DC Health Link Platform

What Happened

In March 2023 DC Health Link disclosed that an unauthorized party accessed its systems and extracted 48,145 user records. The stolen data—later posted on a public breach forum—includes full names, dates of birth, Social Security numbers, contact details, ethnicity, gender, employer information, and purchase history.

Why It Matters for Compliance & Audit Readiness

  • Demonstrates the need for continuous control‑assurance that validates data‑handling controls (e.g., encryption at rest, least‑privilege access) before a breach can occur.
  • Highlights the importance of maintaining up‑to‑date vendor risk assessments that capture the full scope of PII processed by third‑party platforms.
  • Reinforces the requirement to document incident‑response testing and evidence collection to satisfy audit trails under frameworks such as NIST CSF, ISO 27001, and HIPAA.

Who Is Affected

  • Healthcare providers and insurers that use DC Health Link for enrollment or benefits administration.
  • Employees and members whose personal and demographic data were stored on the platform.
  • Any downstream partners that receive the exposed data for claims processing or analytics.

Recommended Actions

  • Review your organization’s exposure to DC Health Link and update the vendor risk register.
  • Verify that monitoring controls (e.g., anomalous login detection, data‑loss‑prevention) are actively logging and alerting on suspicious activity.
  • Request a detailed incident‑response disclosure from DC Health Link, including root‑cause analysis and remediation steps.
  • Ensure that all PII at rest is encrypted and that access is limited to a need‑to‑know basis.
  • Document the breach response in your audit evidence repository to demonstrate defensible controls.

Technical Notes

  • Attack vector: Not publicly disclosed; breach surfaced via a data‑breach forum, suggesting possible credential compromise or misconfiguration.
  • CVEs: None reported.
  • Data types exposed: Citizenship status, date of birth, email address, employer, ethnicity, gender, full name, phone number, physical address, purchase history, Social Security number.

Source: https://haveibeenpwned.com/api/v3/breach/DCHealth

📰 Original Source
https://haveibeenpwned.com/api/v3/breach/DCHealth ↗

This LiveThreat Intelligence Brief is an independent analysis. Read the original reporting at the link above.

From the Verisq platform · Vendor Risk Hub

This is the scenario continuous vendor monitoring is built to catch.

When a vendor is compromised, your third-party risk controls are what produce the audit trail showing you knew, assessed, and acted. The Verisq AI Trust Operations platform tracks that continuously.

Explore the Verisq AI Trust Operations platform →