DreamHost breach and WordPress email: what to do

If your WordPress site is hosted at DreamHost and its contact form, order emails or password-reset messages went quiet some time after 23 October, the likely cause is a password DreamHost changed without the site knowing. DreamHost has since disclosed why it reset passwords: an attacker broke into its File Manager server and reached some webmail systems. A site set up the way DreamHost’s own instructions describe sends its mail by logging in to a DreamHost mailbox, so it lost the ability to send when that password changed. The site rarely says so: some forms report an error to the visitor, but many show their success message anyway. If you or an FTP user on your account logged in to DreamHost’s File Manager since August, the credentials stored in the site may need replacing too.

What DreamHost has said

On 29 October DreamHost said what happened. An attacker exploited a flaw in the third-party software behind File Manager, the browser tool at files.dreamhost.com that customers use to work on their website files, and got the FTP/SFTP usernames and passwords of people who logged in to it between about August 2026 and 23 October. The attacker also reached certain webmail systems. DreamHost says the incident affected “a fraction of email and FTP/SFTP accounts hosted at DreamHost, well under approximately 10%”, that it has found no evidence of access to control-panel logins or billing details, and that its investigation continues. The notice it filed with the California Attorney General is headed “Notice of Data Breach”, and the filing gives 15 August 2026 as the date of the breach.

DreamHost’s post and the letter filed with the Attorney General describe the webmail access differently: the post says the attacker obtained “the login credentials of a limited number of webmail users”, and the letter says the access “may have exposed the session information (the data that keeps a user signed in, including session credentials)” of a limited number of users. On what was read, the post says DreamHost believes mailbox contents may have been viewed in a small number of cases and that it is contacting those customers individually, while the letter says “the contents of your email and files in the FTP/SFTP server may have also been accessed”. The post makes no such statement about files, but it does ask owners to look over their website files for changes they don’t recognise.

DreamHost also narrowed who needs to act. Not everyone it emailed turned out to be affected, and it says anyone who got no email needs to do nothing for now. A password that still works, and that you haven’t changed yourself, was not exposed on its findings so far, though it encourages changing that too. If you or an FTP/SFTP user on your account logged in to File Manager in that window, it says to “treat those usernames and passwords as compromised”.

The resets came before any of that. DreamHost’s status page reported File Manager trouble on the afternoon of 23 October (Pacific time). By that evening it said several services were affected and “As a precaution, we are resetting the passwords of some email accounts”, which stopped old passwords working in webmail and email apps; FTP and SFTP users were added later that night. On 25 October it said every affected account owner had been emailed instructions. On 26 October it reported File Manager back online and said resets were “still required for a subset of email and FTP/SFTP user accounts”, which suggests some owners have yet to set them. DreamHost marked the incident resolved on the afternoon of 27 October (Pacific time), with the same reminder: some email and FTP/SFTP users still need a new password before they can log in again.

BleepingComputer’s report adds what the notices to account owners ask for: check every mailbox for forwarding rules and remove destinations you don’t recognise, change any reset password you also use elsewhere, and tell your mailbox and FTP users yourself, because DreamHost can’t contact them directly.

Why a mailbox reset stops WordPress mail

DreamHost’s WP Mail SMTP setup guide has the site send through smtp.dreamhost.com on port 587 with TLS (encryption for the connection), logging in with “your DreamHost email address” and that address’s password. The DreamHost host page explains why DreamHost recommends that setup: without a mailer plugin, WordPress there sends unsigned mail that inboxes trust less.

That makes the mailbox password the site’s sending password. When DreamHost reset it, the copy saved in WP Mail SMTP, FluentSMTP or Post SMTP went stale, and every send since has been refused at login. Neither DreamHost’s notices nor its 29 October post mentions SMTP by name; this follows from the setup, because the mailbox login and the SMTP login are the same login.

In WP Mail SMTP’s or FluentSMTP’s test email, the failure reads SMTP Error: Could not authenticate., the wording of PHPMailer, the mail library WordPress ships. Post SMTP sends through its own library by default and shows the mail server’s refusal instead. The full reply, starting with 535 (the SMTP code for a rejected login), is in the email log’s Session Transcript.

