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

Mercer Advisors Inc. — January 2026 breach

Clustered 10 filings across 10 jurisdictions · filing window Feb 21, 2026 → Apr 17, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

9

Affected · reported

143,104

First → last filing

Feb 21, 2026 → Apr 17, 2026

Merge confidence

100%

incident inc_3f3416f03f074760 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings and 1 unverified claim. Intrusion Jan 1, 2026–Mar 26, 2026, discovered Jan 22, 2026 — the first regulatory filing landed 68 days later. 143,104 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 5 more. Notifications rolled out on a 54-day schedule across 9 filings beginning Feb 21, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
68days

Discovered → first regulatory filing

Discovery variance
62days

Range of discovered_at dates across filings

Leak precedence
37days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
54days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap⏱ Leak >30dFull clock table in Litigation Timeline

Sensitive data

authenticationidentity_government

Incident timeline

Jan 1, 2026breach begins
Jan 22, 2026discovered · members disagree
notification delay · 68 days
Mar 31, 2026first filing
Apr 17, 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. FEB 21Leak siteshinyhunters postfirst filing · attacker claim · unverifiedday 0
  2. MAR 31NE AGNE AG noticeno count stated+38d
  3. MAR 31CA AGCA AG noticeno count stated+38d
  4. MAR 31MT AGMT AG notice514 MT residents+38d
  5. MAR 31IN AGIN AG noticestates nationwide total 143,104+38d
  6. MAR 31MA AGMA AG noticeno count stated+38d
  7. MAR 31VT AGVT AG noticeno count stated+38d
  8. MAR 31WA AGWA AG notice7,470 WA residents+38d
  9. APR 2TX AGTX AG noticestates nationwide total 143,104+40d
  10. APR 17OR AGOR AG noticemost recent · states nationwide total 1+55d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 22, 2026
NE AG
Discovered
Jan 22, 2026NE AG + MT AG + WA AGMar 25, 2026TX AGfilings disagree on discovery
Data types
Authentication · Credentials · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
NE AG + CA AG + MT AG +4
Attack vector
Unauthorized Access
NE 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)

143,104

Sum of filed state slices

24,173· 16.9% of stated

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

US143,104
TX15,486
WA7,470
IN703
MT514

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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing9 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 Aug 14, 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

54 days

Cadence

~1 / 6d

vs. multi-state median

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