Substack user data leaked via exploited API flaw
An attack exploiting an API flaw at Substack leaked user email addresses, phone numbers and other information. 662,752 user records were published on a cybercrime forum, and Substack notified users of the breach. The incident was discovered about four months after it occurred.
Key facts
- Affected organisation
- Substack
- Incident type
- Data breach
- Occurred / detected
- Not confirmed
- Scale of damage
- 662,752 user records
- Cause / method
- Exploitation of an API flaw
- Location
- United States
If your data was exposed
Exposed dataEmailPhone number
- 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
- Substack confirmed the leak of email addresses and phone numbers and notified users of the breach.
- It emerged that the data leak via the exploited API flaw had been discovered about four months later.
11 related reports
- Substack reports mass data leak: ‘This sucks. I’m sorry’
- Substack data breach leaks users’ email addresses and phone numbers
- Substack confirms data breach affects users’ email addresses and phone numbers
- Dark Web Profile: 0APT Ransomware
- Substack warns customers of data breach following hacker’s dark web claims
- Substack Discloses Security Incident After Hacker Leaks Data
- Substack data breach exposed users’ emails and phone numbers
- Newsletter platform Substack notifies users of data breach
- Substack Breach: 662,752 User Records Leaked on Cybercrime Forum
- Substack data breach exposes emails and phone numbers
- 서브스택, API 허점 악용 약 70만 사용자 정보 유출... 4개월 만에 발견
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.