Pension Benefit Information, LLC — May 2023 breach
Clustered 46 records across 14 jurisdictions: 45 filings and 1 leak-site claim · filing window Jun 26, 2023 → Sep 22, 2023 (dated filings only). View entity profile → Other incidents for this victim →
incident inc_e1feff6bc203429b · merged by human · confidence 100%
Litigation Timing
SupplementalRange of discovered_at dates across filings
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.
Sensitive data
identity_governmentIncident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.
Member cascade — every filing and leak-site claim in this incident
- JAN 1IL AGIL AG noticefiling day not on record · no count statedoperator-confirmed—
- JAN 1IL AGIL AG noticefiling day not on record · no count statedoperator-confirmed—
- JUN 26HI AGHI AG noticefirst filing · 1,802 HI residentsoperator-confirmedday 0
- JUL 10MT AGMT AG notice891 MT residentsoperator-confirmed+14d
- JUL 11MA AGMA AG notice18,181 MA residentsoperator-confirmed+15d
- JUL 11ME AGME AG noticestates nationwide total 371,359operator-confirmed+15d
- JUL 12WA AGWA AG notice18,856 WA residentsoperator-confirmed+16d
- JUL 12OR AGOR AG noticestates nationwide total 371,359operator-confirmed+16d
- JUL 12IN AGIN AG noticestates nationwide total 371,359operator-confirmed+16d
- JUL 14HHS OCRHHS OCR noticestates nationwide total 1,866,694operator-confirmed+18d
- JUL 21MT AGMT AG notice262 MT residentsoperator-confirmed+25d
- JUL 25HI AGHI AG notice2,250 HI residentsoperator-confirmed+29d
- JUL 26Leak sitecl0p postattacker claim · unverifiedoperator-confirmed+30d
- JUL 27OR AGOR AG noticestates nationwide total 2,373,076operator-confirmed+31d
- JUL 28HI AGHI AG notice6,669 HI residentsoperator-confirmed+32d
- JUL 31OR AGOR AG noticestates nationwide total 27,946operator-confirmed+35d
- AUG 2OR AGOR AG noticestates nationwide total 42,922operator-confirmed+37d
- AUG 4ME AGME AG noticestates nationwide total 82,955operator-confirmed+39d
- AUG 4VT AGVT AG noticeno count statedoperator-confirmed+39d
- AUG 4CA AGCA AG noticeno count statedoperator-confirmed+39d
- AUG 4NH AGNH AG notice91 NH residentsoperator-confirmed+39d
- AUG 8HI AGHI AG noticeno count statedoperator-confirmed+43d
- AUG 10VT AGVT AG noticeno count statedoperator-confirmed+45d
- AUG 10IN AGIN AG noticestates nationwide total 9,618operator-confirmed+45d
- AUG 11NH AGNH AG notice5 NH residentsoperator-confirmed+46d
- AUG 16CA AGCA AG noticeno count statedoperator-confirmed+51d
- AUG 16DE AGDE AG noticeno count statedoperator-confirmed+51d
- AUG 16CA AGCA AG noticeno count statedoperator-confirmed+51d
- AUG 16MA AGMA AG notice516 MA residentsoperator-confirmed+51d
- AUG 16ME AGME AG noticestates nationwide total 9,618+51d
- AUG 18VT AGVT AG noticeno count statedoperator-confirmed+53d
- AUG 24VT AGVT AG noticeno count statedoperator-confirmed+59d
- AUG 24ME AGME AG noticestates nationwide total 336,672operator-confirmed+59d
- AUG 24WA AGWA AG notice6,228 WA residentsoperator-confirmed+59d
- AUG 24ME AGME AG noticestates nationwide total 308,072operator-confirmed+59d
- AUG 24MA AGMA AG notice3,008 MA residentsoperator-confirmed+59d
- AUG 24CA AGCA AG noticeno count statedauto-linked+59d
- AUG 24NH AGNH AG notice1,318 NH residentsauto-linked+59d
- AUG 24OR AGOR AG noticestates nationwide total 308,072operator-confirmed+59d
- AUG 24VT AGVT AG noticeno count statedoperator-confirmed+59d
- AUG 24CA AGCA AG noticeno count statedoperator-confirmed+59d
- AUG 25VT AGVT AG noticeno count statedauto-linked+60d
- AUG 25SC AGSC AG notice4,485 SC residentsoperator-confirmed+60d
- SEP 18CA AGCA AG noticeno count statedoperator-confirmed+84d
- SEP 19CA AGCA AG noticeno count statedoperator-confirmed+85d
- SEP 22NH AGNH AG noticemost recent · 80 NH residentsoperator-confirmed+88d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- May 29, 2023 – May 30, 2023 HI AG
- Discovered
- May 31, 2023IL AG + HI AG + MT AG +6Jun 2, 2023ME AG + WA AG + OR AG +1Jun 4, 2023ME AGJun 28, 2023OR AGJul 21, 2023ME AG + OR AGfilings disagree on discovery
- Data types
- Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII HI AG + MT AG + ME AG +8
- Attack vector
- Third-Party / Supply Chain HI 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)
2,373,076
Sum of filed state slices
67,169· 2.8% of stated
97% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.
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
Attacker assertion only. Establishes: claim date, group, alleged victim.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
No SEC filing or victim statement yet.
Merge provenance
- Method
- human
- Confidence
- 1.00 · above the 0.85 auto-merge floor
- Reviewed
- operator-reviewed Oct 29, 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
88 days
Cadence
~1 / 2.1d
vs. multi-state median
14.7× 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.