Skip to content
Breach Index · running record

State Street data breach history (2016-2026): the Fiserv MOVEit check-image exposure and misdirected-data notices

State Street is one of the largest custody banks, holding assets and paying benefits for pension funds and other institutions. This page records the incidents since 2016 that exposed data it handles, what is confirmed, and what clients and their members should do.

Short answer

Was State Street hacked?

We found no confirmed breach of State Street’s own systems from 2016 to 2026 in the sources we read. The main incident was at a vendor: Fiserv, which clears and processes physical checks for State Street, told State Street on 16 October 2023 that check information had been exposed through its MOVEit file-transfer application, breached in the May 2023 MOVEit campaign.

The exposure reached State Street’s institutional clients’ payees. The Los Angeles County Employees Retirement Association (LACERA), a State Street custody client, said about 2,400 retirees and beneficiaries paid by check were affected, plus about 200 other payees. State Street also filed notices in Massachusetts about documents or files sent to the wrong recipient in 2023 and 2025 (via search).

Timeline at a glance

  1. Apr 2023Client application emailed to the wrong client after two documents were scanned together (via search). (Massachusetts OCABR (via search))Reported
  2. 16 Oct 2023Fiserv tells State Street check information was exposed through its MOVEit app. (LACERA)Confirmed
  3. 27 Oct 2023State Street tells LACERA; member details follow in December 2023. (LACERA)Confirmed
  4. 5 Jan 2024LACERA: about 2,400 retirees and 200 other payees affected. (LACERA)Confirmed
  5. Feb 2024State Street files its own Massachusetts notice about the check images (via search). (Massachusetts OCABR (via search))Reported
  6. 2025Data file with names, addresses and bank account details sent in error (via search). (Massachusetts OCABR (via search))Reported

Last updated November 13, 2026. Every entry is dated and linked to its source; claims by attackers are labelled as claims, never stated as fact.

State Street incident timeline, in detail

Confirmed = acknowledged by State Street, a regulator filing or a court. Reported = credible reporting State Street has not fully confirmed. Unverified claim = an attacker or leak-site claim.

2025ReportedMisdirected data (error)

Data file sent in error

What happened. A 2025 State Street notice on file with Massachusetts says a data file was sent in error (via search; we could not open it).

Impact. Names, addresses and bank account information, per the search snippet. Number of people not known to us.

Sources: Massachusetts notice 2025-1438 (via search)

May 2023 (State Street told 16 Oct 2023)ConfirmedVendor breach (Fiserv / MOVEit Transfer)

Fiserv MOVEit breach exposes check images State Street processed

What happened. Per LACERA, “Fiserv notified State Street on October 16, 2023, that it had identified check information exposures through its transfer application, MOVEit.” Fiserv provides State Street’s physical check deposit clearing and processing. State Street investigated which clients were affected, told LACERA on 27 October and gave member details in December 2023. LACERA said its own systems were not compromised. It was the vendor’s systems.

Impact. LACERA: about 2,400 retirees, survivors, beneficiaries and legal-split payees paid by check, plus about 200 other payees; two years of Kroll monitoring. State Street’s own notice (via search) says check images may show payee name, address, phone and sometimes bank account and routing numbers, and in limited cases handwritten driver’s licence numbers, dates of birth or SSNs. Total across all State Street clients not published.

Sources: LACERA press release, 5 Jan 2024 · State Street Massachusetts notice 2024-225 (via search)

Apr 2023ReportedMisdirected data (error)

Client application emailed to another client

What happened. A State Street notice says an employee scanned two documents meant for separate clients together and the application was emailed to another client (via search; we could not open the letter).

Impact. Number of people and data types not known to us.

Sources: Massachusetts notice 29401 (via search)

The pattern across the record

Exposure comes from vendors and mistakes

The one sizeable incident was at Fiserv, a check processor. The others were documents or files sent to the wrong recipient. None involved an intruder in State Street’s own network, per the sources we read.

Custody banks pass breaches down a long chain

Fiserv told State Street, State Street told its pension-fund clients, and they told their retirees, about three months after Fiserv’s notice. Each hop adds delay.

Older history

In 2008 State Street disclosed that a vendor-held hard drive with data on about 45,000 people from its Investors Financial Services acquisition had been stolen in 2007 (via search). It is before this page’s window.

What it means for State Street institutional clients and their members — and what to do

Most people affected by State Street incidents are not its direct clients: they are pension members or payees of funds State Street serves. If you got a letter from your pension fund naming State Street or Fiserv, your check details may have been exposed.

  1. 1.Switch to direct deposit if you can

    LACERA noted that members paid by direct deposit were not affected. Check images carry account and routing numbers.

  2. 2.Watch the bank account on your checks

    Ask your bank about check fraud alerts or a new account number if routing and account numbers were exposed.

  3. 3.If your SSN was on a check, act on it

    Freeze your credit and get an IRS IP PIN.

    SSN exposure action plan
  4. 4.For pension funds: ask about fourth parties

    Ask your custodian which subcontractors handle member data and how fast they must tell you about a breach.

    Vendor Risk Scorecard

CISO takeaways

Sources

Company statements and regulator filings first, then reputable reporting. Reviewed November 13, 2026.

  1. 1.LACERA protecting members in wake of third-party data breach — LACERA (press release), 5 Jan 2024
  2. 2.State Street notice 2024-225 (via search) — Massachusetts OCABR, Feb 2024
  3. 3.State Street Corporation notice 29401 (via search) — Massachusetts OCABR, 2023
  4. 4.State Street notice 2025-1438 (via search) — Massachusetts OCABR, 2025

Frequently asked questions

Was State Street hacked?

We found no confirmed breach of State Street’s own systems from 2016 to 2026. Its check-processing vendor Fiserv exposed check images through the 2023 MOVEit breach, which affected payees of State Street clients such as LACERA.

What was the State Street Fiserv MOVEit breach?

Fiserv, which clears and processes physical checks for State Street, told State Street on 16 October 2023 that check information was exposed through its MOVEit application. State Street then notified affected institutional clients.

What data was exposed in the State Street breach?

Check images, which can show payee name, address, phone and bank account and routing numbers, and in limited cases handwritten SSNs, dates of birth or driver’s licence numbers, per State Street’s notice (seen via search).

How many people were affected by the State Street data breach?

State Street has not published a total. LACERA alone reported about 2,400 retirees and beneficiaries plus about 200 other payees.

Same sourced, verification-tagged timeline, company by company — compare how peers have fared.

Or see the full Breach Index and how to read it.

Independent analysis for security-leadership education; not affiliated with or endorsed by State Street. Facts are attributed to the dated sources above, and anything disputed or unconfirmed is labelled as such. See the full Breach Index.