Droplets get locked down because of outgoing DDOS attacts.

Two of my droplets were locked down this week from my account for an apparent reason of outgoing DDOS attack.

My first machine was allegedly compromised on Nov 18 2014 and my networking is brought down - which essentially means the server is off the internet. We found a directory containing suspicious files and I assumed the possibility of DDOS from my server because of these files. The support also sent a packet and a destination IP of the traffic that was going out. Plus I also had set a weak password which made me believe that there is really a DDOS originating from my server. Eventually I had to destroy the server

But today Nov 21 2014. This happened again.

The new droplet has a really really strong password and it was created on Nov 19 2014. I don’t see a reason how this can happen again. I get a similar email from DO saying “Uh on, we have a problem” and a ticket has been raised with a same format as the previous one and I have pretty good idea on where this is going to end.

How do I take care of this?

Show comments

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

This question was answered by @sierracircle:

you might need to nuke everything and build back from scratch.

then…create a really strong back-up routine that backs-up everything on a daily basis…to a separate location. also, another backup-routine backs everything up on a weekly or monthly basis to a different folder.

That way, if you have this happen again, you have a selection of backups to restore from before any attacks happened…

doing that will save you loads of headaches…

After that, you might consider limiting ssh access to your droplet from only one IP.

You can see the comment here.