Personal data of 57 million Hot Topic customers leaked
Customer personal information was leaked at Hot Topic, and follow-up checks put the number affected at 57 million. Initial claims said personal and payment information of 350 million people had been exposed. Breach notification service Have I Been Pwned notified 57 million people of the breach.
Key facts
- Affected organisation
- Hot Topic
- Incident type
- Data breach
- Occurred / detected
- Not confirmed
- Scale of damage
- Personal information of 57 million customers
- Cause / method
- Infostealer infection identified as the cause
- Location
- United States
If your data was exposed
- Don’t tap links in texts, calls or emails that mention this incident and offer compensation, refunds or breach checks. Check directly on the organisation’s official website or app.
Timeline
- Claims emerged that personal and payment information of 350 million people had been exposed through an infostealer infection.
- Have I Been Pwned notified 57 million people in connection with the Hot Topic breach.
- The amount of leaked customer personal information was put at 57 million people.
8 related reports
- Largest Retail Breach in History: 350 Million "Hot Topic" Customers’ Personal & Payment Data Exposed — As a Result of Infostealer Infection
- Hacker May Have Breached Hot Topic, Stolen Data on Millions
- HIBP notifies 57 million people of Hot Topic data breach
- Hot Topic breach: Has your credit card info been compromised?
- Have I Been Pwned says 57m affected in Hot Topic data breach
- Major Hot Topic Data Breach Affects 57 Million Customers
- Hot Topic data breach exposed personal data of 57 million customers
- Hot Topic impacted in 'largest retail breach in history,' report says
Other incidents at Hot Topic
Retail chain Hot Topic hit by another cyber-attack
Retail chain Hot Topic was hit by a cyber-attack again. The attack method, the extent of the damage and the response have not been confirmed.
Read on Cybernews ↗
The summary and key facts are written by AI from related reports and may contain errors. Check the original articles and the organisation’s official statements for accurate details.