DisclosureLens
Leak SiteState AGConfirmed5 records · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedinc_ransomhigh sensitivity
Merged incident · 5 records

Parker Lipman LLP — February 2026 breach

Clustered 5 records across 4 jurisdictions: 4 filings and 1 leak-site claim · filing window May 20, 2026 → May 26, 2026 (dated filings only). View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

5 records

States

4

Affected · reported

1,120

First → last dated filing

May 20, 2026 → May 26, 2026

Merge confidence

100%

incident inc_f307ef148e8a4fc9 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Feb 10, 2026–Mar 2, 2026, discovered Feb 5, 2026. 1,120 individuals reported across the linked filings. Data reported: Government ID, PII, Financial account, and 2 more. Notifications rolled out on a 6-day schedule across 3 dated filings beginning May 20, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Discovery variance
28days

Range of discovered_at dates across filings

Filing span
6days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksMaine⏱ ME AG >30d · 104dLeak gap⏱ Leak >30dFull clock table in Litigation Timeline

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.

Parker Lipman LLP data breach (2026) — filings in 4 jurisdictions, March 2026 · DisclosureLens