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

ProMedical — January 2026 breach

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

Determination

Confirmed

Members

1 filing

States

1

Affected · reported

1

First → last filing

Jan 29, 2026

incident inc_df5ba446f5b84b88 · merged by deterministic

Confirmed breach. Intrusion Jan 15, 2026, discovered Jan 15, 2026 — the first regulatory filing landed 14 days later. 1 individuals reported across the linked filings.

Litigation Timing

Notification delay
14days

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 clocksMassachusetts✓ MA AG ≤30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 15, 2026breach begins
Jan 15, 2026discovered
notification delay · 14 days
Jan 29, 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 29MA AGMA AG noticeonly filing · 1 MA residentsday 0
  2. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 15, 2026
MA AG
Discovered
Jan 15, 2026
MA AG
Data types
Government ID · Identity (basic) · Financial
MA AG
Response
Contacted the individual who received the erroneous W-2 · Confirmed in writing that the information has been deleted and was not further disseminated · Offering 24 months of credit monitoring services at no cost to you through a provider of your choice
MA AG

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

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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.