The reset doesn’t touch a site with no mailer plugin: that site sends through PHP’s mail() without logging in to anything. If its mail stopped, the cause is elsewhere, and debugging with the wp_mail_failed hook is the place to start. Nor does it touch sites that send through a provider’s API key or the provider’s own SMTP login (Postmark, SMTP2GO, Mailgun and the like), because they don’t log in to DreamHost to send. That is inference from the setup: DreamHost hasn’t listed which logins it reset beyond “email and FTP/SFTP users”. Whether those sites’ keys were exposed is a separate question, covered below.

FTP logins break the same way. If wp-config.php sets FTP_PASS for updates, or a deploy script pushes over SFTP, put the new password there.

Getting mail working again

  1. Set the mailbox’s new password in the DreamHost panel. During this incident the account owner sets it; mailbox users can’t log in until they do. Use the mailbox your mailer plugin logs in with: it is the username in the plugin’s SMTP settings. DreamHost says a new password can take up to 15 minutes to apply, and warned that changes made before its reset finished on 24 October “will be overwritten”, so a password changed early may not be the one in force now.
  2. Paste the new password into the mailer plugin and save. If the password field is greyed out or says it is set by a constant, it lives in wp-config.php instead (WPMS_SMTP_PASS for WP Mail SMTP); change it there.
  3. Send a test email from the plugin’s test screen to an address outside DreamHost.
  4. Find what didn’t go out. Post SMTP emails the site’s admin address about failed sends by default (subject “Post SMTP email error”), so check that inbox and its spam folder. FluentSMTP and Post SMTP keep an email log and can resend a failed message from it; WP Mail SMTP’s log is a Pro feature, but the free version records failed sends under Tools → Debug Events and shows a failure notice in the dashboard. Resend orders and form notifications; on a WooCommerce order, the Order actions box has “Send order details to customer” and “Resend new order notification”. Don’t resend password-reset emails: their links expire after a day by default, so the user has to ask again. Without a log, check whether your form plugin stores entries.

Check forwarding rules and filters on the right mailbox

DreamHost asks owners to check every mailbox for forwarding rules and filters they didn’t set up. For a WordPress site, the mailboxes that matter most are the one WordPress sends admin mail to (Settings → General → Administration Email Address) and the one on your own WordPress user account, if either is at DreamHost. Often neither is the mailbox the plugin logs in with. A WordPress password-reset email carries a working reset link, so a forwarding rule on either of those mailboxes hands the link to whoever added the rule.

Whether to change anything else

Inference: a password reset can stop future logins with the old password, but it can’t take back what has already been read. DreamHost’s post doesn’t mention SMTP, databases or wp-config.php, so everything below that isn’t attributed to DreamHost is inference from where WordPress keeps credentials.

If you or an FTP/SFTP user on your account logged in to File Manager since August, assume the site’s files were read: the attacker had the login, and the letter says files may have been accessed. Treat every constant in wp-config.php as exposed. That covers mailer secrets kept there (WPMS_SMTP_PASS, FLUENTMAIL_*, POST_SMTP_*) and FluentSMTP’s encryption keys. It also covers DB_PASSWORD, a database credential, though whether that value permits a database connection depends on the host’s access controls. Inference: if the database could be reached, credentials a mailer plugin stores there by default (including SMTP passwords, API keys and OAuth tokens) may have been exposed. The same FTP/SFTP login could change files, so look over the site before any new credential goes in.

If nobody used File Manager in that window, DreamHost’s post doesn’t identify a route from the attacker to your site’s files through stolen FTP/SFTP logins, but the letter says files in the FTP/SFTP server may have been accessed and doesn’t limit that to File Manager sessions. Neither document says whether any particular site’s API keys or OAuth tokens were exposed. Before deciding whether to rotate them, review the site’s files and mailboxes and check each provider’s activity and credentials.

If DreamHost reset a mailbox that holds account emails, the new password doesn’t undo anything already read. The letter says to consider whether the contents of your emails or files mean other accounts need review. On a WordPress site that means SMTP logins or API keys sent by email, and any sending provider whose account is registered to that mailbox, because whoever reads the mailbox can request that provider’s password-reset emails. Check the provider’s sending log and API keys back to August.

Host breached: are my WordPress email credentials exposed? maps what each kind of access exposes, and rotating SMTP credentials after a compromise has the order and the steps per provider.

Fake reset emails

An incident like this is cover for phishing: a message that looks like a DreamHost reset notice and links to a login page that isn’t DreamHost’s. DreamHost says its incident emails will never ask you to sign in through a link. Type panel.dreamhost.com yourself to set passwords, and check anything a notice claims against the status page.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *