DisclosureLens
Leak SiteState AGConfirmed16 filings · 14 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedshinyhuntershigh sensitivity
Merged incident · 16 filings

AMERIPRISE FINANCIAL, INC. — March 2026 breach

Clustered 16 filings across 15 jurisdictions · filing window Mar 22, 2026 Jul 29, 2026. View entity profile → Other incidents for this victim →

1 cross-filing discrepancyMerge100%

Determination

Confirmed

Members

16 filings

States

14

Affected · reported

47,876

First → last filing

Mar 22, 2026 Jul 29, 2026

Merge confidence

100%

incident inc_ff1e36c3a38446c0 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 15 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Mar 2, 2026–Mar 18, 2026, discovered Mar 18, 2026 — the first regulatory filing landed 14 days later. 47,876 individuals reported across the linked filings. Data reported: Government ID, Financial account, PII, and 2 more. Notifications rolled out on a 128-day schedule across 15 filings beginning Mar 22, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
14days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
9days 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
128days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delayno SEC 8-K in this cluster.

Regulatory clocksLeak gap Leak >30dMassachusetts MA AG ≤30dMaine ME AG ≤30d · 30dRhode Island RI AG ≤45dWashington WA AG ≤30dOregon OR AG ≤45dSouth Carolina SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 2, 2026breach begins
Mar 18, 2026discovered
notification delay · 14 days
Apr 1, 2026first filing
Jul 29, 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. MAR 22Leak siteshinyhunters postfirst filing · attacker claim · unverifiedday 0
  2. APR 1IL AGIL AG noticeno count stated+9d
  3. APR 17MA AGMA AG notice1,880 MA residents+25d
  4. APR 17NH AGNH AG notice433 NH residents+25d
  5. APR 17ME AGME AG noticestates nationwide total 47,876+25d
  6. APR 17IA AGIA AG notice583 IA residents+25d
  7. APR 17IN AGIN AG noticestates nationwide total 47,876+25d
  8. APR 17RI AGRI AG notice256 RI residents+25d
  9. APR 17NE AGNE AG noticeno count stated+25d
  10. APR 17WA AGWA AG notice1,359 WA residents+25d
  11. APR 17VT AGVT AG notice83 VT residents+25d
  12. APR 17CA AGCA AG noticeno count stated+25d
  13. APR 17OR AGOR AG noticestates nationwide total 47,876+25d
  14. APR 20SC AGSC AG notice2,684 SC residents+28d
  15. APR 22TX AGTX AG noticestates nationwide total 47,876+30d
  16. JUL 29NH AGNH AG noticemost recent · states nationwide total 552+128d
  17. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 2, 2026
ME AG
Discovered
Mar 18, 2026· 16d undetected
IL AG + MA AG + NH AG +9
Data types
Financial account · Identity (basic) · Government ID · PCI · PII
IL AG + MA AG + NH AG +9
Attack vector
Unauthorized Access
MA 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)

47,876

Sum of filed state slices

10,595· 22.1% of stated

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

US47,876
SC2,684
TX2,390
MA1,880
WA1,359
IN592
IA583
NH433
ME335
RI256
VT83

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 filing15 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 9, 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

128 days

Cadence

~1 / 8.5d

vs. multi-state median

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