Intersport 2025 Dataset
The March 2025 dataset record attributed to Intersport had been published with a scope value of 2,625,398 and email, name, phone, physical-address, and purchase fields.
Exposed Data Types
5- Alleged email addresses
- Alleged names
- Alleged phone numbers
- Alleged physical addresses
- Alleged purchases
About This Record
Manual review of both locale versions found no company notice, regulator record tied to a specific country operation, reliable independent report, verified breach-index entry, or original dataset listing supporting those claims. The source field said only “Third party breach” and contained no source URL.
Production evidence does not authenticate the claim either. No import job is associated with the record, and no locally linked data was found in the email, name/identity, phone, address, password, username, IP, sensitive-data, or general breach-data collections. The existence of the Intersport brand and working intersport.com domain does not establish a March 2025 incident affecting the global brand or a particular national operator.
Unverified scope
It is unknown whether March 2025 represents an incident, access, discovery, or publication period. No measurement definition shows whether 2,625,398 means customers, people, accounts, orders, rows, or unique email addresses. The email, name, phone, physical-address, and purchase fields also lack a sample, schema, file manifest, or technical report. Because the global brand works through separate retail operations in different countries, the brand name alone cannot establish the event identity or affected system.
Why was the record removed?
Publishing an unsupported physical-address and purchase-history breach would create targeted-fraud concern and attribute an unverified incident to a brand or national operator. The record is therefore retained as unverified and retired and should not appear on public breach pages or in search results. If an original listing, file hashes and sample schema, company notice, regulator record, or reliable independent verification emerges, the country/operator identity, date, count unit, and data fields can be reviewed from the beginning.
Verification and editorial method
LeakData compares the incident name, date, affected-record count, and exposed data types with accessible sources. Unverified fields are not presented as facts, and records are updated when new evidence becomes available.
Report missing or incorrect information
