DreamHost has been resetting some email, FTP and SFTP passwords during an ongoing incident, but hasn't explained the cause or said whether customer data was exposed. How much should site owners investigate themselves, and what should they expect the host to disclose?
DreamHost is resetting passwords but hasn't said why. What should customers check?
Answers
A password reset limits future access with the old password. It doesn't tell you whether someone accessed a mailbox or changed a site beforehand.
For WordPress sites, review recently changed files, especially unexpected PHP files under wp-content/uploads. Compare them against a known clean backup where possible. Modification times alone aren't proof either way, so investigate anything unfamiliar rather than deleting it blindly.
Also check each mailbox's forwarding settings and remove forwards you don't recognize, as DreamHost has advised. Keep an independent backup of your site and data while you investigate.
Reply to this answer
Customers need enough information to decide what to check. DreamHost may not know the full scope yet, but it could say what services are affected, whether it has found evidence of access to files or messages, and when it expects another update.
That doesn't mean publishing technical details of an unfinished fix. Acknowledging what is known, what is still being investigated, and what customers should do would be useful without giving away the whole investigation.
Reply to this answer
There are guesses about a PHP vulnerability, but the resets and the mailbox forwarding advice don't establish a cause. They also don't establish that every hosted site was accessed.
I'd treat this as a reason to check your own accounts and files, not as proof of a particular exploit or a host-wide compromise.
Reply to this answer
Don't forget the practical housekeeping. Set new passwords for affected accounts, consider rotating database credentials too, and make sure you have backups outside the hosting account. Check that you can actually restore them.
Reply to this answer
Add your answer
Answers are reviewed before publication.
c.586+fusecaddy:
And check that the backup itself predates any suspicious changes. Restoring a compromised copy could bring the problem right back.