Possibility of being hacked?


Ok, so on June, 21 my website was getting bruteforce attack on my website. No biggie. It is just a bot that tries usual username/password combinations, it was happening before. But this time my whole droplet went down and all of my sites were down. CPU got to 130% and my write speed on disk droplet went to 9 MB/s.

My question is how to know what was written. I don’t think anyone got into droplet. Maybe it was log files. If anyone knows if there is any scan for malware or something that would be helpful.

Thank you.

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Hi there,

You can install malware detection software like Linux Malware Detect, also known as Maldet or LMD. It will help you to locate any malicious files on your droplet.

If you’re interested in securing your droplet (everyone should be in general) you can double-check our tutorial - An Introduction to Securing your Linux VPS.

The article will cover the basic and some more advanced steps in website and server security.

You can check the article here:

Hope that this helps!

also, more simply, just change the login page for wordpress from wp-login.php to something else.

I do this now on every wordpress install I do, and it reduces those brute-force attacks to zero.

you can then delete wp-login.php, but I still add a line to my .htaccess to protect it, since it gets added back during updates:

    #prevents access to wp-config
    <Files wp-config.php>
    order allow,deny
    deny from all

#prevents access to wp-login
   <Files wp-login.php>
    order allow,deny
    deny from all

It’s also probably not a bad idea to add a host based detection system (HIDS) like Tripwire or OSSEC. These collect details about your filesystem and configuration. It then stores this information to reference and validate the current state of the system. If changes are found between the known-good state and the current state, it could be a sign that your security has been compromised. This software can keep track of many different filesystem data points in order to detect whether unauthorized changes have occurred. Good luck.