Skip to content
Breach Index · running record

Vanguard data breach history (2016-2026): the 2026 social-engineering incident, vendor events and claims

Vanguard is one of the largest US fund managers and a big workplace-retirement recordkeeper. This page is the running record of its security incidents since 2016: what Vanguard told regulators and clients, what state filings add, what attackers claim without proof, and what clients should do.

Short answer

Was Vanguard hacked?

Yes. Vanguard’s notice letter, filed with California’s Attorney General, says it “experienced a social engineering incident between July 29-31, 2026”: an imposter deceived an employee and a third party got into “certain files within a limited set of cloud-based applications, like Microsoft 365”. Some files held client personal information. Vanguard says no client accounts were accessed and there is no evidence of access to its recordkeeping system or anything that can move money.

Vanguard has not published a total. Vermont’s list shows 94 Vermont residents and Social Security numbers. Vanguard told the Independent Vanguard Adviser it is notifying “a couple hundred thousand clients”, mostly workplace retirement plan participants. It offers three years of Kroll monitoring. At least one class action, Peppard v. The Vanguard Group, has been filed.

Two forum claims are separate and unproven: about 14 million records (relayed by ThreatMon around 16 October 2026) and 22.5 million records from an actor calling themselves “Solonik” in January 2026. Vanguard has confirmed neither. Earlier, Vanguard reported client accounts accessed with reused passwords in March 2024 (via search) and was caught up in the 2023 Infosys McCamish outage, where its memo said no data exfiltration had been found.

Timeline at a glance

  1. Mar 2024Client accounts accessed with passwords stolen elsewhere, per a Massachusetts letter (via search). (Massachusetts OCABR (via search))Reported
  2. Jan 2026“Solonik” claims 22.5M Vanguard records; separate claim, not confirmed. (Hackmanac (via search))Unverified claim
  3. 29-31 Jul 2026Social-engineering attack gives a third party access to files in cloud apps such as Microsoft 365. (Vanguard letter (CA AG))Confirmed
  4. ~16 Oct 2026Forum listing claims “+14M” investor.vanguard.com records; Vanguard has not confirmed. (ThreatMon on X)Unverified claim
  5. 4 Nov 2026Vermont AG notice: 94 Vermont residents, Social Security numbers. (Vermont AG)Confirmed
  6. 9 Nov 2026Law360 reports Peppard v. The Vanguard Group, a putative class action in Pennsylvania federal court. (Law360)Reported
  7. 11 Nov 2026Vanguard tells the Independent Vanguard Adviser it is notifying “a couple hundred thousand clients”. (Independent Vanguard Adviser)Reported
  8. 11 Nov 2026California AG posts Vanguard’s notice; letter offers three years of Kroll monitoring. (California AG)Confirmed

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.

Vanguard incident timeline, in detail

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

29-31 Jul 2026 (notified Nov 2026)ConfirmedSocial engineering / cloud business applications

Social-engineering attack on Vanguard cloud files exposes client SSNs

What happened. Per Vanguard’s sample letter on file with the California AG, an imposter posing as a legitimate contact deceived an employee into giving access to corporate accounts. The third party reached “certain files within a limited set of cloud-based applications, like Microsoft 365”. Vanguard says there was no malware or ransomware, the activity was contained, and it is working with law enforcement. The Independent Vanguard Adviser reports Vanguard described a “cloud-based business application” and said most people affected are workplace retirement plan participants.

Impact. Vermont: 94 residents, Social Security numbers. Vanguard’s letter says the data varied by person and “may have also included additional details associated with your plan”. Vanguard has not published a total; it told the Independent Vanguard Adviser “a couple hundred thousand clients”. No client accounts were accessed, per Vanguard. Three years of Kroll credit monitoring and $1 million identity fraud reimbursement are offered. Law360 reported a putative class action, Peppard v. The Vanguard Group, on 9 November 2026.

