whogothacked

Insulet Corporation data breach record

Is there a breach on record for Insulet Corporation?

Yes. There are four breach incidents on record for Insulet Corporation. The most recent was first reported on May 16, 2025.

The most recent was reported to the HHS Office for Civil Rights.

The most recent incident

How many
841 individuals, per the HHS Office for Civil Rights.
Data listed
Not listed by the sources on record.
Source record
Open the HHS list of HIPAA breach reports at ocrportal.hhs.gov (how to find this record there)
What to do
If you received a notice letter, start with the letter: keep it, use any free monitoring it offers, and check that the letter is real.
Incidents on record
4
Newest incident first on record
Largest single figure
29,000 individuals per the HHS Office for Civil Rights

Jump to the incident first on record May 16, 2025, Jan 5, 2023, Mar 19, 2021 or Oct 17, 2017.

Get a daily email of new incidents

Email alerts

We use your address only for these alerts and to run and test the service (privacy). Want only SEC filings? Sign up on the alerts page.

Sector
Healthcare Provider
State
Massachusetts

Was Insulet Corporation hacked?

The record gives a cause, in the source's own words. For the incident first reported on May 16, 2025, the record from the HHS Office for Civil Rights gives the cause as “Unauthorized Access/Disclosure (location of breached information: Network Server)”. For the incident first reported on January 5, 2023, the record from the HHS Office for Civil Rights gives the cause as “Unauthorized Access/Disclosure (location of breached information: Network Server)”. For the incident first reported on March 19, 2021, the record from the HHS Office for Civil Rights gives the cause as “Hacking/IT Incident (location of breached information: Network Server)”. For the incident first reported on October 17, 2017, the record from the HHS Office for Civil Rights gives the cause as “Unauthorized Access/Disclosure (location of breached information: Network Server)”.

The HHS Office for Civil Rights describes what happened in its own words. That description is quoted with the incident below.

A filing shows who notified the regulator. The filer is sometimes a vendor or a customer of the firm whose systems were affected, so a filing on its own does not establish whose systems were broken into.

The 4 incidents on record

First reported

Official record

1 source record

Insulet Corporation reported a data breach to the US Department of Health and Human Services Office for Civil Rights in a notice filed on May 16, 2025. The HHS filing puts the number of individuals affected at 841. The HHS filing lists the type of breach as "Unauthorized Access/Disclosure (location of breached information: Network Server)".

Figures on record

  • 841individualsper the HHS Office for Civil Rights

This figure counts only the group named beside it.

Cause on record

Unauthorized access.

The record behind this entry

  1. First record

    Listed on the HHS Office for Civil Rights breach portal under the name Insulet Corporation.

    On this record: 841 individuals; cause given as “Unauthorized Access/Disclosure (location of breached information: Network Server)”.

    • Open the HHS list of HIPAA breach reports at ocrportal.hhs.govThe HHS breach portal has no page for each report. On its list, look for “Insulet Corporation” (MA) with the breach submission date 05/16/2025. Look on its Under Investigation tab first; a report that has been resolved is on its Archive tab. Show Advanced Options can search the list by name (CE / BA Name Search) and by submission date.

What to do if this involved you

The sources on record do not list what kind of data was involved, so the notice letter is the place to look. What to do with a notice letter

First on recordper the HHS Office for Civil Rights and the Washington Attorney General

Official record

3 source records

Insulet Corporation reported a data breach to the US Department of Health and Human Services Office for Civil Rights, the Washington Attorney General and the California Attorney General. The first of 3 notices was filed on January 5, 2023 and the latest on January 10, 2023. The filings give December 1, 2022 as the date of the breach. The HHS filing puts the number of individuals affected at 29,000. The Washington filing puts the number of Washington residents affected at 558. These figures count different groups and are not added together. The HHS filing lists the type of breach as "Unauthorized Access/Disclosure (location of breached information: Network Server)". The Washington filing lists the information involved as: medical information.

Breach dated
December 1, 2022
Latest filing
January 10, 2023

Figures on record

  • 29,000individualsper the HHS Office for Civil Rights
  • 558Washington residentsper the Washington Attorney General

Each figure counts a different group, so they are not added together.

Cause on record

Unauthorized access.

Data exposed, as the sources list it

  • medical information

The records behind this entry

  1. First record

    Listed on the HHS Office for Civil Rights breach portal under the name Insulet Corporation.

    On this record: 29,000 individuals; cause given as “Unauthorized Access/Disclosure (location of breached information: Network Server)”.

    In the words of the HHS Office for Civil Rights

    The covered entity (CE), Insulet Corporation, reported that it inadvertently used tracking devices on its computer systems that captured the protected health information (PHI) of 29,000 individuals. The PHI involved included names and IP addresses. The CE notified HHS, affected individuals and the media of the breach. In its mitigation efforts, the CE implemented additional technical safeguards to better protect PHI.

    • Open the HHS list of HIPAA breach reports at ocrportal.hhs.govThe HHS breach portal has no page for each report. On its list, look for “Insulet Corporation” (MA) with the breach submission date 01/05/2023. Reports older than 24 months are on its Archive tab. Show Advanced Options can search the list by name (CE / BA Name Search) and by submission date.
  2. Update

    Breach notice filed with the Washington Attorney General under the name Insulet Corporation.

    On this record: 558 Washington residents; breach dated Dec 1, 2022.

    This record lists this kind of data: medical information.

  3. Update

    Breach notice filed with the California Attorney General under the name Insulet Corporation.

    On this record: breach dated Dec 1, 2022.

