Substack disclosed a security incident in early February 2026 involving unauthorized access to user data. The company identified the issue on February 3, 2026, and determined that the unauthorized access had occurred earlier, in October 2025. The breach affected a significant portion of its user base.
The exposed data includes:
Not accessed:
The presence of internal backend fields (e.g., admin flags, captcha status, session indicators) suggests the data was obtained through internal system access or data exports, not simple public web scraping. The dataset includes both readers and active publishers, including monetized creator accounts.
Substack stated that:
The CEO issued a direct apology, acknowledging the failure and committing to preventing similar incidents in the future.
While no confirmed abuse has been detected, the exposed dataset significantly increases the risk of:
Attackers may use accurate account metadata to craft highly convincing emails or SMS messages.
Impacted users are advised to:
Enjoyed reading this Threat Intelligence Advisory? Stay updated with our latest exclusive content by following us on Twitter and LinkedIn
No related posts found.
This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
This website uses Google Analytics to collect anonymous information such as the number of visitors to the site, and the most popular pages.
Keeping this cookie enabled helps us to improve our website.
This website uses the following additional cookies:
(List the cookies that you are using on the website here.)
More information about our Cookie Policy