Sources: Vanguard sample notice letter (California AG) · California AG breach entry: Vanguard Group Inc. · Vermont AG security breach notices · Independent Vanguard Adviser, 11 Nov 2026 · Law360: Peppard v. The Vanguard Group

~16 Oct 2026Unverified claimForum sale claim

Forum listing claims 14 million Vanguard records

What happened. The monitoring account ThreatMon relayed an underground forum listing titled “Database [investor.vanguard.com] +14M”. Its samples look like SMS verification-code logs, which points at a messaging or verification provider rather than Vanguard’s own records, though nobody has shown where they came from.

Impact. Not confirmed by Vanguard or verified independently. It has not been linked to the July 2026 incident. Records are not the same as people.

Sources: ThreatMon on X

Feb 2026ReportedRegulator filing (cause not stated)

Vanguard notice filed with Massachusetts (details unclear)

What happened. Aggregators report that Vanguard filed a breach notice with the Massachusetts Office of Consumer Affairs on 11 February 2026 listing Social Security numbers. We could not open the letter, and the aggregator says the filing does not state the cause (via search).

Impact. Number of people and cause not known to us.

Sources: ClaimDepot summary of the Massachusetts filing

Jan 2026Unverified claimForum claim

“Solonik” claims 22.5 million Vanguard records

What happened. An actor calling themselves “Solonik” claimed 22.5 million Vanguard records, according to a Hackmanac post we saw only via search.

Impact. Not confirmed by Vanguard. Nothing links it to the 14M listing or the July 2026 incident.

Sources: PlayCISO news post (timeline)

Mar 2024ReportedAccount takeover (credential reuse)

Client online accounts accessed with passwords stolen elsewhere

What happened. A Vanguard letter on file with Massachusetts (2024-915) says Vanguard detected suspicious activity on some clients’ online accounts in March 2024: an unauthorized party used usernames and passwords that appear to have come from third parties, not from Vanguard, and got past additional verification steps (via search; we could not open the letter).

Impact. Number of clients not known to us. Vanguard said it had no evidence the information was misused.

Sources: Massachusetts OCABR letter 2024-915 (via search)

Nov 2023ReportedVendor incident (Infosys McCamish via Newport)

Infosys McCamish ransomware outage hits Vanguard nonqualified plans

What happened. Vanguard told nonqualified plan sponsors that a cybersecurity event at Infosys McCamish Systems, used by its nonqualified provider Newport, disrupted service. The memo said the investigation “has not revealed evidence that data of your plan or participants was exfiltrated” and that Vanguard saw no unusual activity on its own systems. It was the vendor’s systems.

Impact. Service disruption. PLANADVISER later listed Vanguard among firms “previously reported as being hit” by the 6 million-person Infosys breach; we found no Vanguard notice giving a count.

Sources: PLANADVISER, 16 Nov 2023 · PLANADVISER, 11 Sep 2024

Where the reports disagree

  • Scale: Vanguard told the Independent Vanguard Adviser “a couple hundred thousand clients”; a forum listing claims 14 million records and an earlier claim 22.5 million. Neither claim is confirmed or linked to the July 2026 incident.
  • Wording: Vanguard’s letter speaks of “a limited set of cloud-based applications, like Microsoft 365”; the Independent Vanguard Adviser quotes “a cloud-based business application”. Vanguard has not named a vendor.
  • Lawsuits: Law360 confirms Peppard v. The Vanguard Group. Posts say three suits were filed and that one alleges SSNs were not encrypted; we could not confirm either.

The pattern across the record

People, not exploits

The confirmed 2026 incident started with an employee being deceived, and the 2024 account access used passwords reused from other sites. Both go around technical controls by abusing trust or credentials.

Retirement-plan data sits in many places

Plan participant data moves between Vanguard, plan sponsors, nonqualified-plan providers and vendors such as Infosys McCamish. Each hop is another place it can leak.

Big claims, small confirmations

Forum sellers have twice claimed tens of millions of Vanguard records. What Vanguard has confirmed is far smaller. Treat claims as claims until the firm or a regulator filing says otherwise.