What to do if this involved you

  • Review medical and insurance statements

    Check statements from your insurer and providers for care you did not receive, and tell your insurer about anything that is not yours.

These steps follow from the kinds of data the sources list. If you have a notice letter, start with the letter.

First reported

Official record

2 source records

Insulet Corporation reported a data breach to the California Attorney General and the US Department of Health and Human Services Office for Civil Rights. The 2 notices were filed on March 19, 2021. The filings give January 13, 2021 as the date of the breach. The HHS filing puts the number of individuals affected at 9,050. The HHS filing lists the type of breach as "Hacking/IT Incident (location of breached information: Network Server)".

Breach dated
January 13, 2021

Figures on record

  • 9,050individualsper the HHS Office for Civil Rights

This figure counts only the group named beside it.

Cause on record

Listed by HHS as “Hacking/IT Incident”. Happened at a vendor.

The records behind this entry

  1. First record

    Breach notice filed with the California Attorney General under the name Insulet Corporation.

    On this record: breach dated Jan 13, 2021.

  2. Update

    Listed on the HHS Office for Civil Rights breach portal under the name Insulet Corporation.

    On this record: 9,050 individuals; cause given as “Hacking/IT Incident (location of breached information: Network Server)”.

    In the words of the HHS Office for Civil Rights

    The covered entity (CE), Insulet Corporation, reported that its business associate (BA) was the victim of a cyber-attack that affected the electronic protected health information (ePHI) of 9,050 individuals. The ePHI involved included names, addresses, and treatment information. The CE notified HHS, affected individuals, and the media. In its mitigation efforts, the BA retrained its staff on recognizing and responding to fraudulent email communications.

    • Open the HHS list of HIPAA breach reports at ocrportal.hhs.govThe HHS breach portal has no page for each report. On its list, look for “Insulet Corporation” (MA) with the breach submission date 03/19/2021. Reports older than 24 months are on its Archive tab. Show Advanced Options can search the list by name (CE / BA Name Search) and by submission date.

What to do if this involved you

This entry has no itemized list of the kinds of data involved. The description quoted above may name them, and a notice letter, if you received one, is the place to look. What to do with a notice letter

First reported

Official record

1 source record

Insulet Corporation reported a data breach to the US Department of Health and Human Services Office for Civil Rights in a notice filed on October 17, 2017. The HHS filing puts the number of individuals affected at 1,469. The HHS filing lists the type of breach as "Unauthorized Access/Disclosure (location of breached information: Network Server)".

Figures on record

  • 1,469individualsper the HHS Office for Civil Rights

This figure counts only the group named beside it.

Cause on record

Unauthorized access. Happened at a vendor.

The record behind this entry

  1. First record

    Listed on the HHS Office for Civil Rights breach portal under the name Insulet Corporation.

    On this record: 1,469 individuals; cause given as “Unauthorized Access/Disclosure (location of breached information: Network Server)”.

    In the words of the HHS Office for Civil Rights

    On August 18, 2017, a business associate (BA), Brainshark Inc., had a technical error that caused 3,732 email addresses of the covered entity's (CE) customers to be seen by other customers. The CE contacted the BA and the entities worked together to deactivate the training module that caused the error and investigate the incident. Upon notice of the technical error, Brainshark disabled the CE's site and all further access to the presentation that was involved in the breach. The CE provided breach notification to HHS and the affected individuals. OCR obtained assurances that the CE implemented the corrective actions noted above. In addition, the CE terminated its contract with the BA.

    • Open the HHS list of HIPAA breach reports at ocrportal.hhs.govThe HHS breach portal has no page for each report. On its list, look for “Insulet Corporation” (MA) with the breach submission date 10/17/2017. Reports older than 24 months are on its Archive tab. Show Advanced Options can search the list by name (CE / BA Name Search) and by submission date.

What to do if this involved you

This entry has no itemized list of the kinds of data involved. The description quoted above may name them, and a notice letter, if you received one, is the place to look. What to do with a notice letter

If you received a notice letter

  • Keep the letter

    It names the incident and lists which of your details were involved. The letter, not this page, is the authority on what happened to your data.

  • Use any free monitoring it offers

    Many notices include free credit monitoring with an enrollment code and a deadline. Enroll using the instructions printed in the letter, not a link from an email or text.

  • Check that the letter is real

    Compare it with the source records linked on this page. If you are unsure, contact the organization using a phone number or address from its own website, not one printed in a message you were sent.

  • If your identity is misused, report it

    The Federal Trade Commission's IdentityTheft.gov gives you a recovery plan and the forms to send.

    Report identity theft at IdentityTheft.gov

About this record

Official record: A regulator filing or the organization's own disclosure exists.

Being on record here is not a finding that Insulet Corporation did anything wrong or broke any law. This page reports what the source records say, and no more.

Every fact on this page comes from the source records linked above. The steps for people who received a letter are general guidance, not part of the record. How records are verified

Something wrong here? See how to dispute an entry, or write to corrections@whogothacked.com.

The same record for software: /api/v1/orgs/insulet-corporation