DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed1 filing · 1 stateLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlow sensitivity
Incident · single filing

Harvard Pilgrim Health Care — October 2024 breach

One linked filing — more sources may join as they report · filed Jan 14, 2026. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

1 filing

States

1

Affected · reported

505

First → last filing

Jan 14, 2026

incident inc_a1936c5d526a402d · merged by deterministic

Confirmed breach. The filing describes unauthorized access. Intrusion Oct 21, 2024–Jan 13, 2025, discovered Jan 13, 2025 — the first regulatory filing landed 366 days later (flagged late). 505 individuals reported across the linked filings. Data reported: Identity (basic) and PII.

Litigation Timing

Notification delay
366days

Discovered → first regulatory filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksMaine✗ ME AG >90d · 366dFull clock table in Litigation Timeline

Incident timeline

Oct 21, 2024breach begins
Jan 13, 2025discovered
notification delay · 366 days
Jan 14, 2026first & only filing
—watching for filings

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

Member cascade — every filing about this breach

  1. JAN 14ME AGME AG noticeonly filing · states nationwide total 505day 0
  2. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 21, 2024 – Jan 13, 2025
ME AG
Discovered
Jan 13, 2025· 84d undetected
ME AG
Data types
Identity (basic) · PII
ME AG
Attack vector
Unauthorized Access
ME AG

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)

505

Sum of filed state slices

4· 0.8% of stated

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

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 filing1 member

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

SEC 8-K / victim statement

No SEC filing or victim statement yet.

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.