TOO LOST LLC
bd_4ad7e3b0d8858b93 · schema v1 · pii pii-v2
Full breach record for TOO LOST LLC →Too Lost LLC notified Nebraska residents of a data breach involving unauthorized access to a web application between July 25, 2025, and September 2, 2025. The company discovered the incident on February 10, 2026, and sent notifications on February 20, 2026. Affected data included names and basic contact information (address, email, phone). No passwords were compromised. Too Lost engaged cybersecurity experts and law enforcement, confirmed data destruction by the attacker, and offered credit monitoring services.
J jump to incidentP pin to compareR raw source
Incident timeline
Jul 25, 2025
Begins
Feb 10, 2026
Discovered
Feb 20, 2026
Filed
Linked disclosures
Why this link?Regulatory filings (9) · sorted by filing gap
- Vermont State AGbd_0879145c47f3fbf52026-02-20Verified
- California State AGbd_2d71718d265351de2026-02-20Candidate
- Indiana State AGbd_32c22f44949121742026-02-20Verified by operator
- New Hampshire State AGbd_373b6de6cb19f9512026-02-20Verified
Show 5 more filings ↓Show fewer ↑up to 34d gap
- Maine State AGbd_54386167de42a9932026-02-20Verified
- Indiana State AGbd_a10965c99e7afc612026-02-20Verified
- Massachusetts State AGbd_b2c600e1387b37c42026-02-20Verified
- Texas State AGbd_8bce7e39abf24b6e2026-03-16 · +24dVerified
- New Hampshire State AGbd_979e794526725f7b2026-03-26 · +34dVerified
Filing propagation · 10 filings · 8 states
View merged incident ↗Pattern: first filing Feb 20 (VT), last Mar 26 (NH) — a 34-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.