FloatMe
ent_036ec2810af5fb6f3daf8b84
Disclosures
3
State AG · 3 jurisdictions
Incidents
1
filings grouped by incident
Max affected reported
401
nationwide · State AG IN
Leak-site claims
0
none in sample
Identity resolution
- Canonical name
- FloatMe
- Normalized
- floatme— dedupe via name-norm; Microsoft / MSFT collapse to one row
- GLEIF LEI
- No match
- SEC EDGAR CIK
- None — not an SEC registrant
- Domain
- None on record
Disclosure history (3)newest first
- ⛰️New Hampshire State AGas victim2026-01-06
FloatMe, Corp. notified the New Hampshire Attorney General of a credential stuffing incident involving its Auth0 platform. The breach occurred December 8-9, 2025, affecting 2 New Hampshire residents. Exposed data included login credentials, mailing addresses, phone numbers, partial bank/debit card numbers, and recent financial transactions. FloatMe reset passwords, shut down the compromised endpoint, and cancelled fraudulent advances. Notifications were sent to affected individuals on January 6, 2026.
- 🦞Maine State AGas victim2026-01-06
FloatMe, Corp. experienced an external system breach where an unauthorized party gained access to its systems between December 8, 2025, and December 11, 2025. The breach was discovered on December 9, 2025, and affected one Maine resident.
- 🏎️Indiana State AGas victim2026-01-05
FloatMe Corp reported a data breach to the Indiana Attorney General. The breach occurred on 2025-12-08 and was reported on 2026-01-05. 7 Indiana residents were affected. 401 individuals affected in total.