Skip to content
Cloud Security Breaches

iRhythm Holdings, Inc. (2026): what the sources say about the cloud incident

iRhythm Holdings, Inc. disclosed the incident on 15 Jun 2026. What was exposed, as the sources state it: The filing says a threat actor claimed sensitive information including proprietary data, patient protected health information and other personal information, and the company confirmed certain data was exfiltrated; the volume is not public.

Open the ledger · Report a correction

Disclosed
15 Jun 2026
Incident window
identified June 8, 2026, as the filing says
Cloud or provider
not public
What was exposed
The filing says a threat actor claimed sensitive information including proprietary data, patient protected health information and other personal information, and the company confirmed certain data was exfiltrated; the volume is not public.
How access was gained
The filing says the affected data was obtained through social engineering from certain third-party-hosted business applications (the provider is not named).
Access path
Stolen user credentials and session tokens
Kind of control that addresses it
require phishing-resistant multi-factor authentication for every account on hosted business applications and verify help-desk callers through a second channel

In the words of the source

“the affected data was obtained through social engineering and is from certain third-party-hosted business applications.” (regulator filing, iRhythm Form 8-K, Item 1.05, filed 2026-06-15)

Primary sources

If a field is wrong or a newer primary source exists, write to the editor with the entry name in the subject.

Sources

  1. iRhythm Form 8-K, Item 1.05, filed 2026-06-15, read 16 Nov 2026

Last reviewed 16 Nov 2026.