Scribd says an unauthorized party entered its systems, reached other internal systems and accessed user information. Its current incident notice says the final affected-user notifications were sent on October 30 through Epiq. The help-center record was edited November 2; this is a developing disclosure, not evidence that the intrusion began this week.
Evidence status: unauthorized access confirmed by the affected provider. Scribd says most affected accounts involved basic account information, while a smaller group involved more sensitive information. The public notice supplies neither an account count nor a complete field-by-field exposure list.
Check the notice for your account
Scribd’s guidance covers Scribd, Slideshare, Everand and Fable. It recommends resetting passwords out of caution and checking for the Epiq notification, including in spam or junk folders. Its support page provides a dedicated incident contact for questions about individual exposure.
A Hacker News participant’s posted notification describes possible access to an email address and payment-related details. The listed fields include the card’s last four digits, country, issuer, expiry date and payment history. That is one user’s reproduced notice, not a verified inventory for every account. It does not establish theft of complete card numbers.
The public notice does not specify whether passwords or password hashes were accessed. Its precautionary reset recommendation should not be rewritten as confirmation that they were.
Protect the account without trusting a new message
Open the service’s website or help center independently before changing a password or checking an incident notice. Scribd says it will never ask for passwords or personal information by email, text or phone. A sender claiming to be Epiq is not sufficient proof that a message is genuine.
Use a unique password when resetting an affected account. If the old password was reused elsewhere, replace it on those services too. This is ordinary account-protection advice; it does not assume that this incident exposed passwords.
Payment-related details can make a fraudulent billing or refund message sound credible. Verify unexpected requests through a known support route and review statements for unfamiliar activity. The reviewed evidence does not support a blanket claim that every customer needs a replacement card.
What the thread adds
In the ranked discussion, smurda writes: “I only received this same email a few hours ago, Oct 30.” The participant also links Scribd’s official help-center page. That connects the circulated email to a provider-maintained disclosure, while keeping the receipt date a self-report.
The submitter, x______________, replies by quoting the earlier FAQ’s phased-notification language. The current official page now says all user notifications have been sent. Readers can therefore check for their own notice or contact the incident support channel, rather than assume that another notification round is still coming.
From a 123-comment thread, in HN’s own order.
What remains unresolved
Scribd says it closed the vulnerability, ended unauthorized access, engaged outside forensic experts and notified authorities. It has not published the entry route, affected software versions or a technical reconstruction. There is no customer-installable patch identified in this hosted-service notice.
Caveat: Scribd is reporting on its own incident; its public summary and one reproduced customer email do not establish the full breach scope.