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

OneDigital Investment Advisors LLC — August 2025 breach

Clustered 11 filings across 11 jurisdictions · filing window Apr 8, 2026 → Apr 20, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

11

Affected · reported

28,414

First → last filing

Apr 8, 2026 → Apr 20, 2026

Merge confidence

100%

incident inc_2f86a71dba99414d · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe a third-party compromise. Intrusion Aug 12, 2025–Aug 18, 2025, discovered Aug 22, 2025 — the first regulatory filing landed 229 days later (flagged late). 28,414 individuals reported across the linked filings. Data reported: Government ID, Authentication, Credentials, and 3 more. Notifications rolled out on a 12-day schedule across 11 filings beginning Apr 8, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
229days

Discovered → first regulatory filing

Discovery variance
122days

Range of discovered_at dates across filings

Filing span
12days

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 clocksWashington✗ WA AG >90dMaine✗ ME AG >90d · 229dVermont✗ VT AG >45 bdayCalifornia✗ CA 60-day late · 229dTexas✗ TX AG >30dOregon✗ OR AG >45dFull clock table in Litigation Timeline

Sensitive data

authenticationidentity_government

Incident timeline

Aug 12, 2025breach begins
Aug 22, 2025discovered · members disagree
notification delay · 229 days
Apr 8, 2026first filing
Apr 20, 2026most 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 8WA AGWA AG noticefirst filing · 565 WA residentsday 0
  2. APR 8ME AGME AG noticestates nationwide total 28,414day 0
  3. APR 8VT AGVT AG notice35 VT residentsday 0
  4. APR 8NE AGNE AG notice299 NE residentsday 0
  5. APR 8CA AGCA AG noticeno count statedday 0
  6. APR 8NH AGNH AG notice163 NH residentsday 0
  7. APR 8IN AGIN AG noticestates nationwide total 28,414day 0
  8. APR 8MT AGMT AG notice36 MT residentsday 0
  9. APR 8MA AGMA AG noticeno count statedday 0
  10. APR 10TX AGTX AG noticestates nationwide total 28,414+2d
  11. APR 20OR AGOR AG noticemost recent · states nationwide total 535+12d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 12, 2025 – Aug 18, 2025
WA AG
Discovered
Aug 22, 2025WA AG + ME AG + VT AG +5Dec 22, 2025TX AGfilings disagree on discovery
Data types
Authentication · Credentials · Financial account · Identity (basic) · Government ID · PII
WA AG + TX AG + ME AG +6
Attack vector
Third-Party / Supply Chain
WA 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)

28,414

Sum of filed state slices

2,183· 7.7% of stated

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

US28,414
TX916
WA565
NE299
NH163
IN96
ME73
MT36
VT35

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 filing11 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

12 days

Cadence

~1 / 1.2d

vs. multi-state median

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