DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed12 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 12 filings

PlanMember Securities Corporation — February 2022 breach

Clustered 12 filings across 9 jurisdictions · filing window Apr 11, 2022 → Jul 1, 2022. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

12 filings

States

9

Affected · reported

97,205

First → last filing

Apr 11, 2022 → Jul 1, 2022

Merge confidence

100%

incident inc_337a1cc857ff4f3f · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings. Intrusion Feb 17, 2022–Mar 15, 2022, discovered Feb 17, 2022 — the first regulatory filing landed 53 days later (flagged late). 97,205 individuals reported across the linked filings. Data reported: Government ID, Financial account, Identity (basic), and 1 more. Notifications rolled out on a 81-day schedule across 12 filings beginning Apr 11, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
53days

Discovered → first regulatory filing

Discovery variance
26days

Range of discovered_at dates across filings

Filing span
81days

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; no SEC 8-K in this cluster.

Regulatory clocksMaine✗ ME AG >90d · 104dWashington⏱ WA AG >30dOregon✓ OR AG ≤45dMassachusetts✓ MA credit monitoring dueHawaii✓ HI CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 17, 2022breach begins
Feb 17, 2022discovered · members disagree
notification delay · 53 days
Apr 11, 2022first filing
Jul 1, 2022most 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. APR 11NH AGNH AG noticefirst filing · 16 NH residentsday 0
  2. APR 12ME AGME AG noticestates nationwide total 71,116+1d
  3. APR 15WA AGWA AG noticestates nationwide total 96,813+4d
  4. APR 15CA AGCA AG noticeno count stated+4d
  5. APR 15OR AGOR AG noticestates nationwide total 71,116+4d
  6. APR 16MA AGMA AG notice188 MA residents+5d
  7. APR 16ME AGME AG noticestates nationwide total 71,116+5d
  8. JUN 15IN AGIN AG noticestates nationwide total 71,116+65d
  9. JUN 27ME AGME AG noticestates nationwide total 97,205+77d
  10. JUN 29CA AGCA AG noticeno count stated+79d
  11. JUN 30HI AGHI AG notice3,349 HI residents+80d
  12. JUL 1MT AGMT AG noticemost recent · 122 MT residents+81d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 17, 2022
NH AG
Discovered
Feb 17, 2022WA AGMar 15, 2022NH AG + ME AG + CA AG +3filings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
NH AG + ME AG + WA AG +4
Attack vector
Phishing
NH 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)

97,205

Sum of filed state slices

8,190· 8.4% of stated

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

US97,205
WA4,231
HI3,349
MA188
ME149
IN135
MT122
NH16

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 filing12 members

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

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Jun 12, 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

81 days

Cadence

~1 / 7.4d

vs. multi-state median

10.1× 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.