DreamHost says hackers accessed its systems and customer session data for three months
According to a filing with California's Attorney General, DreamHost says hackers had access to its systems, including customer session information, for about three months.
Written by a model from the sources below. Verify against them.
- Vendor
- DreamHost
- Status
- Confirmed
- Disclosed
- Data taken
- Tokens and keys
Summary
The item reports that DreamHost had earlier resolved an incident affecting customers' email and FTP access, and that session data could let attackers log in.
What to do
Rotate API keys and tokens you gave it, and review the OAuth apps and integrations connected to it
For tokens and keysReset your DreamHost account password
Log out all active DreamHost sessions and review recent logins
Enable two-factor authentication on your account
Check email and FTP access logs for unfamiliar activity
Timeline
- Made public by Zack Whittaker on Bluesky
- Confirmed by DreamHost
Zack Whittaker on Bluesky: “In a filing with California's AG, DreamHost says hackers had access to its systems, including customer session info (which lets attackers log in!), for 3 month…”
- First seen by cve.now
What was taken
| Taken | Per the source |
|---|---|
| Tokens and keys | Zack Whittaker on Bluesky: “In a filing with California's AG, DreamHost says hackers had access to its systems, including customer session info (which lets attackers log in!), for 3 month…” |
Evidence 1
- PressZack Whittaker on Bluesky
“In a filing with California's AG, DreamHost says hackers had access to its systems, including customer session info (which lets attackers log in!), for 3 months!”
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about the DreamHost breach
Was DreamHost breached?
Yes. DreamHost says so: “In a filing with California's AG, DreamHost says hackers had access to its systems, including customer session info (which lets attackers log in!), for 3 months!” (Zack Whittaker on Bluesky).
What data was exposed?
Tokens and keys.
What should DreamHost customers do?
Rotate API keys and tokens you gave it, and review the OAuth apps and integrations connected to it. Reset your DreamHost account password. Log out all active DreamHost sessions and review recent logins. Enable two-factor authentication on your account. Check email and FTP access logs for unfamiliar activity.