DreamHost Data Breach: What Happened and What You Should Do
DreamHost disclosed a data breach affecting an unconfirmed number of people. Here's what is currently known about the incident, what information may have been exposed, and steps you can consider taking.
- Company
- DreamHost
- People affected
- Undisclosed
DreamHost has not published a total number of people affected in the sources reviewed.
- Incident date
- August 15 – October 23, 2026
- Discovered
- Not yet disclosed
- Disclosed
- November 2, 2026
- Information exposed
- Account credentials · possibly email address, other personal information
- Status
- Notification underway
Sessions terminated and passwords reset for potentially affected users; one year of identity theft protection offered.
What happened in the DreamHost breach?
How the attacker got in
An unauthorized third party exploited a vulnerability in DreamHost's web-based File Manager software and also reached certain webmail systems.
Reports conflict
Timeline of what is known
- 01August 15 – October 23, 2026Unauthorized access
- 02Not yet disclosedBreach discovered
- 03November 2, 2026Breach disclosed publicly
- 04November 2026Affected individuals notified
Dates come from the sources listed at the bottom of this page. Separate events are kept separate; where a date has not been disclosed, it says so.
What information was exposed?
The categories below come from DreamHost's disclosure and the sources listed on this page. Each is labeled by what the evidence supports. Categories not mentioned in any source are not listed, even if they are common in similar breaches.
Account credentials
FTP/SFTP usernames and passwords of people who used the File Manager, and webmail session credentials for a limited number of users (DreamHost notice).
Email address
Contents of webmail accounts may have been accessed (DreamHost notice).
Other personal information
Contents of files stored on the FTP/SFTP server may have been accessed (DreamHost notice).
Why this information matters
The risks below are the ones associated with the categories of information involved in this breach. This describes how exposed information can be used in general. It does not state that any of this has happened with data from this incident.
Information from one breach can sometimes be combined with information from other breaches or public sources. A name and email address on their own are limited. Paired with a date of birth from one leak and an address from a people-search site, they become enough to answer a security question or make a scam call sound informed.
Whether the data from this breach has been sold, shared, or used is not known unless a source on this page says so. Where that is documented, it appears in the "What happened" section above.
If you were affected, consider doing these things now
Practical steps for this breach, in rough order of priority. None of these require buying anything. Monitoring services, including ours, are one option among several.
- 01Change your DreamHost File Manager, FTP/SFTP, and webmail passwords, and change the password anywhere else you used the same or a similar one.
- 02Check your website files for unexpected changes and your email settings for forwarding rules or filters you did not create.
- 03Review the contents of your email and hosted files for anything that could be used to get into other accounts, and secure those accounts.
- 04Enroll in the complimentary identity theft protection using the instructions in your notice.
- 05DreamHost says it will never ask for your password by email; treat any such request as phishing.
AI Protection
Monitoring, alerts, and recovery help for what comes after a breach.
A breach puts information you can't take back into circulation. AI Protection watches for it being misused, alerts you when something changes, and helps you recover if something goes wrong. It cannot undo the breach or retrieve data an attacker already holds.
How one breach can contribute to a larger exposure footprint
A possible risk pattern, not a description of this incident. Each step is something that can happen after a breach. Nothing here states that it has happened with data from this incident.
Illustrative pattern- Step 1
One breach
A single company's records are accessed without authorization.
- Step 2
Personal information is exposed
Some categories can be changed afterward. Others, like a name or date of birth, can't.
- Step 3
It may remain accessible
Copies of breached data can persist well beyond the original incident.
- Step 4
Sources can be combined
Fragments from different breaches and public sources may be assembled into a fuller profile.
- Step 5
More targeted attempts
A fuller profile can make fraud, impersonation, phishing, or social engineering attempts more convincing.
A breach is an event. Exposure can last longer.
A password can be reset and a card reissued. Some information can't be replaced, and that is the part that stays useful to someone attempting fraud later. This does not mean fraud will occur. It means the risk does not close when the news cycle does.
Involved in this breach and hard to change
None of the categories reported in this breach are in the hard-to-change group. Changeable items like passwords and account numbers should still be addressed.
What DreamHost has done so far
Only actions the company has announced or that are documented in the sources below. If something you'd expect to see isn't here, it hasn't been announced as of the last update.
Sources
Primary sources first: company disclosures, regulator and attorney general filings, SEC filings, court documents. News reporting is listed as secondary. Where reports conflict, the conflict is noted in the "What happened" section rather than resolved silently.
Last updated November 4, 2026 · First published November 4, 2026
Questions about the DreamHost breach
Take control of what happens next.
Monitoring for misuse of your information, alerts when something changes, and a real person to call if something goes wrong. Plans from $7 per month. Cancel anytime.