DreamHost runs a browser-based File Manager at files.dreamhost.com: a customer types an FTP or SFTP username and password into a web page and gets their website's files without installing an FTP client. For roughly ten weeks, from about August 2026 until the afternoon of Friday 23 October, someone else was on the server behind that page. Everyone who logged in during that time handed their FTP or SFTP password to the intruder as well as to DreamHost.

It is a small incident next to this autumn's headline breaches. It is also the plainest example of a pattern this site keeps returning to: the convenient web front end to a powerful credential is the place to sit, because every user walks through it.

[INFO]
Primary sources: DreamHost's "October Security Incident" notice (29 October 2026) and its breach notification letter filed with the California Attorney General (2 November), both as read on 12 November; the letter through BleepingComputer's report of 4 November.
◈ interactive artifact
The Page Everyone Walked Through
Log in to a recreated web file manager the way a customer did, then switch to what the server's other occupant received. Check whether you would be affected by DreamHost's own criteria, and look for the forwarding rule DreamHost tells customers to hunt for.

//What DreamHost Says Happened

From the notice: "On the afternoon of Friday, October 23, we discovered that an unauthorized third party accessed the server that runs our web-based File Manager at files.dreamhost.com." File Manager is "built on third-party software", and "the unauthorized third party exploited a vulnerability in that software". DreamHost has not named the software or the vulnerability. It took the File Manager servers offline the same day, emailed affected account owners over that evening and weekend, and rebuilt and relaunched File Manager with added monitoring.

What was exposed: the FTP and SFTP usernames and passwords of anyone who logged into File Manager in the window. From there the intruder could "reach certain webmail systems", exposing login credentials for "a limited number of webmail users", and in "a small number of cases" may have used them to read mailbox contents. DreamHost found no evidence of access to control-panel logins or billing details, and says it does not store full card numbers. The notification letter adds that the attack "appears deliberate".

Scope: "well under approximately 10%" of email and FTP/SFTP accounts hosted at DreamHost, with fewer customers known to be affected than first suspected. DreamHost has given no count. It is offering affected people a year of Equifax credit monitoring.

DreamHost also took pains to say what this was not: "This incident was not related to recent PHP server updates." That is a reference to the PHP2Shell bugs disclosed on 21 October, two days before DreamHost found the intrusion; DreamHost says its PHP servers were patched within hours and its web application firewall blocked tens of thousands of attempts before that.

//Why a Web File Manager Is a Good Place to Wait

This is our reading.

It collects the credential in clear text, by design. To act as an FTP or SFTP client, the File Manager server must receive the user's password and use it. HTTPS protects it on the way in; once it arrives, whoever controls that server sees it. There is nothing to crack.
It concentrates the right users. A browser file manager is the tool for people without an FTP client set up, and every one of them hands over a working password. Where that password is reused, it opens more than the website, which is why DreamHost tells customers to change it anywhere else they used it.
The FTP password is a write key to the website. With it, an intruder can change a site's files, which is why DreamHost's first instruction after resetting passwords is to review website files for changes you do not recognise.
Ten weeks is a long time for a server that only relays. A gateway like this has a narrow normal: it receives logins and opens FTP sessions to customer accounts. Outbound connections anywhere else, new processes, or changes to its own code are all unusual for it. DreamHost has not said how it noticed on 23 October.

The same shape appears in this autumn's other hosting incidents. At OPSSHIELD a customer-facing billing app sat next to the key that shipped root updates. At GMO's Desktop Cloud a management server sat behind every customer desktop. The convenient shared front end is the target, and the customers behind it carry the cost.

//If You Host at DreamHost

DreamHost's criteria: you may be affected if you, or an FTP/SFTP user on your account, logged into File Manager between about August 2026 and 23 October 2026 (treat those credentials as compromised), or if an email user was signed out and their old password stopped working on or after 23 October. Passwords that still work and that you did not change were, per DreamHost, not exposed, though it recommends changing them anyway.

What to do, from the notice: set new passwords only through the control panel at panel.dreamhost.com, typed into the browser rather than followed from a link; update saved passwords in mail and FTP clients; review website files for anything you did not change; check webmail forwarding rules and filters for anything you did not create; change the same password anywhere else you used it; and treat emails asking for your password as phishing, since DreamHost says it never asks.

[IOC]
Provider: DreamHost; affected service: web-based File Manager at files.dreamhost.com, built on unnamed third-party software
Window: about August 2026 to 23 October 2026 (discovered the afternoon of Friday 23 October)
Exposed: FTP/SFTP usernames and passwords of File Manager users in the window; webmail credentials for a limited number of users; mailbox contents possibly viewed in a small number of cases
Not found: access to control-panel logins or billing details
Scale: "well under approximately 10%" of hosted email and FTP/SFTP accounts; no count published
Notices: DreamHost "October Security Incident", 29 October; California AG breach notice letter, 2 November

//Sourcing and Uncertainty

The timeline, quotes, exposure, scope wording, actions, the PHP statement, the criteria and the customer steps are from DreamHost's notice. "Appears deliberate", the Equifax offer and the California filing are from the notification letter as reported by BleepingComputer, whose questions about numbers DreamHost did not answer. A customer total of about 400,000 appears in secondary coverage without a source and is not used. The section on why a web file manager is a target is our analysis.

What is unknown. The third-party software and the vulnerability. How the intruder got in in August and how DreamHost noticed in October. How many accounts were affected, and whether any website files were actually changed with the stolen passwords. Who did it.