HIPAA Breaches in 2025: HHS Portal Data Analysis

Tyler Carbone
Published ·2 min read

Agency’s analysis of the HHS breach portal snapshot identifies 807 reports submitted during the latest complete calendar year that meet the portal’s large-breach threshold. This is a count of reports, not unique people or incidents across the entire health sector. Submission dates, entity classifications, and later corrections limit how the findings should be interpreted.

Key Takeaways

  • •The combined exports contain 807 qualifying reports after the documented deduplication.
  • •Hacking/IT Incident is the largest reported breach category in this snapshot.
  • •Entity-type counts and breach-type counts describe the same reports.
  • •Counts do not identify unique people or independent attack campaigns.

For implementation support, review HIPAA compliance support and business associate agreement definition. Confirm scope and operating responsibilities before choosing an engagement.

What population does this analysis measure?

It measures reports submitted in 2025 in the active and archive exports from the HHS breach portal, retrieved on the snapshot date. Both exports are needed because resolved investigations move to the archive. The results are Agency’s calculations from government data, not a separate HHS publication.

Which breach types appear in the export?

Hacking/IT Incident is the largest category in this snapshot. Counts by reported type appear in the chart, accessible table, and downloadable CSV below. Entity type is a separate dimension and should not be added to breach-type counts.

These are report classifications, rather than forensic judgments by Agency. A submission can change as the reporting entity or OCR updates the record.

What does the entity breakdown mean for health-tech vendors?

Business-associate reports are one category, alongside providers, health plans, and clearinghouses. A supplier incident can also affect multiple customer reports, so the number of portal records is not the number of independent attack campaigns.

The Security Rule summary explains the safeguard framework. Use the data to prompt questions about information flows, supplier responsibilities, access, and incident coordination. It does not rank vendors or establish the return on buying a product.

How can readers reproduce and reuse the result?

Download the aggregate CSV and review the methodology below. It explains the period filter, threshold, deduplication, and exclusions. The repository records hashes of the original exports and includes the aggregation script.

For operational planning, review HIPAA services and HIPAA for startups. A government dataset supplies context; the actual controls and responsibilities must follow your information and obligations.

Dataset findings

HHS HIPAA breach reports submitted in 2025Type: Hacking/IT Incident652Type: Unauthorized Access/Disc…143Type: Theft9Type: Loss2Type: Improper Disposal1Entity: Healthcare Provider608Entity: Business Associate138Entity: Health Plan59Entity: Healthcare Clearing Ho…2
Agency analysis of official HHS active and archive exports, grouped by reported breach type and covered entity type.
HHS HIPAA breach reports submitted in 2025: aggregate counts
CategoryCount
Type: Hacking/IT Incident652
Type: Unauthorized Access/Disclosure143
Type: Theft9
Type: Loss2
Type: Improper Disposal1
Entity: Healthcare Provider608
Entity: Business Associate138
Entity: Health Plan59
Entity: Healthcare Clearing House2
Download aggregate figures as CSV

Methodology

Data source
HHS OCR Breach Portal; active and archived HIPAA reports downloaded November 1, 2026.
Sample size
n = 807
Period
2025-01-01/2025-12-31
Inclusion criteria
Reports with Breach Submission Date in the stated calendar year and at least 500 individuals affected, from both portal views.
Exclusion criteria
Other submission years, reports below the threshold, Part 2 reports, and 2 exact duplicate row signatures are excluded.
Calculation
Count each retained report once. Deduplicate on entity name, state, entity type, individuals affected, submission date, breach type, and information location. Group separately by breach type and entity type; no percentages or unique-person estimates are calculated.
Limitations
Submission year differs from incident year. Overlapping reports can describe related events and people. Exact row deduplication may combine indistinguishable submissions. The portal can be corrected after retrieval. This snapshot is not a prevalence census.

Frequently Asked Questions

Is this an official HHS annual total?
It is Agency’s reproducible analysis of an HHS portal snapshot. The period is based on submission dates, and later portal corrections may change the result.
Does adding affected individuals count unique people?
No. An individual may appear in multiple reports. This analysis uses report counts and does not claim a deduplicated count of people.
Why include both active and archive exports?
Investigations can move between views. Combining both and applying the stated deduplication reduces the risk of excluding resolved reports or counting an overlapping record twice.
Tyler Carbone

Tyler Carbone

Managing Director and Cofounder

Tyler Carbone is a Managing Director and Cofounder of Agency and one of the industry's leading voices on governance, risk, and compliance. He holds degrees from Harvard and a JD/MBA from the University of Virginia, and previously worked in cybersecurity at Deloitte. Tyler has helped hundreds of companies operate SOC 2, ISO 27001, HIPAA, and GDPR programs.

LinkedIn

Related Reading

Stay ahead of compliance

Expert insights on cybersecurity compliance delivered to your inbox.

We respect your privacy. Unsubscribe anytime.