Substack confirms data breach affects users' email addresses and phone numbers

Summary

Substack confirmed a data breach in October, affecting user email addresses and phone numbers. Sensitive data like passwords and credit card numbers were unaffected. The company is investigating and has fixed the issue.

Key Takeaways

1. Substack confirmed a data breach in October that compromised user email addresses and phone numbers.
2. The breach did not affect more sensitive data like credit card numbers or passwords.
3. Substack is investigating the breach and has taken steps to fix the vulnerability.

Statement Breakdown

• Claimed Facts: 70% of statements the article presents as facts
• Opinions: 15% of statements classified as editorial or subjective
• Claims: 15% of statements surfaced for additional reader evaluation

Credibility & Bias Reasoning

Credibility assessment: The article reports on a confirmed data breach at Substack, citing an email from the company's CEO. TechCrunch is a reputable source for tech news, and the article acknowledges unanswered questions, indicating balanced reporting. The direct quotes from the CEO enhance credibility.

Bias assessment: Neutral Reporting. The article presents the facts of the data breach without apparent slant or emotional language. It includes direct quotes from Substack's CEO and acknowledges missing information. The reporting focuses on informing the reader about the incident.

Note: This article reports on a confirmed data breach. Exercise caution with unsolicited communications and monitor your accounts for suspicious activity.

Credibility flag: Verified Breach

Claimed Facts (7)

• This is a direct statement of fact confirmed by the company.
• This is a direct quote from Substack describing the breach.
• This is a specific detail provided by Substack about the scope of the breach.
• This is a direct statement from the CEO regarding the timeline of the breach.
• This is a statement of action taken by the company.
• This is a statement about TechCrunch's reporting process.
• This is a statement from the company regarding the misuse of data.

Opinions (2)

• This is an expression of personal feeling.
• This is a subjective assessment of the company's performance.

Claims (3)

• This highlights a lack of transparency, making the claim dubious.
• The delay in detection raises questions about the company's security practices.
• This vague advice is not particularly helpful and could be seen as a way to avoid responsibility.

Key Sources

• Ivan Mehta — Author, TechCrunch
• Chris Best — CEO, Substack
• Substack — Company