DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
HHS OCRSEC 8-KState AGConfirmed28 filings · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 28 filings

HEALTHEQUITY, INC. — March 2024 breach

Clustered 28 filings across 12 jurisdictions · filing window Jul 2, 2024 → May 23, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

28 filings

States

11

Affected · reported

4,300,000

First → last filing

Jul 2, 2024 → May 23, 2025

Merge confidence

100%

incident inc_e3a0e1258bd54c0f · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 28 regulatory filings. The filings describe hacking. Intrusion Mar 9, 2024–Mar 25, 2024, discovered Mar 25, 2024 — the first regulatory filing landed 99 days later; 9 later filings were flagged late. 4,300,000 individuals reported across the linked filings. Data reported: Government ID, PII, PHI, and 4 more. Notifications rolled out on a 325-day schedule across 28 filings beginning Jul 2, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
99days

Discovered → first regulatory filing

Discovery variance
93days

Range of discovered_at dates across filings

Filing span
325days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster.

Regulatory clocksWashington✗ WA AG >90dCalifornia✗ CA 60-day late · 93dVermont✗ VT AG >45 bdayMaine⏱ ME AG >30d · 123dDate basis✓ Clock withheld · confirmation dateSouth Carolina✓ SC CRA notice dueMassachusetts✓ MA credit monitoring dueHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 9, 2024breach begins
Mar 25, 2024discovered · members disagree
notification delay · 99 days
Jul 2, 2024first filing
May 23, 2025most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. JUL 2SEC 8-KSEC 8-K noticefirst filing · no count statedday 0
  2. JUL 26WA AGWA AG notice102,140 WA residents+24d
  3. JUL 26MT AGMT AG notice17,606 MT residents+24d
  4. JUL 26ME AGME AG noticestates nationwide total 4,300,000+24d
  5. JUL 26OR AGOR AG noticestates nationwide total 4,300,000+24d
  6. JUL 26SC AGSC AG notice110,216 SC residents+24d
  7. JUL 26CA AGCA AG noticeno count stated+24d
  8. JUL 26VT AGVT AG noticeno count stated+24d
  9. JUL 27MA AGMA AG notice81,180 MA residents+25d
  10. JUL 29IN AGIN AG noticestates nationwide total 4,300,000+27d
  11. AUG 9HHS OCRHHS OCR noticestates nationwide total 4,300,000+38d
  12. MAR 21CA AGCA AG noticeno count stated+262d
  13. MAR 24NH AGNH AG noticeno count stated+265d
  14. APR 9NH AGNH AG notice2,586 NH residents+281d
  15. APR 9CA AGCA AG noticeno count stated+281d
  16. APR 16NH AGNH AG notice3,229 NH residents+288d
  17. APR 17NH AGNH AG notice105 NH residents+289d
  18. APR 17CA AGCA AG noticeno count stated+289d
  19. MAY 9NH AGNH AG notice1,088 NH residents+311d
  20. MAY 13CA AGCA AG noticeno count stated+315d
  21. MAY 13NH AGNH AG notice638 NH residents+315d
  22. MAY 15CA AGCA AG noticeno count stated+317d
  23. MAY 15NH AGNH AG notice10,500 NH residents+317d
  24. MAY 16CA AGCA AG noticeno count stated+318d
  25. MAY 16NH AGNH AG notice108 NH residents+318d
  26. MAY 19NH AGNH AG notice2 NH residents+321d
  27. MAY 19MA AGMA AG notice61,403 MA residents+321d
  28. MAY 23MA AGMA AG noticemost recent · 253 MA residents+325d
  29. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 9, 2024 – Mar 25, 2024
WA AG
Discovered
Mar 25, 2024WA AG + MT AG + ME AG +4Jun 26, 2024OR AGfilings disagree on discovery
Data types
Employment · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
SEC 8-K + WA AG + ME AG +7
Attack vector
Third-Party / Supply Chain
SEC 8-K

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

4,300,000

Sum of filed state slices

433,979· 10.1% of stated

90% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US4,300,000
SC110,216
WA102,140
IN98,857
MA81,180
MT17,606
ME13,480
NH10,500

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing27 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement1 member

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 9, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

325 days

Cadence

~1 / 12d

vs. multi-state median

54.2× slower

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.