---
title: Your hosting provider says it was breached: assume anything on its servers is exposed, rotate secrets (including from deleted servers), keep DNS and mail alive, and decide whether you have your own breach to report | ctxsec
url: https://ctxsec.com/playbooks/hosting-provider-compromise-customer-response
---

[← Playbooks](/playbooks)

# Your hosting provider says it was breached: assume anything on its servers is exposed, rotate secrets (including from deleted servers), keep DNS and mail alive, and decide whether you have your own breach to report

For customers of a VPS, web or email host that discloses an intrusion or shuts down services (e.g. 1984 Hosting, Nov 2026). Providers rarely know the scope at first, so act on what could have been reached, not on what has been confirmed.

For: IT / ops, Security, Developers, Privacy / legal

[1. Inventory what lived there](#s1)[2. Rotate from a clean machine](#s2)[3. Keep critical services up](#s3)[4. Watch for follow-on abuse](#s4)[5. Decide on notification](#s5)

1.

Step 1 of 5

__

### Inventory what lived there

You can't rotate what you don't know about.

   - List every VPS, site, mailbox, DNS zone and backup at the provider, including servers deleted in the last year
   - For each, note the secrets it held: SSH keys, .env files, API tokens, database and cloud credentials, wallet keys
   - Note which domains use the provider's nameservers or registrar

2.

Step 2 of 5

__

### Rotate from a clean machine

Assume disks, snapshots and backups were readable.

   - Revoke and reissue credentials at the issuing service (cloud IAM, GitHub, payment/API providers), not just on the server
   - Replace SSH host and user keys; remove the provider's IPs from allowlists elsewhere
   - Move crypto keys that ever touched the host to new wallets

3.

Step 3 of 5

__

### Keep critical services up

Outages last days.

   - Add a secondary DNS provider for important zones, or move nameservers if your registrar is elsewhere
   - Remember sending mail servers retry for about 4-5 days; restore mail elsewhere before that if the outage drags on
   - Restore sites from off-site backups to another host if downtime is costly

4.

Step 4 of 5

__

### Watch for follow-on abuse

Breaches feed phishing and account takeover.

   - Warn staff and users about fake provider 'security notices' asking for logins or payment
   - Monitor for logins with the rotated credentials and for changes to DNS records
   - Check sites for injected code when they come back

5.

Step 5 of 5

__

### Decide on notification

Data you host for others may make this your breach too.

   - If personal data sat on the host, assess GDPR/state-law duties (72 hours under GDPR from when you become aware)
   - Ask the provider in writing what was accessed, how long it keeps data from deleted servers, and when it will confirm scope
   - Document decisions and timelines for regulators

Original content by ctxsec. Printable checklist: use your browser's print view.
