← Breach analysis by the Dual Vulnerabilities framework

Williamsport Home data breach (Unattributed, 2023)

2023 · United States · Q - Human health and social work activities · Network intrusion with data theft of resident personal and health information

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Network intrusion with data theft of resident personal and health information

Dual vulnerability type

No DV evidenced

Alternative: none defensible

Why this classification

(1) As a HIPAA-covered continuing-care retirement community, the doctrinal expectation at the victim was the safeguarding of residents' protected health and financial information held in its business systems. (2) In practice, unauthorized actors accessed internal systems used for business operations between 18 and 24 April 2023; the organisation discovered suspicious activity itself on 24 April 2023, reported to HHS under the HIPAA Breach Notification Rule as affecting at least 500 individuals, and disclosed publicly on 23 June 2023 - within the 60-day window - naming a very broad set of potentially taken data categories (names, dates, medical condition, diagnoses, lab results, medications, Social Security numbers, financial account and credit card numbers). (3) No lifecycle stage yields a defensible victim-side mechanism: the entry vector and root cause were never disclosed and the victim's own press release leaves the cause undetermined; the victim states the intrusion touched only a limited number of business systems with no evidence that resident-care software was affected, so no containment failure is documented; detection by the organisation's own side within days of the intrusion period shows no documented detection gap; the disclosure was legally timely, so the notification conduct is not a codeable failure; and no regulator (OCR), state attorney-general, court or forensic follow-up reporting exists that documents any origin-and-break gap. Under the method's decision rule, where the reporting confirms impact only and the primary source states the cause is undetermined, the case is set to Unknown; the entry vector and every later-stage mechanism are not load-bearing because none is evidenced. The possible ransomware component is reporter speculation (DataBreaches.Net inferred it from a homepage notice of ongoing phone and internet interruption) and remains unconfirmed, contradicting the EuRepoC fields that record no system disruption; it is noted, not classified.

Sources

Notes

The victim's registered name is The Williamsport Home, Inc. (a 501(c)(3) continuing-care retirement community at 1900 Ravine Road, Williamsport, PA); the dataset victim string is kept as written. Data quality: the case file's affected_entities '1-10' conflicts with the HHS HIPAA reporting of at least 500 individuals (HIPAA Journal, 3 July 2023). The case file's description matches the stated victim. Williamsport Home and Senior Choice, Inc. (three other PA facilities) issued near-identically worded press releases the same day and share the same inquiry phone number, suggesting a shared incident-response provider or shared administration, but no source confirms the two incidents are related or that either had a ransomware component; the ransomware reading is DataBreaches.Net's own inference from a homepage outage notice and sits against the EuRepoC has_disruption=False field. Searches found no OCR enforcement action, state-AG action, lawsuit or follow-up forensic reporting for this incident, and no attribution; breach-count aggregator pages listing an HHS portal figure were not opened per the research boundaries, so no exact affected count is recorded. Link check: databreaches.net blocks automated access (HTTP 403); the page was opened and read during research. Unattended run: no consent-requiring action was needed; research used only public news pages and the victim's own press release.