Navia Benefit Solutions, Inc.: 2,151,330 individuals, Mar 2026.

OCR classifies the incident as a hacking or IT incident, with the breached information held in a network server and another location. Hacking/IT Incident is the type recorded on 117 of the 185 Washington filings (63%) and on 86% of all filings submitted in 2026. Network Server appears on 48% of Washington filings.

A business associate is recorded as present on the filing, as it is on 21% of Washington filings. At 2,151,330 individuals the breach is 545 times the Washington median filing of 3,950 and 538 times the national median of 4,000 across all 7,884 filings. It is one of 149 filings on the register of one million or more individuals.

As of 28 August 2026 the case is listed by HHS OCR under Cases Currently Under Investigation. OCR has not published a closing summary, so this page is limited to the fields on the filing itself; the archive entry that follows a closed investigation usually adds a short account of what was exposed and what the entity did afterwards.

Washington's breach notification statute (RCW 19.255.010) requires notice to affected residents no later than 30 days after discovery. Its attorney general threshold: more than 500 Washington residents. The HIPAA Breach Notification Rule ran alongside it: notice to affected individuals and to HHS without unreasonable delay and no later than 60 days after discovery, which is the clock that put this filing on the portal.

Multiplying 2,151,330 individuals by IBM's $160 customer-PII cost per record (Cost of a Data Breach 2025, the figure the site's calculator uses) gives a modelled $344M; the 2026 edition's $192 gives $413M. Both are modelled estimates with the method shown, not costs disclosed by Navia Benefit Solutions, Inc.. Because the filing is above the roughly 100,000-record range in which the per-record figure is reliable, the result is an upper bound, not an estimate: fixed costs are spread across far more records at this scale.