What it means for Vanguard clients — and what to do

If you got a Vanguard letter, your Social Security number is likely in someone else’s hands. Your Vanguard account itself was not accessed, per Vanguard, so the main risks are identity fraud and convincing scam calls.

  1. 1.Build an SSN action plan

    Freeze your credit at Equifax, Experian and TransUnion, get an IRS Identity Protection PIN, and enrol in the three-year Kroll monitoring before its deadline. Our news post explains what is confirmed so far.

    Read our Vanguard news post
  2. 2.Check the letter is real

    Call Vanguard on the number on its own website, not a number in an email or text. Vanguard’s letter lists (844) 301-0144 as its dedicated call centre.

    Decode a breach notice
  3. 3.Use a unique password and stronger sign-in

    The 2024 incident used passwords reused from other sites. Use a unique password, turn on Vanguard security codes and activity alerts, and prefer a security key or passkey where offered.

    Phishing-resistant MFA planner
  4. 4.Expect breach-themed scams

    Callers may cite the breach to sound official. Vanguard will not ask you to move money to a “safe” account or read out a code.

    SSN exposure action plan

CISO takeaways

Sources

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

  1. 1.Vanguard Group Inc. sample notice letter — California AG, 11 Nov 2026
  2. 2.Breach entry: Vanguard Group Inc. — California AG, 11 Nov 2026
  3. 3.Security Breach Notices (Vanguard Group, Inc., 11-4-2026) — Vermont AG, 4 Nov 2026
  4. 4.Weekly brief: beyond the headlines — Independent Vanguard Adviser, 11 Nov 2026
  5. 5.Peppard v. The Vanguard Group — Law360, 9 Nov 2026
  6. 6.Database [investor.vanguard.com] +14M listing — ThreatMon on X, ~16 Oct 2026
  7. 7.Vanguard data breach (Massachusetts filing summary) — ClaimDepot, 13 Feb 2026
  8. 8.Data breach notice 2024-915 (via search) — Massachusetts OCABR, 7 May 2024
  9. 9.Infosys cybersecurity event disrupting recordkeeper, insurance platforms — PLANADVISER, 16 Nov 2023
  10. 10.Infosys breach from 2023 exposed personal data of 6 million people — PLANADVISER, 11 Sep 2024
  11. 11.Vanguard data breach: SSNs exposed, what is confirmed — PlayCISO, 13 Nov 2026

Frequently asked questions

Was Vanguard hacked in 2026?

Yes. Vanguard’s notice letter says a social-engineering attack between 29 and 31 July 2026 let a third party reach files in cloud applications such as Microsoft 365, some holding client personal information. Vanguard says no client accounts were accessed.

How many people were affected by the Vanguard data breach?

Vanguard has not published a total. Vermont’s list shows 94 Vermont residents. Vanguard told the Independent Vanguard Adviser it is notifying “a couple hundred thousand clients”. Forum claims of 14 million and 22.5 million records are not confirmed.

What data was exposed in the Vanguard breach?

Vermont lists Social Security numbers. Vanguard’s letter says the data varied by person and may include other details tied to the client’s retirement plan.

Is there a Vanguard data breach class action or settlement?

There is at least one class action, Peppard v. The Vanguard Group, reported by Law360 on 9 November 2026. No settlement has been announced as of 13 November 2026.

What is Vanguard offering people affected?

Per its letter: three years of free credit monitoring through Kroll, $1 million identity fraud loss reimbursement, fraud consultation and identity restoration, plus a call centre at (844) 301-0144.

Was Vanguard hacked before 2026?

In March 2024 Vanguard reported clients’ online accounts accessed with passwords stolen from other sites (via a Massachusetts letter we saw only in search). In November 2023 its nonqualified plans were disrupted by the Infosys McCamish ransomware attack; Vanguard said it found no evidence of data exfiltration at the time.

Our coverage of Vanguard

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 Vanguard. Facts are attributed to the dated sources above, and anything disputed or unconfirmed is labelled as such. See the full Breach Index.