HackingHealthcareHealthcareData ExfiltratedCustomer Data InvolvedDelayed DiscoveryPHIIdentity (basic)LowContained

Richmond University Medical Center

bd_5abb4c743a98f6a6 · schema v1 · pii pii-v1

Severity

Low

Discovered

—

Filed

Dec 20, 2024

To disclose

—

Affected

Not disclosed

Linked

5 filings

Confidence

65%

Full breach record for Richmond University Medical Center →

Richmond University Medical Center notified consumers of unauthorized access to its network on or around May 6, 2023. An investigation involving outside cybersecurity professionals determined that certain files containing personal information (full name and potentially other data) were accessed or removed. The electronic health records system was not affected. The organization contained the threat, conducted a manual review of files, and is offering complimentary credit monitoring to affected individuals.

J jump to incidentP pin to compareR raw source

Incident timeline

May 6, 2023

Begins

Dec 20, 2024

Filed

This filing is one of 5 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (4) · sorted by filing gap

Massachusetts State AGbd_d8e141705d6904092024-12-20Verified
Maine State AGbd_2c4f5951d760bb672024-12-19 · +1dVerified
HHS OCRbd_cf416c801d7621b72024-12-19 · +1dVerified
New Hampshire State AGbd_7ca405a4a12fed012024-12-26 · +6dVerified

Name: Richmond University Medical Center
norm: richmond university medical center

Name: Richmond University Medical Center
norm: richmond university medical center
Industry: Healthcarellm

Discovered: —
Breach occurred: May 6, 2023
Materiality determined: —
Notification sent: Dec 1, 2024
Affected individuals: Not disclosed
Data types: PHIIdentity (basic)
Attack vector: Unknown
MITRE ATT&CK: T1078 Valid Accounts
Threat actor: External

During the incident: Contained and secured the threat
Commenced a prompt and thorough investigation
Consulted with outside cybersecurity professionals
Posted notice of the incident on our website
Undertook a manual review process of files to determine whether they contained sensitive personal information
Offering a complimentary membership of Experian IdentityWorks Credit 3B
Changes made: Continually evaluate and modify our practices and internal controls to enhance the security and privacy of your personal information
Source: Quoted from the filing itself, not independently verified.

Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 5 filings · 5 states

View merged incident ↗

Maine State AGDec 19 · first

HHS OCRDec 19 · first

Massachusetts State AG+1d

Vermont State AG+1d · this page

New Hampshire State AG+7d

Pattern: first filing Dec 19 (ME), last Dec 26 (NH) — a 7-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://ago.vermont.gov/document/2024-12-20-richmond-university-medical-center-data-breach-notice-consumers
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Dec 20, 2024
Raw hash: 8ac86a6d736a3cfb7f1963e7dfd8c8e2d9a83b12c951c074810d976b7d04fc0f

Linked disclosures

Regulatory filings (4) · sorted by filing gap

Reporting entityRichmond University Medical Center

Victim entityRichmond University Medical Center

IncidentUnknown

Stated responseContained and secured the threat

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceago.vermont.gov