Help for owners
DigitalOcean says my server is sending abuse traffic or was hacked
Short answer
DigitalOcean's guidance says that when a Droplet sends unusually large traffic, its normal internet access is disabled because it has usually been compromised. You can still reach it through the Recovery Console. The recommended path is to copy the content off, build a fresh hardened Droplet, and redeploy, rather than clean the old one.
Does this sound like your situation?
- I got an abuse or security email from DigitalOcean about my server.
- My site went offline and the server is cut off from the internet.
- Strange processes, files or logins appeared on the server.
- Bandwidth or CPU use spiked with no extra visitors.
- My developer says the server was probably compromised.
Why does this happen?
DigitalOcean disables internet access on purpose
Its guidance says unusually large outgoing traffic usually means the Droplet is compromised and is being used to send spam or malicious traffic, so normal internet access is disabled. Console access through the Recovery Console remains.
Confirmed by docs.digitalocean.com
Weak entry points were left open
Common doors are guessable passwords, root login over the internet, old software and open admin forms. DigitalOcean's list of hardening steps names disabling root login, using SSH keys, keeping software updated, strong passwords and strict firewall rules.
Confirmed by docs.digitalocean.com
A web app was the way in
An outdated website plugin or upload form can let someone run code without any password. The server then looks like it was hacked even if the login was never touched.
Cleaning in place is unreliable
DigitalOcean recommends moving to a fresh Droplet rather than trying to clean the old one. It lists tools for investigating the old server, but you cannot be sure every backdoor is found.
Confirmed by docs.digitalocean.com
No backup means a harder recovery
If files only exist on the Droplet, getting them out depends on the Recovery Console and a working password.
Confirmed by docs.digitalocean.com
What can I do about it today?
- Read DigitalOcean's email and keep itIt names the Droplet and the problem. Do not ignore it, and do not delete the email.
- Do not delete the Droplet yetIt holds your files and the evidence of what happened. A rebuild or destroy removes what is on the disk.
- Change passwords that were used on itChange the passwords for the database, the website admin and DigitalOcean itself, and turn on two-step sign-in. Do it from a computer you trust.
- Ask for the files to be copied out firstThe Recovery Console and the recovery ISO let someone copy data off. You need a root or sudo password, which can be reset from the control panel.
- Tell your customers if their data might be involvedKeep it factual. If personal data was stored, someone responsible for legal duties should decide what to say. I cannot give legal advice.
- Plan to rebuild, not repairAgree with your developer to set up a new server from clean software and copy only checked content onto it.
When should I bring someone in?
- Customer data or payment pages were on that server.
- You have no backup and no password for the Recovery Console.
- The same files or database were shared with other servers.
How do I handle it?
- Preserve before anything elseA snapshot is taken and the logs are copied so there is a record of what happened.
- Recover the contentThrough the Recovery Console and ISO route I copy out the site files and the database export, nothing that runs.
- Build a clean, hardened serverNew Droplet, SSH keys only, root login off, firewall closed except what is needed, software current.
- Redeploy and check each stepI check uploaded files and the database for signs of tampering before they go back.
- Find the way in and add backupsI look at logs and the app for the entry point, then set up scheduled backups, tested by a restore.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Can I just clean the server?
DigitalOcean's guidance recommends a fresh Droplet instead. It cannot be sure what an attacker left behind, and nor can I.
Will the internet come back by itself?
I cannot say. The notice and DigitalOcean support decide that, usually after the cause has been dealt with.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.
For your developer: the technical fixes
Failed password for invalid user admin from 198.51.100.23 port 40122 ssh2Your auth.log is full of Failed password and Invalid user attemptsCertbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:A Let's Encrypt certificate did not renew with Certbot