Have I Been Pwned has added a Too Lost dataset to its breach database: 724,323 unique email addresses belonging to artists, their collaborators and fans. Some records also contain bcrypt password hashes, and a small subset includes partial card data, identity verification information and records of payments made to artists. Have I Been Pwned added the dataset after examining the information attributed to Too Lost. But the break-in behind it is not yet confirmed: Too Lost says its investigation is ongoing, and the company has not said how the data was obtained, whether it has been misused, or how many people need to be notified.
What Have I Been Pwned found
Have I Been Pwned added the Too Lost breach to its database on 20 November 2026. Its record lists the breach date as 2 November 2026. The service identified 724,323 unique email addresses. That figure counts distinct addresses in the dataset, not a verified count of affected individuals, a distinction that matters because the more sensitive categories sit only in some records.
The base data in the records includes names, usernames, dates and places of birth, physical addresses, IP addresses and social media profiles. Some records also contain passwords stored as bcrypt hashes. Bcrypt is a hashing mechanism designed to make recovering the original password computationally difficult, and the listing does not establish that plaintext passwords were disclosed. But a hash can still be cracked when the underlying password is weak or reused, particularly through offline guessing.
A small subset goes further. Some records include partial credit card data, the last four digits and the card type, not full card numbers. That cannot authorize a card transaction on its own, though it can make an impersonation attempt look more credible. Other records include identity verification information: in some cases, passport, driver’s licence or national ID numbers. The listing does not establish that complete scans of those documents were disclosed, or that every address in the dataset came with identity credentials. Records of payments made to artists also appear in the material. The public entry does not establish that bank account credentials were exposed or that royalties were diverted.
What the company has, and has not, said
Too Lost has told Have I Been Pwned that its investigation remains ongoing, that external forensic specialists have been engaged, and that measures have been taken to secure affected systems and credentials. The company is also working with advisors to coordinate communications and support for affected individuals.
What it has not done is explain the incident itself. The company has not publicly established how the information was obtained, whether it has been misused, or how many individuals require notification. It has not named an attacker, described an entry method, or said whether the data was copied directly from its production systems. The dataset arrived with a claim: an unauthorised party said it had obtained data from Too Lost, and the company has confirmed only that the claim exists and that an investigation is under way.
That distinction is the whole story. Have I Been Pwned’s decision to list the data shows the material is associated with a reported security incident. It does not establish how the data was obtained or who is responsible.
The second incident in under two years
This is not Too Lost’s first public security incident. The company previously disclosed unauthorised access to information in one of its web applications: an investigation found evidence of unauthorised access and data transfer between 25 July and 2 September 2025, and on 10 February 2026 the company determined that personal information could have been affected. Notifications went to US state authorities, including the California attorney general, on 20 February 2026. The state filings give different totals: Texas lists 27,695 people affected and Indiana lists 3,206, and the sources do not explain the difference. Texas’s filing also lists Social Security numbers among the data exposed. In that earlier incident, Too Lost said passwords to Too Lost accounts had not been affected. It contacted law enforcement, added security measures and offered identity protection services.
The new dataset differs on the point that mattered most in the earlier disclosure. This time, bcrypt password hashes appear in some records. The earlier assurance about passwords cannot be applied to the new dataset, but the difference does not establish that the two incidents involved different attackers, a recurring vulnerability, or the same systems. No public forensic analysis has shown whether the datasets overlap or are connected.
| Earlier incident (2025 access, disclosed Feb 2026) | New dataset (Nov 2026) | |
|---|---|---|
| Scale | State filings differ: Texas 27,695, Indiana 3,206 | 724,323 unique email addresses |
| Passwords | Company said account passwords NOT affected | Bcrypt password hashes in some records |
| Identity documents | Categories varied by recipient; not the headline | Passport / driver’s licence / national ID numbers in some records |
| Payment data | Not the headline | Partial card data (last 4 + type) + artist payout records in some records |
| Company status | Notification sent, identity protection offered, law enforcement contacted | Investigation ongoing, forensic specialists engaged, no notification count yet |
The earlier disclosure also became the subject of three proposed class-action complaints filed in federal court in March 2026, later consolidated on 16 April 2026 into a single action, Guralnick v. Too Lost LLC, in the Southern District of New York. The plaintiffs accused Too Lost of failing to protect sensitive information and challenged the adequacy of its response. Those are allegations only: the complaints do not establish that Too Lost violated the law, no court has determined liability, and the lawsuit predates the November 2026 dataset, so its allegations concern the earlier incident only.
What should I do if I use Too Lost?
If you have a Too Lost account, change your password now and turn on multi-factor authentication if it is available. Check your email at haveibeenpwned.com to see whether it appears in the dataset. Watch for messages about payouts or royalties. A fraudster who knows your distribution history can make a fake request look convincing.
- Change your Too Lost password. Pick a new one you use nowhere else, in case your record held a hash.
- Turn on multi-factor authentication. It adds a second check if someone gets hold of your password.
- Check your email at haveibeenpwned.com. It will tell you whether your address appears in the Too Lost dataset.
- Treat payout messages with suspicion. Verify any request to change payment details directly with Too Lost first.
- Consider a credit freeze if identity documents were involved. A freeze is a bigger step than a new password.
- Watch for phishing that uses your artist details. A message that knows your releases or collaborators deserves a second look.
For most people in this dataset, a new password and multi-factor authentication are the proportionate steps. And do not wait for a letter from Too Lost: the company has not said who will be notified or when, so checking haveibeenpwned.com is the faster way to know whether your address is in the dataset.
What is still unknown
How the data was obtained, and whether it was copied directly from Too Lost’s production environment. Whether the records came from the same systems as the 2025 incident or a different source. Whether any of the data has been misused: no publicly verified case of misuse has been connected to this dataset. How many individuals require notification, and when the company will contact them. And whether the unauthorised party that claimed the data is the same party behind the earlier incident, or someone else entirely.
What to watch next
Whether Too Lost names an entry method or an attacker, and whether the investigation confirms an intrusion at all. Whether any evidence of misuse surfaces, particularly phishing that targets artists with payout or royalty messages. Whether the company publishes a notification count or contacts affected users directly. Whether the earlier class action advances, and whether it stays confined to the 2025 incident. This article will be updated as Too Lost or Have I Been Pwned confirm more about the breach.


