All Breaches
September 1, 2025 Verified Sensitive Record Healthcare

St. John’s Riverside Hospital 2025 Data Breach

The 2025 St. John’s Riverside Hospital data breach affected 2,238 people after unauthorized access to a limited number of employee email accounts.

2.2 Thousand
Affected People
12
Data Types
Low
Severity
Oct 9, 2026
Last updated

Protect Yourself

Check whether you were affected by this breach

Check my email

Exposed Data Types

6 sensitive12
  • Health insurance information
  • Medical information
  • Provider names
  • Medical record numbers
  • Diagnoses
  • Treatment information
  • Names
  • Dates of birth
  • Social security numbers
  • Driver's license numbers
  • Government issued IDs
  • Financial account information

About This Breach

St. John’s Riverside Hospital provides hospital and community health services in New York's Westchester region.

How Did the Incident Occur?

In September 2025, the hospital became aware that certain employee email accounts may have been accessed to distribute phishing messages and reroute payment funds. The notice did not disclose an exact incident date.

What Information Was Affected?

The information varied by person and may have included names, dates of birth, Social Security numbers, driver's-license or state-identification numbers, financial-account numbers, health-insurance information, medical conditions, treatment-provider names, medical-record numbers, treatment costs, diagnoses, and treatment information.

How Did the Hospital Respond?

St. John’s Riverside Hospital said it changed affected passwords, revoked active sessions, reset multifactor authentication, and investigated with security professionals. It reported no indication of misuse for identity theft or fraud as of the notice.

What Should Affected People Do?

Notice recipients should review credit reports, financial-account activity, health-insurance explanations of benefits, and medical records for activity they do not recognize. Payment-redirection or personal-information requests should be verified through official contact channels.

Verification and editorial method

LeakData compares the incident name, date, affected-record count, and exposed data types with accessible sources. Unverified fields are not presented as facts, and records are updated when new evidence becomes available.

Report missing or incorrect information