People search SoFi data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 2 SoFi-linked incidents, with headline counts up to 38K+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.
Why SoFi breach history matters
SoFi operates in Finance (United States). Across indexed rows, recurring themes include credential theft and social engineering, cloud and database misconfiguration, third-party and supply-chain exposure. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2026 — third-party vendor database unauthorized access
Cataloged incident. SoFi confirmed in June 2026 that its Hong Kong subsidiary detected unauthorized access on April 30, 2026 to a customer information database managed by a third-party vendor. BleepingComputer reported the public disclosure June 8, 2026 alongside ongoing investigation into data categories and scope; SoFi emphasized no account passwords or financial account numbers were in the compromised database per initial statements. Exposed categories include Customer PII categories under investigation; SoFi stated no account passwords or financial account numbers in accessed set per June disclosures. No attested victim count is published for this row yet. See the sofi-hong-kong-vendor 2026 record and canonical BreachHistory entry.
2025 — social engineering breach exposed PII for 38,049 Washington residents
Cataloged incident. SoFi Technologies confirmed a social engineering incident allowing unauthorized access to internal systems from December 29, 2025 through January 3, 2026, discovered January 2, 2026. A Washington Attorney General filing disclosed 38,049 state residents affected with names, dates of birth, addresses, contact details, and employment/education information; SoFi stated account passwords and payment card numbers were not accessed. The company engaged CrowdStrike and notified affected individuals by mail. Exposed categories include Names, DOB, addresses, emails, phones, employment and education info; no passwords or payment card numbers per SoFi. BreachHistory cites approximately 38K+ affected records in this row. See the sofi-social-engineering 2026 record and canonical BreachHistory entry.
Patterns and analysis
- Credential theft and social engineering — appears across multiple SoFi catalog entries; prioritize controls that address this class of failure.
- Cloud and database misconfiguration — appears across multiple SoFi catalog entries; prioritize controls that address this class of failure.
- Third-party and supply-chain exposure — appears across multiple SoFi catalog entries; prioritize controls that address this class of failure.
- Record-count hygiene — BreachHistory indexes actor-cited figures separately from company-confirmed totals; read each row's technicalWriteup before treating counts as fact.
- 2026 monitoring — New disclosures roll into this timeline as they are verified or labeled unverified per catalog policy.
What to do if you may be affected
- Step 1: Enable phishing-resistant MFA on every account tied to this brand.
- Step 2: Use unique passwords and a password manager—breach rows often involve credential reuse.
- Step 3: Monitor official company breach notices and regulator filings, not dark-web downloads.
- Step 4: Bookmark the SoFi company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/sofi · Latest: sofi-hong-kong-vendor2026.
Sources: BreachHistory catalog (2 rows for SoFi), company and regulator disclosures cited in individual breach records.