Consumer Apps · Fintech/Banking (neobank) · Private litigation + Data breach
Chime
Headline
An IRAN-LINKED hacktivist group calling itself 'Team 313' allegedly breached Chime's servers on April 1, 2026, coinciding with an outage that, per plaintiffs and press reports, locked members out of their own bank…
Not independently verified. Verification status: Unverified - heuristic first draft. Publish state: draft unverified.
An IRAN-LINKED hacktivist group calling itself 'Team 313' allegedly breached Chime's servers on April 1, 2026, coinciding with an outage that, per plaintiffs and press reports, locked members out of their own bank accounts (Downdetector user outage reports topped 24,000 that morning, per GV Wire - a measure of reports, not a verified count of locked-out members) — no balance checks, no transfers, no rent payments for people whose paycheck sits at Chime instead of a traditional bank. Chime publicly maintains no member data was actually compromised and blames only its marketing website; the plaintiffs in three proposed class actions dispute that directly, alleging Social Security numbers and login credentials were exposed and that the group has threatened to publish stolen data. SEPARATELY, and predating this breach: Chime has faced years of customer complaints (and related litigation, scope not verified this pass) alleging it closes customer accounts and freezes funds WITHOUT NOTICE OR EXPLANATION — a company positioning itself as the friendly alternative to traditional banking has generated a persistent pattern of people simply waking up locked out of their own money.
- Severity
- Evidence tierUnassigned
- Claims confirmed
- Last verified2026-08-04
Case status. Private litigation; no sources are on file yet, so no legal tier is assigned.
Primary source. None recorded — Unverified - heuristic first draft.
Terms
Arbitration
Not independently confirmed this pass — standard binding arbitration + class action waiver expected.
Data sharing
ALLEGED APRIL 2026 DATA BREACH (Chime denies any member data was compromised; three proposed class actions pending in N.D. Cal. as of July 2026; later status not verified as of Oct 2026): a class action alleges Chime Financial 'lost control' over customers' highly sensitive financial data during an April 2026 breach that plaintiffs argue could have been prevented with adequate security measures — specific data types exposed and total customer count not independently confirmed this pass; recommend direct follow-up given Chime's status as a neobank handling checking/savings-equivalent accounts for potentially financially vulnerable customers (Chime markets itself partly toward underbanked/lower-income consumers), making a financial-data breach here potentially more consequential per-customer than at a typical retailer.
Fees and billing
Not itemized this pass.
Contacts
Privacy contact. Not recorded.
Legal notice. Not verified this pass. If publicly traded: SEC Form 10-K cover page gives the official corporate address; the Secretary of State business-entity search in the state of incorporation gives the registered agent, which must accept service. If private: the state registered agent is usually the only reliable route.
Mailing address. Not recorded.
Evidence
No claims have been itemized for this row yet.
No sources are on file for this row yet.
Source vault
Link status: Candidate - not yet fetched
| Document | Last fetch | |
|---|---|---|
| Privacy policy chime.com/legal/privacy-policy/ | Not fetched yet | NO (HTML only) |
| Terms of service chime.com/legal/terms-of-service/ | Not fetched yet | NO (HTML only) |
| Website No URL recorded | Not fetched yet | — |
| Primary source No URL recorded Verification: Unverified - heuristic first draft | Not fetched yet | — |
Enforcement
No enforcement actions are linked to this row.
State statute
No HQ state on file, so no state statute applies by headquarters.